Posted by Igor on 04/23/07 12:43

1. In this topic
http://groups.google.com/group/comp.databases.ms-sqlserver/browse_thread/thread/b4a07b516f4a2fcd/cb21516252b65e7c?lnk=gst&q=SET+TRANSACTION+ISOLATION+LEVEL+READ+UNCOMMITTED&rnum=10#cb21516252b65e7c,
someone wrote: "I've implemented SET TRANSACTION ISOLATION LEVEL READ
UNCOMMITTED at the beginning
of a number of stored procedures and, then SET TRANSACTION ISOLATION
LEVEL READ
COMMITTED at the end to minimize the disruption to the application.".
My question is, do you really need to set READ COMMITTED at the end of
stored procedure? What scope does that command affect?

2. Could someone write some real world example where i should never
read uncommitted data... i'm having trouble understanding when i
should and when i should not use it.

[Back to original message]