Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Ciupaz
Posting Yak Master
232 Posts |
 Posted - 2013-07-18 : 11:05:08
|
| Hello all,in some stored procedure (written by someone else), I've found these settings at the beginning: SET NOCOUNT ONSET XACT_ABORT ONSET TRANSACTION ISOLATION LEVEL READ COMMITTEDIs a good practice to set the Isolation Level to "Read Committed"?Is not already the default setting for SQL Server 2008? Is a good idea to put also the Xact_Abort ON?Let me know. Thanks a lot. Luis |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
denis_the_thief
Aged Yak Warrior
596 Posts |
Posted - 2013-07-18 : 13:37:57
|
| Read Committed is the default default so to speak. You can change a Database's Default to Snapshot Isolation. So that maybe one reason, they want to override this. Also the Transaction Isolation Level is for a session so if it was set to something else earlier in the session, this statement would have an effect - changing it to READ COMMITTED.Not sure about the XACT_ABORT ON in Stored Procedures, we don't do this but then again we are only starting to get into the TRY/CATCH. |
 |
|
|
Ciupaz
Posting Yak Master
232 Posts |
Posted - 2013-07-19 : 03:40:15
|
| Where I can find the Isolation Level of my DB? Under Properties -> Options I've not found it. Maybe, I think, these statements has been added to guarantee the atomicity of the operations. L |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|
|
Setting Isolation Level in stored procedure