Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

MS SQL Server 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • There was a story on slashdot about this. Five of thirteen root nameservers disabled - ouch. I've never heard a good thing about MS SQL Server (and not just because MS makes it). Why do folks use it? I'm genuinely curious.

    • Re:slashdot (Score:2)

      by Matts (1087) on 2003.01.26 17:58 (#16401) Journal
      It's actually not a bad database, so long as you understand its locking strategies. It's based off an old branch of Sybase, so it's got good heritage. We use it in an extremely large installation - over 25 replicated SQL servers globally. It all seems to work fairly well, though I try not to get involved.

      However where MS SQL Server doesn't work is when you get deadlocks. Its locking strategy is significantly poorer than PostgreSQL or Oracle's (i.e. it doesn't do MVCC - reading commited data while other transactions are in progress) - you can either lock completely, or allow dirty reads (reading uncommited data!). And locking completely often causes lock ups. Same problem in Sybase though (and other locking databases).
      • There's also the problem with row locks myseriously escalating into page locks (they may have changed this behavior in SQL Server 2000, but it was definitely a problem in 6.5 and 7).
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.