Skip to main content
Announcements
See why Qlik is a Leader in the 2024 Gartner® Magic Quadrant™ for Analytics & BI Platforms. Download Now
cancel
Showing results for 
Search instead for 
Did you mean: 
StaHorse
Contributor III
Contributor III

[ODBC Driver 13 for SQL Server][SQL Server]The query has been canceled because the estimated cost of this query (3066)

Hi,

I have this error from one of my Qlik jobs:

"[ODBC Driver 13 for SQL Server][SQL Server]The query has been canceled because the estimated cost of this query (3066) exceeds the configured threshold of 3000. Contact the system administrator."

Where can I increase it, Please help.

Labels (3)
2 Solutions

Accepted Solutions
Or
MVP
MVP

Sounds like you should contact your system administrator / DBA, or cut down on the query's estimated cost by improving it, adding indexes, reducing complexity, etc.

 

View solution in original post

Chip_Matejowsky
Support
Support

Hello @StaHorse,

This looks to be a SQL related issue and not a Qlik issue, as the error [SQL Server]The query has been canceled because the estimated cost of this query (3066) isn’t coming the QlikView side. I agree with @Or ‘s suggestion that you reach out to your organization’s DBA as they likely have configured things to not allow expensive queries. 

I did a Google search and found the below threads regarding the error you reported:

Best Regards

Principal Technical Support Engineer with Qlik Support
Help users find answers! Don't forget to mark a solution that worked for you!

View solution in original post

3 Replies
Or
MVP
MVP

Sounds like you should contact your system administrator / DBA, or cut down on the query's estimated cost by improving it, adding indexes, reducing complexity, etc.

 

StaHorse
Contributor III
Contributor III
Author

Where can I increase it?

Chip_Matejowsky
Support
Support

Hello @StaHorse,

This looks to be a SQL related issue and not a Qlik issue, as the error [SQL Server]The query has been canceled because the estimated cost of this query (3066) isn’t coming the QlikView side. I agree with @Or ‘s suggestion that you reach out to your organization’s DBA as they likely have configured things to not allow expensive queries. 

I did a Google search and found the below threads regarding the error you reported:

Best Regards

Principal Technical Support Engineer with Qlik Support
Help users find answers! Don't forget to mark a solution that worked for you!