Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
While investigating a problem I believed to be related to lock escalation and thinking that READ_COMMITTED_SNAPSHOT would be the solution, I checked whether it was already enabled. To my surprise, the database had compatibility level 80 (SQL Server 2000, and I’m new here, and nobody or document seems to know why!).
But READ_COMMITTED_SNAPSHOT was new in 2005. So even though it’s enabled, does it have any affect when running in 2000 compatibility mode?
The compatibility mode refers to features available in the backaward mode. Any new feature will run unaffected. For instance you can set the compatibility mode to 80 and have the old outer join syntax, but at the same time you can create a Service Broker queue and it will run just fine.
Snapshot isolation is a new feature and works in backward compatible databases unaffacted.