The query processor could not produce a query plan because distributed query does not support materializing intermediate results with default in DML queries over remote sources. Try to use actual default values instead of default or split the update into multiple statements, one only containing the DEFAULT assignment, the other with the rest.
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 ...
The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected ...