SQL Server Errors or Failures from Error: 8691 to Error: 8726

SQLServerF1

 

Error: 8691, Severity: 16, Query cannot be compiled because USE PLAN hint conflicts with SET %ls ON. Consider setting %ls OFF.
Error: 8693, Severity: 16, Cannot compile query because combination of LogicalOp = ‘%ls’, PhysicalOp = ‘%ls’, and sub_element = ‘%ls’ under RelOp element in XML plan in USE PLAN hint is not valid. Use a recognized combination instead. Consider using an automatically generated XML p
Error: 8694, Severity: 16, Cannot execute query because USE PLAN hint conflicts with use of distributed query or full-text operations. Consider removing USE PLAN hint.
Error: 8695, Severity: 16, Cannot execute query because of incorrectly formed XML plan in USE PLAN hint. Verify that XML plan is a legal plan suitable for plan forcing. See Books Online for additional details.

Error: 8696, Severity: 16, Cannot run query because of improperly formed Spool element with parent RelOp with NodeId %d in XML plan in USE PLAN hint. Verify that each Spool element’s parent RelOp has unique NodeId attribute, and each Spool element has either a single RelOp sub-elem
Error: 8697, Severity: 16, Cannot run query because in XML plan provided to USE PLAN, element %ls must have %d %ls nodes as children, but has %d.
Error: 8698, Severity: 16, Query processor could not produce query plan because USE PLAN hint contains plan that could not be verified to be legal for query. Remove or replace USE PLAN hint. For best likelihood of successful plan forcing, verify that the plan provided in the USE PL
Error: 8699, Severity: 16, Cannot run query because it contains more than one USE PLAN hint. Use at most one USE PLAN hint.

Error: 8709, Severity: 16, Error due to negative or NULL window delimiter.
Error: 8710, Severity: 16, Aggregate functions that are used with CUBE, ROLLUP, or GROUPING SET queries must provide for the merging of subaggregates. To fix this problem, remove the aggregate function or write the query using UNION ALL over GROUP BY clauses.
Error: 8711, Severity: 16, Multiple ordered aggregate functions in the same scope have mutually incompatible orderings.
Error: 8712, Severity: 16, Index ‘%.*ls’, specified in the USE PLAN hint, does not exist. Specify an existing index, or create an index with the specified name.
Error: 8713, Severity: 16, Could not force query plan because of a problem in an indexed view referenced in the plan.
Error: 8720, Severity: 15, Cannot execute query. There is more than one TABLE HINT clause specified for object ‘%.*ls’. Use at most one such TABLE HINT clause per table reference.
Error: 8721, Severity: 15, Cannot execute query. TABLE HINT in the OPTION clause leads to ambiguous reference for object ‘%.*ls’. Consider USE PLAN query hint instead.
Error: 8722, Severity: 15, Cannot execute query. Semantic affecting hint ‘%.*ls’ appears in the ‘%.*ls’ clause of object ‘%.*ls’ but not in the corresponding ‘%.*ls’ clause. Change the OPTION (TABLE HINTS…) clause so the semantic affecting hints match the WITH clause.
Error: 8723, Severity: 15, Cannot execute query. Object ‘%.*ls’ is specified in the TABLE HINT clause, but is not used in the query or does not match the alias specified in the query. Table references in the TABLE HINT clause must match the WITH clause.
Error: 8724, Severity: 15, Cannot execute query. Table-valued or OPENROWSET function ‘%.*ls’ cannot be specified in the TABLE HINT clause.
Error: 8725, Severity: 17, Subproc thread aborted during parallel query execution.
Error: 8726, Severity: 16, Input parameter of %.*ls function must be a constant.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

Leave a Reply

Your email address will not be published. Required fields are marked *