TechNet
Export (0) Print
Expand All

MSSQLSERVER_601

Topic Status: Some information in this topic is preview and subject to change in future releases. Preview information describes new features or changes to existing features in Microsoft SQL Server 2016 Community Technology Preview 2 (CTP2).

Product Name

SQL Server

Event ID

601

Event Source

MSSQLSERVER

Component

SQLEngine

Symbolic Name

Message Text

Could not continue scan with NOLOCK due to data movement.

The SQL Server Database Engine cannot continue executing the query because it is trying to read data that was updated or deleted by another transaction. The query is using either the NOLOCK locking hint or the READ UNCOMMITTED transaction isolation level.

Typically, access to data that is being changed by another transaction is denied because of locks put on the data. However, the NOLOCK locking hint and READ UNCOMMITTED transaction isolation level let a query read data that is locked by another transaction. This is referred to as a dirty read because you can read values that have not yet been committed and that are subject to change.

This error cancels the query. Either resubmit the query or remove the NOLOCK locking hint.

Community Additions

Show:
© 2016 Microsoft