SQL Server Errors or Failures from Error: 8604 to Error: 8635

SQLServerF1

 

Error: 8604, Severity: 16, ALTR TABLE SWITCH statement failed. Table ‘%.*ls’ has a column level check constraint ‘%.*ls’ on column ‘%.*ls’ that is not loadable for semantic validation.
Error: 8605, Severity: 10, Index creation operation will use %ld KB of memory specified in the advanced sp_configure option “min memory per query (KB)” instead of %lu KB specified in “index create memory (KB)” option because the former has to be smaller than the latter.
Error: 8606, Severity: 17, This index operation requires %I64d KB of memory per DOP. The total requirement of %I64d KB for DOP of %lu is greater than the sp_configure value of %lu KB set for the advanced server configuration option “index create memory (KB)”. Increase this setting

Error: 8607, Severity: 16, The table ‘%.*ls’ cannot be modified because one or more non-clustered indexes reside in a filegroup which is not online.
Error: 8608, Severity: 16, The query could not be completed due to an online index build operation and must be recompiled.
Error: 8616, Severity: 10, The index hints for table ‘%.*ls’ were ignored because the table was considered a fact table in the star join.
Error: 8618, Severity: 16, The query processor could not produce a query plan because a worktable is required, and its minimum row size exceeds the maximum allowable of %d bytes. A typical reason why a worktable is required is a GROUP BY or ORDER BY clause in the query. If the quer
Error: 8619, Severity: 16, The query processor could not produce a query plan because a worktable is required, and its minimum row size exceeds the maximum allowable of %d bytes. A typical reason why a worktable is required is a GROUP BY or ORDER BY clause in the query. Resubmit yo

Error: 8621, Severity: 16, The query processor ran out of stack space during query optimization. Please simplify the query.
Error: 8622, Severity: 16, Query processor could not produce a query plan because of the hints defined in this query. Resubmit the query without specifying any hints and without using SET FORCEPLAN.
Error: 8623, Severity: 16, The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions. Please simplify the query. If
Error: 8624, Severity: 16, Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services.
Error: 8625, Severity: 10, Warning: The join order has been enforced because a local join hint is used.

Error: 8628, Severity: 17, State: 0

A time out occurred while waiting to optimize the query. Rerun the query.

This error can occur due to memory pressure on the server and on SQL Server. Check for the processes running and memory used by the processes and make sure there is enough memory for SQL Server to operate.

Error: 8630, Severity: 17, Internal Query Processor Error: The query processor encountered an unexpected error during execution (HRESULT = 0x%x).
Error: 8631, Severity: 17, Internal error: Server stack limit has been reached. Please look for potentially deep nesting in your query, and try to simplify it.
Error: 8632, Severity: 17, Internal error: An expression services limit has been reached. Please look for potentially complex expressions in your query, and try to simplify them.
Error: 8633, Severity: 16, 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
Error: 8634, Severity: 17, The query processor received an error from a cluster communication layer.
Error: 8635, Severity: 16, The query processor could not produce a query plan for a query with a spatial index hint. Reason: %S_MSG. Try removing the index hints or removing SET FORCEPLAN.

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 *