The query processor could not produce a query plan because a USE PLAN hint was used for a query that modifies data while the target table of the modification has an index that is currently being built online. Consider waiting until the online index build is done before forcing the plan, or using another way to tune the query, such as updating statistics, or using a different hint or a manual query rewrite.
The query designer could not be loaded. Verify your connection string and query string or enter a valid query to continue. ...
The query has been canceled because the estimated cost of this query (%1!s!) exceeds the configured threshold of %2!s!. Contact ...
The query has exceeded the maximum number of result sets that can be displayed in the results grid. Only the first {0} result ...
The query must have at least one axis. The first axis of the query should not have multiple hierarchies, nor should it reference ...
The query processor could not produce a query plan because a USE PLAN hint was used for a query that modifies data while ...
The query processor could not produce a query plan because a worktable is required, and its minimum row size exceeds the ...
The query processor could not produce a query plan because a worktable is required, and its minimum row size exceeds the ...
The query processor could not produce a query plan because distributed query does not support materializing intermediate ...
The query processor could not produce a query plan because there is a subquery in the predicate of the full outer join. This ...