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 ««12

NOLOCK Hint Corrupts Results from SELECT Expand / Collapse
Author
Message
Posted Monday, November 26, 2012 7:51 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, September 9, 2014 12:16 PM
Points: 40, Visits: 456

Update:

We upgraded the production server to SP1, and the issue is gone. Lunch for anyone who can figure out why it was happening
Post #1388911
Posted Monday, November 26, 2012 11:32 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Tuesday, August 19, 2014 12:26 AM
Points: 2,840, Visits: 3,963
hisakimatama (11/8/2012)
If my understanding of the dirty reads process is correct, even if all transactions at a given time have been committed, page splits may still occur for a short time afterwards. If you query a table using NOLOCK during that time period and a page split occurs, the data will be shuffled around throughout the table to accomodate the split, and as such, you may end up with data returned from the NOLOCK operation that corresponds to a location in memory that doesn't hold the data you originally wanted. My understanding might be a little off, but the article should be much more succint
@gsquard , can you please put some light here


-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done
Post #1388963
Posted Wednesday, November 28, 2012 6:55 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Today @ 3:58 PM
Points: 4,359, Visits: 6,195
Langston Montgomery (11/26/2012)

Update:

We upgraded the production server to SP1, and the issue is gone. Lunch for anyone who can figure out why it was happening


Seems pretty obvious what was happening: you experienced the effects of a bug in the product that was fixed by the SQL Server patch you applied. End of story. Do I get a prize??


Best,

Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru at GMail
Post #1389742
Posted Wednesday, November 28, 2012 10:16 AM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: 2 days ago @ 6:01 PM
Points: 356, Visits: 871
It may not be a bad idea to have the server and other workstations check apply updates automatically to Windows and applications.
Post #1389960
Posted Wednesday, November 28, 2012 12:29 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, September 15, 2014 5:39 AM
Points: 2,694, Visits: 3,387
mmartin1 (11/28/2012)
It may not be a bad idea to have the server and other workstations check apply updates automatically to Windows and applications.
Yes it would. This should administered by a systems or domain administrator.


Thanks,

Jared
SQL Know-It-All

How to post data/code on a forum to get the best help - Jeff Moden
Post #1390062
Posted Wednesday, November 28, 2012 9:53 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, September 9, 2014 12:16 PM
Points: 40, Visits: 456
SQLKnowItAll (11/28/2012)
mmartin1 (11/28/2012)
It may not be a bad idea to have the server and other workstations check apply updates automatically to Windows and applications.
Yes it would. This should administered by a systems or domain administrator.


Thanks. We let Server Ops know
Post #1390271
Posted Wednesday, November 28, 2012 9:55 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, September 9, 2014 12:16 PM
Points: 40, Visits: 456
TheSQLGuru (11/28/2012)
Langston Montgomery (11/26/2012)

Update:

We upgraded the production server to SP1, and the issue is gone. Lunch for anyone who can figure out why it was happening


Seems pretty obvious what was happening: you experienced the effects of a bug in the product that was fixed by the SQL Server patch you applied. End of story. Do I get a prize??


Lol. You bet!
Post #1390272
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse