The query processor could not produce a query plan because a worktable is required, and its minimum row size exceeds the maximum allowable of %1!s! bytes. A typical reason why a worktable is required is a GROUP BY or ORDER BY clause in the query. If the query has a GROUP BY or ORDER BY clause, consider reducing the number and/or size of the fields in the clause. Consider using prefix (LEFT()) or hash (CHECKSUM()) of fields for grouping or prefix for ordering. Note however that this will change the behavior of the query.
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 ...
The query processor could not produce a query plan for a query with a spatial index hint. Reason: %1!s!. Try removing the ...
The query processor is unable to produce a plan for the table or view '%1!s!' because the table resides in a filegroup which ...