Posted by Erland Sommarskog on 03/08/06 00:05

pb648174 (google@webpaul.net) writes:
> SQL 2005 - Row level versioning works very nice for this purpose.

Yes, snapshot isolation can be a very good way to resolve locking issues.
And note that there is a database switch: ALTER DATABASE db SET
READ_COMMITTED_SNAPSHOT ON. This changes the default isolation level of
READ COMMITTED to use the snapshot instead.

However, I got the feeling that Robert's problem rather was long-running
queries, and not blocking.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

• Next in forum: Re: Can a stored procedure parameter be optional
• Prev in forum: Re: ORDER BY in VIEW not working
• Thread view: Re: How does one set read-uncommitted on the entire DB?

[Reply to this message]