NOLOCK and SQL Server... Perfect together?

I'm using NOLOCK on some search queries... some times I get this error message throught the day.

[Microsoft][ODBC SQL Server Driver][SQL Server]Could not continue scan with NOLOCK due to data movement

Is there anything I should lookup? I am also getting a ton of timeouts recently and I can not figure out why... not all of my connects are getting timeouts... just some of the search queries...

Any thoughts or directions would be mucho apprciated

Thanks

CrazyVBr

Well why are you using NOLOCK on this query? This message means another process is performing an INSERT/UPDATE/DELETE statement on the table, which leads to data being shuffled around. Hence it can't know what's new data and what's old and what's new and what's gone and returned so it just craps out. I could only assume this would be causeing the time outs as well but that's just a guess....

I'm using NOLOCK on Select statements becuase my data can change at any moment. My understanding of the NOLOCK is that I can get information back but only as 'dirty data'. That being if the information was being changed during the select (read) it would return only the information if read prior to the INSERT/UPDATE/DELETE was committed... but I could be wrong

I think I found that the READPAST hint might work.

Thanke for the response

CrazyVBr

CrazyVBr,

Your correct.. That's exacly how NOLOCK works.. If your getting an error, that may mean your query is doing more than a select. Would it be doing an insert into select?

http://support.microsoft.com/defaul...kb;en-us;235880

Looks like MS knows about it..

For the other guy..
NOLOCK (equivalent to READUNCOMMITTED) permits dirty reads. Dirty reads will not issue shared locks and will ignore exclusive locks placed by other processes. It is possible to receive error messages if the read takes place on an uncommitted transaction or a set of pages being rolled back.