Contents
Why is SQL Server unable to continue scan with nolock?
The root cause of this error is because pages were deleted or moved by page splits caused by DML statements so that SQL Server is not able to continue scan operation. In order to verify that it is a page corruption issue you can run the DBCC CHECKDB command with PHYSICAL_ONLY option. DBCC CHECKDB (MY_DATABASE) WITH PHYSICAL_ONLY.
Why is MY SQL Server in nolock mode?
SQL Server Management Studio also sends SQL statements to the database, likely in the NOLOCK / READ UNCOMMITTED mode to not block tables. If a change to the table occurs while being read in this mode, the SQL command may run into this error.
Why is MY SQL Server engine not working?
If the other machine’s SSMS gets the same error when connecting to the laptop’s engine, then uninstall and reinstall the SQL Server engine on the affected laptop. (It’s some type of corruption issue, and not worth the $500 MS support call to troubleshoot – if it was a production server, I’d answer otherwise.)
Can you continue scan with nolock due to data movement?
Could not continue scan with NOLOCK due to data movement. The query that throws this error is a large complex query that joins over a dozen tables. Our underlying data can be updated frequently. The cultural ‘best-practice’ is that, in the past, introduction of NOLOCK hints increased performance and improved concurrency.
When do you delete a row in nolock?
More precisely, the row has to be deleted after process B reads the index, but before it attempts to read the data row. If that doesn’t work, you have the slightly more painful option of removing all your WITH (NOLOCK) hints and setting your transaction isolation level to something above READ UNCOMMITTED.
Why is there an error message in SQL Server?
This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online. The error message indicates that there is an error during a READ operation.