SQL Server Performance

Could not continue scan with nolock Due to data movement

Discussion in 'SQL Server 2005 Performance Tuning for DBAs' started by sridevi kodali, Oct 4, 2011.

  1. sridevi kodali New Member

    we are using Idera monitoring tool for servers. everyday morning we are getting this
    error :
    Error executing Table Growth Collector: Could not continue scan with NOLOCK due to data movement.
    I have checked if they are any jobs or query running at that time. I found none but, transaction log backup jobs are running. I alo checked if any query running with nolock hint.I found none. Can you please help me wih this issue.
  2. FrankKalis Moderator

    Welcome to the forum!
    You can find many references to this error message on the internet, but I would check with Idera what they suggest in that situation. In the end it seems to be their software having some sort of issue.
  3. satya Moderator

    Identify at what time and what process is generating thsi alert, may be a server side trace would help.
    This happens due to TRANSACTION ISOLATION level setting. such as SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED

    What version of SQL Server are you using?

Share This Page