SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 SQL Server 2005 Forums
 Other SQL Server Topics (2005)
 SQL Server Error
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

JenniferK
Starting Member

2 Posts

Posted - 02/18/2013 :  07:18:48  Show Profile  Reply with Quote
Hi all,

Does anyone know what it means if you get this in your error logs:
SQL Error: 601, SQLState: S1000
Could not continue scan with NOLOCK due to data movement.

We are trying to publish from a content management system to a database which was working fine but has now stopped. We do not have many permissions on the database so do not know if the IT teams have changed something there end and just not told us.

Thanks.

James K
Flowing Fount of Yak Knowledge

3587 Posts

Posted - 02/18/2013 :  07:56:52  Show Profile  Reply with Quote
Are you on SQL 2000 or SQL 2005? If you are on SQL 2000 take a look at this page: http://support.microsoft.com/kb/815008

In either case, if at all possible, removing the NOLOCK hint on the query would be the first thing I would try.
Go to Top of Page

jackv
Flowing Fount of Yak Knowledge

United Kingdom
2039 Posts

Posted - 02/18/2013 :  08:17:10  Show Profile  Visit jackv's Homepage  Reply with Quote
do you have any sql statements running with NOLOCK. As well as user queries , look at VIEWS - where you may see a select statement with NOLOCK.?



Jack Vamvas
--------------------
http://www.sqlserver-dba.com
Go to Top of Page

JenniferK
Starting Member

2 Posts

Posted - 02/18/2013 :  09:08:47  Show Profile  Reply with Quote
We do not have the access to look at these items, it is our content management system trying to publish to a database that we do not have the access to look at or run queries on.
Go to Top of Page

James K
Flowing Fount of Yak Knowledge

3587 Posts

Posted - 02/18/2013 :  09:40:49  Show Profile  Reply with Quote
Without being able to look at the database and the queries that go into the database, there is no way that I know to fix the problem. If it is a vendor database, the best route would be to contact them. If it is an in-house database, the person(s) responsible for the database should be involved.
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.05 seconds. Powered By: Snitz Forums 2000