Best practice for avoiding locks on a heavily read table?

Posted by Luiggi on Stack Overflow See other posts from Stack Overflow or by Luiggi
Published on 2010-05-06T14:45:19Z Indexed on 2010/05/06 14:48 UTC
Read the original article Hit count: 162

Hi,

I have a big database (~4GB), with 2 large tables (~3M records) having ~180K SELECTs/hour, ~2k UPDATEs/hour and ~1k INSERTs+DELETEs/hour.

What would be the best practice to guarantee no locks for the reading tasks while inserting/updating/deleting?

I was thinking about using a NOLOCK hint, but there is so much discussed about this (is good, is bad, it depends) that I'm a bit lost. I must say I've tried this in a dev environment and I didn't find any problems, but I don't want to put it on production until I get some feedback...

Thank you! Luiggi

© Stack Overflow or respective owner

Related posts about sql-server-2008

Related posts about locking