February 12, 2004 at 6:56 am
Does anyone know if putting SET STRANSACTION ISOLATION LEVEL READ UNCOMMITTED in a stored procedure actually works? I know that in 6.5 it does not work, however what about 2000?
I just would rather use this to recode the exisitng stored procedures than have to go through and add nolock hints to all of the selects.
February 12, 2004 at 12:10 pm
It has been my experience that this works as documented in BOL.
February 12, 2004 at 12:55 pm
I've run a couple of tests and it seem to be working as it should.
Thanks.
February 12, 2004 at 1:25 pm
You may use "NOLOCK" hint in select statement. The hint has same effect as the SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED.
February 13, 2004 at 8:19 am
We use this command in all our report SPS, or as a connection property, and it works as expected.
February 13, 2004 at 9:13 am
We have hundreds of procs and I wanted to avoid having to recode the entire group by going through with the nolock hint which is why I wanted to go the read uncommited route.
Looks like it works. Thanks folks.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply