Postgres vs. MSSQL
dcrookston at gmail.com
Wed Nov 8 10:59:49 MST 2006
On 11/8/06, Michael L Torrie <torriem at chem.byu.edu> wrote:
> Clearly your company's decision will not be made on technical grounds.
We can always pretend.
> But if you want to base it soley on technical grounds, there is no
> contest, according to what I've been told. Postgres is better hands
> down. I have a friend (famous last words I know) who does large-scale
> database programming for a living and tells me MS SQL is based on the
> old Sybase engine, which has serious locking issues. He claims to have
> code that can, with just a few concurrent queries, bring MS SQL, Sybase,
> and even DB2 to their knees. (MySQL too, obviously.). The only
> databases that can handle some of their stuff are Oracle and PostgreSQL.
> Bear in mind I'm not talking about the the granularity of the lock
> (MySQL's locking is much finer now than it used to be) but rather the
> techniques used to enforce data integrity. If I recall correctly,
> PostgreSQL and Oracle do not use locks at all to enforce integrity.
> Maybe someone more knowledgeable can explain to me why this might be.
Is it possible to get more information from your friend about this?
> Well it's likely that PHP and Django don't use any advanced DB features
> like triggers, constraints, or stored procedures, so it really doesn't
> matter in the least what db you pick, as long as the load is manageable.
PHP can, Django doesn't have it (except foreign key constraints)
natively. But since we'll be running reports and things from outside
of Django, those things do come into play.
More information about the PLUG