• ta.bu.shi.da.yu (10/28/2009)


    rbramhall (10/28/2009)


    I just wish there was another way that when inserting/deleting the 2.5M records in my table it wouldn't do a total table lock and at 2-3 minutes it causes timeouts on any other store retrieving data from that table.

    Any ideas?

    Thanks!

    Sorry, just realised the way that your table has been put together.

    You can actually stop lock escalation in SQL Server... though that seems a bit drastic. But if you look at the following article it will tell you how to do this. Use at your own risk though!

    However.. I've never really tried using it, but perhaps snapshot isolation might help? Of course, that would put contention on TempDB... someone might want to chime in here if I'm telling anything misleading 🙂

    I'll check out the article. I looked into the Snapshot Isolation before we went from 4 RAID 5 drives to 36 drives. Now that I have the TempDB Data on 4 drives in RAID 10 and TempDB Log on 4 drives in RAID 10, I'll definitely look back into the Snapshot Isolation. Thanks.