The query has been canceled because the estimated cost of this query (1660) exceeds the configured threshold of 1500. Contact the system administrator

  • Have you traced to see what options are in effect (Ansi Null Default On, Ansi Nulls On, Ansi Padding On, Ansi Warnings On etc) at the point the SP is execute via the app?

    .Net apps can specify within the connection what option are available and if connection pooling is enabled then these can be cached (in a way).

  • Connection settings differences makes the most sense. Especially the ANSI standard settings. Differences there will absolutely result in different execution plans.

    "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 2 posts - 1 through 3 (of 3 total)

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