Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««12345

Row Level Versioning Expand / Collapse
Author
Message
Posted Tuesday, January 31, 2012 10:45 AM


Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Monday, November 24, 2014 4:32 AM
Points: 514, Visits: 1,740
Thanks for article Roy.
i am considering turning on these features on an application we have at my current company, but had a question.

If i alter my database with;

ALTER DATABASE MyDatabase
SET ALLOW_SNAPSHOT_ISOLATION ON

ALTER DATABASE MyDatabase
SET READ_COMMITTED_SNAPSHOT ON

Do I need to alter all my existing stored procedures that make use of the
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED
statement?

also, the hint with (NOLOCK), should those also be removed?

Thanks.
Post #1244597
Posted Tuesday, January 31, 2012 10:55 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Friday, November 14, 2014 12:37 PM
Points: 2,361, Visits: 6,752
Yes, you will need to remove those hints that you have given. It will defeat the purpose.

-Roy
Post #1244609
Posted Thursday, May 31, 2012 1:31 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, June 10, 2013 2:42 PM
Points: 2, Visits: 21
I also got incorrect results. I could never get the other machine (or the local machine, for that matter) to show me the 2 once I had run transaction b.
Post #1309318
Posted Thursday, May 31, 2012 1:37 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, June 10, 2013 2:42 PM
Points: 2, Visits: 21
Huonglien Nguyen (3/6/2009)
I followed through the steps but eventhough after I executed "Commit tran a" the select * on dbo.test still showed me the old data: 1212121 and if I executed "Commit tran b" the select statement showed value 5. So I actually never saw the value 2 at all. Do you have any idea? Thanks.


I got the same results. The article seems very good and I have a much better understanding of SQL Server's row level versioning capabilities, but I got the same results here. Will continue reading for any insight into why this happens.

R
Post #1309325
« Prev Topic | Next Topic »

Add to briefcase «««12345

Permissions Expand / Collapse