Problem with NOLOCK on SQL 2008 using a temporary table and selecting statements

Question

I use SQL 2008, and I get the error most of the time when I start the stored procedure. Error: could not continue scan with nolock due to data movement . I looked online for this, and it seems that most people get this when updating their version of SQL or when performing updates / deletes. I don’t do that either. Also, the solution seems to have to remove NOLOCK, but I do not use NOLOCK (unless it is used by default in SQL Server 2008). I also tried to insert SET TRANSACTION ISOLATION LEVEL READ uncommitted , but it did not make any changes.

My stored procedure consists of retrieving parameters, creating a temporary table, filling the table with SELECT statements only, and then retrieving information from the table.

Does anyone know what is wrong?

Answer 1

There is a fix for SQL Server 2008: FIX: You get error 605 and error 824 when you run a query that inserts data into a temporary table in SQL Server

(fixed link. oops)