x

Isolation Levels

For reading dirty data you can set isolation levels at a Connection level using

SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED

Do any of these help with locking / blocking issues at a global level?

ALTER DATABASE MyDatabase
SET ALLOW_SNAPSHOT_ISOLATION ON

or

ALTER DATABASE MyDatabase
SET READ_COMMITTED_SNAPSHOT ON
more ▼

asked Nov 18, 2009 at 02:24 PM in Default

avatar image

Raj More
1.8k 82 87 90

(comments are locked)
10|1200 characters needed characters left

1 answer: sort voted first

I added tags for transaction and isolation-level to your question. There are some good answers in some of the previous questions:

What is snapshot isolation?

Which row-versioning transaction isolation level do you use?

Transaction Types in SQL Server 2005

short answer: Yes, both help by reducing the need for locking but both also increase usage of tempdb.

more ▼

answered Nov 18, 2009 at 02:39 PM

avatar image

Tom Staab ♦
14.5k 7 14 18

Just to clarify, those options are not for dirty reads. They are used to avoid lock/block issues when dirty reads are unacceptable.

Nov 18, 2009 at 02:40 PM Tom Staab ♦

Good answer as usual, sir.

Nov 18, 2009 at 04:27 PM Matt Whitfield ♦♦
(comments are locked)
10|1200 characters needed characters left
Your answer
toggle preview:

Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

SQL Server Central

Need long-form SQL discussion? SQLserverCentral.com is the place.

Topics:

x1067
x72
x47
x30
x15

asked: Nov 18, 2009 at 02:24 PM

Seen: 2324 times

Last Updated: Nov 18, 2009 at 02:35 PM

Copyright 2016 Redgate Software. Privacy Policy