SQL Server Errors or Failures from Error: 8668 to Error: 8690

SQLServerF1

 

Error: 8668, Severity: 16, Cannot create the clustered index ‘%.*ls’ on view ‘%.*ls’ because the select list of the view contains an expression on result of aggregate function or grouping column. Consider removing expression on result of aggregate function or grouping column from s
Error: 8669, Severity: 16, The attempt to maintain the indexed view “%.*ls” failed because it contains an expression on aggregate results, or because it contains a ranking or aggregate window function. Consider dropping the clustered index on the view, or changing the view definiti
Error: 8670, Severity: 16, Query optimizer reached the internal limit of the maximum number of views that can be used during optimization.

Error: 8671, Severity: 16, The attempt to maintain the indexed view “%.*ls” failed because of the ignore_dup_key option on index “%.*ls”. Drop the index or re-create it without the ignore_dup_key index option.
Error: 8672, Severity: 16, The MERGE statement attempted to UPDATE or DELETE the same row more than once. This happens when a target row matches more than one source row. A MERGE statement cannot UPDATE/DELETE the same row of the target table multiple times. Refine the ON clause to
Error: 8673, Severity: 16, A MERGE statement is not valid if it triggers both the ‘ON DELETE SET NULL’ and ‘ON UPDATE CASCADE’ actions for a referential integrity constraint. Modify the actions performed by the MERGE statement to ensure that it does not trigger both these actions f
Error: 8674, Severity: 16, The query processor is unable to produce a plan. The table ‘%.*ls’ is unavailable because the heap is corrupted. Take the database offline to rebuild the table and heap, and then run the query processor again.

Error: 8675, Severity: 17, A timeout occurred while waiting for remote memory resources to execute the query in resource pool ‘%ls’ (%ld). Rerun the query.
Error: 8676, Severity: 16, Invalid plan.
Error: 8680, Severity: 17, Internal Query Processor Error: The query processor encountered an unexpected error during the processing of a remote query phase.
Error: 8681, Severity: 17, Internal Query Processor Error: The query processor encountered an unexpected error during processing. [%ls]
Error: 8682, Severity: 16, SELECT via cursor failed because in XML plan provided to USE PLAN hint, neither Populate nor Fetch plans are provided, and at least one must be present. For best likelihood of successful plan forcing, use an XML cursor plan captured from SQL Server withou
Error: 8683, Severity: 16, Could not force query plan because XML showplan provided in USE PLAN hint contains invalid Star Join specification. Consider specifying a USE PLAN hint that contains an unmodified XML showplan produced by SQL Server. This may allow you to force the plan.
Error: 8684, Severity: 16, A query plan could not be found because optimizer exceeded number of allowed operations while searching for plan specified in USE PLAN hint. First consider removing USE PLAN hint. Then if necessary consider (1) updating statistics, (2) using other hints s
Error: 8685, Severity: 16, Query cannot be compiled because element appears in XML plan provided to USE PLAN but USE PLAN was applied to a non-cursor statement. Consider using an XML plan obtained from SQL Server for statement without modification.
Error: 8686, Severity: 16, Cursor plan forcing failed because input plan has more than one node with OperationType=%ls. Consider using an XML cursor plan captured from SQL Server without modification.
Error: 8687, Severity: 16, Cursor plan failed because it is not possible to force the plan for a cursor of type other than FAST_FORWARD or STATIC with a USE PLAN hint. Consider removing USE PLAN hint and updating statistics or using different hints to influence query plan choice.
Error: 8688, Severity: 16, Cursor plan forcing failed because in XML plan provided to USE PLAN, required element %ls is missing under element. Consider using an XML cursor plan captured from SQL Server without modification.
Error: 8689, Severity: 16, Database ‘%.*ls’, specified in the USE PLAN hint, does not exist. Specify an existing database.
Error: 8690, Severity: 16, Query cannot be compiled because USE PLAN hint conflicts with hint %ls. Consider removing hint %ls.

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 *