Posted by pb648174 on 12/06/05 17:22

I just wanted to post a follow up to a message I posted some months ago
about a long running transaction that was blocking all other users...
The link is below

http://groups.google.com/group/comp.databases.ms-sqlserver/browse_thread/thread/1063b65df1f97492/8649bee2002646a2

By using the new "Row versioning" functionality of SQL 2005, it
completely solved this problem. By reading the books online, it says
there is a performance impact, but that the better performance of SQL
2005 in general might offset it. So far this seems to be the case. just
posting it here in case anyone else has the problem. The SQL command Ii
had to execute to get everything working properly was:

ALTER DATABASE DBname
SET READ_COMMITTED_SNAPSHOT ON;

[Back to original message]