May 5, 2009 at 12:44 am
Hi,
The sql which is running using sql server agent produces the below error:
"The query has been canceled because the estimated cost of this query (3373) exceeds the configured threshold of 300"
We have never encountered the above error, so far.
Running the sql at backend does not produce any error. Also, have checked the query governor property (which is set 300)
Appreciate any help!!!
Thanks in advance...
May 5, 2009 at 1:26 am
Hello,
Is it possible that somebody e.g. a SQL Server Administrator, has recently changed the query governor cost limit?
I am just wondering why your job was working before, and not now. Have there been any other major changes on the Server e.g. a large increase in data volume or removal of indexes that might cause the job to run a lot longer than before?
Regards,
John Marsh
www.sql.lu
SQL Server Luxembourg User Group
May 5, 2009 at 2:06 am
No, I dont think anyone has changed the query cost time...
Even after increasing query cost to 1200, there was no difference...
Now, even the sql's (using except) are not running in backend. So i have changed query governor setting to 0 and remote query timeout to 0
May 5, 2009 at 2:08 am
I had increased query cost to 1200, there was no difference... Now, even the sql's (using except) are not running in backend.
So i have changed query governor setting to 0 and remote query timeout to 0 which seems to have solved teh problem...Am not sure if anyone has changed the query cost time,earlier...
Thanks..
May 5, 2009 at 6:48 am
Just a question, why have the governor in place at all if you're going to remove the limits as soon as you hit them?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply