CODEWITHSUNDEEP
sql-serversql-server-2008isolation-level
Sunil
Sunil

Reputation: 21406

What are usual objections to allowing SNAPSHOT level in SQL Server 2008?

What are the usual objections raised by DBAs when developers request the DBA to allow SNAPSHOT isolation level in a SQL Server 2008 database? Read Committed SNAPSHOT is not being requested but simply isolation level of SNAPSH

Upvotes: 1

Views: 715

Answers (1)

Grant Fritchey
Grant Fritchey

Reputation: 2795

I wouldn't say there usually are objections. As a DBA, I actively encourage development teams to let me use the Read_Committed_Snapshot isolation level. In fact, I prefer it. As it says in the comments, I will see an increase in the use of tempdb because of it, but the reduction in blocking is well worth the cost.

I'm not as crazy about the use of SNAPSHOT because, usually, I can't sell developers on the idea that they need to change their code, which they do. Also, because it's completely dependent on the developers to correctly code it's use, I see more errors, places where it won't work or where it creates problems. That's why I'd rather just enable the isolation level at the database.

I'm sure this is fixed now, but several years ago a project I was working on had problems using SNAPSHOT with nHibernate. I don't remember any of the details, just that they hit issues, but it was quite a while back.

Upvotes: 3

Related Questions