English 中文(简体)
READ_COMMITTED_SNAPSHOT on SQL Server 2005 in 2000 Compatability Mode?
原标题:

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.

问题回答

暂无回答




相关问题
Export tables from SQL Server to be imported to Oracle 10g

I m trying to export some tables from SQL Server 2005 and then create those tables and populate them in Oracle. I have about 10 tables, varying from 4 columns up to 25. I m not using any constraints/...

SQL server: Can NT accounts be mapped to SQL server accounts

In our database we have an SQL server account that has the correct roles to access some of the databases. We are now switching to windows authentication and I was wondering if we can create a NT user ...

SQL Server 2000, ADO 2.8, VB6

How to determine if a Transaction is active i.e. before issuing Begin Transaction I want to ensure that no previous transaction are open.. the platform is VB6, MS-SQL Server 2000 and ADO 2.8

热门标签