5

I am using SQL 2008 and I am getting an error most of the time I run a stored procedure. There error is: could not continue scan with nolock due to data movement. I have looked online for this and it seems that most people get this when updating their SQL version or when doing updates/deletes. I am not doing either. Also the solution seems to be to remove the NOLOCK yet I am not using NOLOCK (unless it is default in SQL Server 2008). I have also tried to insert SET TRANSACTION ISOLATION LEVEL READ uncommitted yet it hasn't made any changes.

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

Does anyone know what is wrong?

3
  • Adding the stored procedure code might help. Commented Apr 1, 2011 at 16:04
  • Kyra: can you post a code sample for us to look at? Commented Apr 1, 2011 at 16:28
  • First time when it's not my bug :))) Commented Dec 5, 2012 at 10:02

1 Answer 1

6

There's a patch for that in SQL server 2008: FIX: You receive error 605 and error 824 when you run a query that inserts data into a temporary table in SQL Server

(fixed link. oops)

Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.