You don't have to use ISOLATION LEVEL SNAPSHOT in order to use row-versioning instead of locks. You can just use.
You don't have to use ISOLATION LEVEL SNAPSHOT in order to use row-versioning instead of locks. You can just use ALTER DATABASE RM2 SET READ_COMMITTED_SNAPSHOT ON; to tell your database that it should use row-versioning with ISOLATION LEVEL READ COMMITTED. And because that's the default isolation level, all your current queries that don't specify a different isolation level will than automatically use row-versioning.
For reference: MSDN.
Although this seems to be the correct approach, i'm still getting "timeout expired" and "deadlock victim" errors in the ASP. NET application if someone executes time-consuming queries,stored-procedures or reports in SQL-Server at the same time. Do you have an idea how to check if this transaction level is working as expected?
– Tim Schmelter Oct 13 at 9:35.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.