Setting Query Governor to zero Not having any effect

  • Hello Experts,

    I am trying to do a database upgrade using our internal .net based application. When I run it on the clients SQL ServerExpress 2012 I get

    "The query has been canceled because the estimated cost of this query exceeds the configured threshold of xx"

    I restored the DB to an instance of SQL ServerExpress 2012 on my own machine and got the same error.

    I went into Server, Connections and unticked "Use query governor to prevent long-running queries".

    I then successfully did the update.

    I did the same on the client server, restarting the SQL server service after making the change and still get the original error.

    The setting on my instance and theirs appear to be the same. The only difference I can see is their instance SP3 and mine is RTM.

    Any suggestions most welcome.

  • It's not clear what versions you are on but...did you check sp_configure values on both servers? I'd double check the query governor cost limit settings. Check run and config values.

    Sue

  • Hi Sue,

    Thanks for your response.

    The client is on SQL Server Express 2012 SP3 and my local copy is SQL Server Express 2012 RTM.

    I used sp_configure with show advanced options on and the settings are identical except for max server memory (MB).

    I changed the max server memory settings and re-ran sp_configure.

    I copied the results out of SSMS and into txt files and used windiff to ensure they were identical.

    I re-ran the job and still got "The query has been canceled because the estimated cost of this query (1000221) exceeds the configured threshold of 10000".

    So, I'm at a loss.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply