601

ﾃ

Product Name

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 can’t continue executing the query because it’s trying to read

data that was updated or deleted by another transaction. The query is using either the

locking hint or the

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

locking hint and

transaction

isolation level let a query read data that is locked by another transaction. This scenario is

referred to as a

dirty read

, because you can read values that aren’t yet committed and that are

subject to change.

This error cancels the query. Either resubmit the query or

remove the NOLOCK locking hint.

Alternatively, use an appropriate

isolation level

such as

(the default) or

to avoid dirty reads while preventing this error.

ﾉ

Expand table

NOLOCK
READ UNCOMMITTED
NOLOCK
READ UNCOMMITTED
READ COMMITTED