SQL Server Errors or Failures from Error: 8636 to Error: 8665

SQLServerF1

 

Error: 8636, Severity: 16, The query processor could not produce a query plan because there is a subquery in the predicate of the full outer join. This is not supported for distributed queries.
Error: 8637, Severity: 16, The query processor could not produce a query plan because a USE PLAN hint was used for a query that modifies data while the target table of the modification has an index that is currently being built online. Consider waiting until the online index build
Error: 8642, Severity: 17, The query processor could not start the necessary thread resources for parallel query execution.

Error: 8644, Severity: 16, Internal Query Processor Error: The plan selected for execution does not support the invoked given execution routine.
Error: 8645, Severity: 17, A timeout occurred while waiting for memory resources to execute the query in resource pool ‘%ls’ (%ld). Rerun the query.
Error: 8646, Severity: 21, Unable to find index entry in index ID %d, of table %d, in database ‘%.*ls’. The indicated index is corrupt or there is a problem with the current update plan. Run DBCC CHECKDB or DBCC CHECKTABLE. If the problem persists, contact product support.
Error: 8648, Severity: 20, Could not insert a row larger than the page size into a hash table. Resubmit the query using the ROBUST PLAN optimization hint.
Error: 8649, Severity: 17, The query has been canceled because the estimated cost of this query (%d) exceeds the configured threshold of %d. Contact the system administrator.
Error: 8651, Severity: 17, Could not perform the operation because the requested memory grant was not available in resource pool ‘%ls’ (%ld). Rerun the query, reduce the query load, or check resource governor configuration setting.

Error: 8653, Severity: 16, The query processor is unable to produce a plan for the table or view ‘%.*ls’ because the table resides in a filegroup which is not online.
Error: 8655, Severity: 16, The query processor is unable to produce a plan because the index ‘%.*ls’ on table or view ‘%.*ls’ is disabled.
Error: 8656, Severity: 16, The query processor could not produce a query plan. Resubmit the query after disabling trace flag %d.
Error: 8657, Severity: 17, Could not get the memory grant of %I64d KB because it exceeds the maximum configuration limit in workload group ‘%ls’ (%ld) and resource pool ‘%ls’ (%ld). Contact the server administrator to increase the memory usage limit.
Error: 8658, Severity: 17, Cannot start the columnstore index build because it requires at least %I64d KB, while the maximum memory grant is limited to %I64d KB per query in workload group ‘%ls’ (%ld) and resource pool ‘%ls’ (%ld). Retry after modifying columnstore index to contain
Error: 8659, Severity: 16, Cannot create the clustered index “%.*ls” on view “%.*ls” because for clustered indexes on aggregate views without GROUP BY, the only distribution option supported is DISTRIBUTION=NONE.
Error: 8660, Severity: 16, Cannot create the clustered index “%.*ls” on view “%.*ls” because the select list of the view definition does not include all columns in the GROUP BY clause. Consider adding these columns to the select list.
Error: 8661, Severity: 16, Cannot create the clustered index “%.*ls” on view “%.*ls” because the index key includes columns that are not in the GROUP BY clause. Consider eliminating columns that are not in the GROUP BY clause from the index key.
Error: 8662, Severity: 16, Cannot create the clustered index “%.*ls” on view “%.*ls” because the view references an unknown value (SUM aggregate of nullable expression). Consider referencing only non-nullable values in SUM. ISNULL() may be useful for this.
Error: 8663, Severity: 16, Cannot create the clustered index “%.*ls” on view “%.*ls” because its select list does not include COUNT_BIG(*). Consider adding COUNT_BIG(*) to the select list.
Error: 8665, Severity: 16, Cannot create the clustered index “%.*ls” on view “%.*ls” because no row can satisfy the view definition. Consider eliminating contradictions from the view definition.

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 *