| title | MSSQLSERVER_601 | |
|---|---|---|
| description | MSSQLSERVER_601 | |
| author | MashaMSFT | |
| ms.author | mathoma | |
| ms.reviewer | randolphwest | |
| ms.date | 12/16/2024 | |
| ms.service | sql | |
| ms.subservice | supportability | |
| ms.topic | reference | |
| f1_keywords |
|
|
| helpviewer_keywords |
|
[!INCLUDE SQL Server]
| Attribute | Value |
|---|---|
| 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 [!INCLUDE ssDEnoversion] 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 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 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.