Brandie Tarvin (7/30/2015)
And now I'm finding out our databases aren't set up to allow snapshot or read committed isolation. So do I take the overhead hit or not?How do people deal with isolation levels if the databases aren't set up to use them? I guess they use NOLOCK.
Consider this.
If it is a handful of queries causing the grief, snapshot is probably overkill.
If they have any code using the nolock directive, or connection strings that force a specific isolation level for the connection, then the SNAPSHOT isolation will be overridden - and you are right back at the same problem.
I would do a little more digging and find the top 10 grief causing queries and see if they are constantly related to blocking or deadlocking. I would also see if they are things that can get away with using nolock. But in the end, it will take a little investigation and some blood and tears on your part.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events