The query processor could not produce a query plan because the name '%1!s!' in the FORCESEEK hint on table or view '%2!s!' did not match the key column names of the index '%3!s!'.
The query processor could not produce a query plan because the FORCESEEK hint on table or view '%1!s!' cannot be used with ...
The query processor could not produce a query plan because the FORCESEEK hint on table or view '%1!s!' cannot be used with ...
The query processor could not produce a query plan because the FORCESEEK hint on table or view '%1!s!' specified more seek ...
The query processor could not produce a query plan because the FORCESEEK hint on view '%1!s!' is used without a NOEXPAND ...
The query processor could not produce a query plan because the name '%1!s!' in the FORCESEEK hint on table or view '%2!s!' ...
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 ...
The query processor is unable to produce a plan. The table '%1!s!' is unavailable because the heap is corrupted. Take the ...