Skip to content

Query Processing & Performance errors

The optimizer cannot build a plan, recursion or nesting limits are hit, or SET options block an operation.

530 The maximum recursion has been exhausted before statement completionA recursive CTE went deeper than MAXRECURSION (default 100), or the data loops. 217 Maximum stored procedure, function, trigger or view nesting level exceededProcedures, functions or triggers called each other more than 32 levels deep. 1934 Statement failed because SET options have incorrect settingsQUOTED_IDENTIFIER, ANSI_NULLS or similar is wrong for a filtered index or indexed view. 1204 Cannot obtain a LOCK resource at this timeThe instance ran out of lock memory, usually one huge transaction holding millions of locks. 8622 Query processor could not produce a query plan because of the hintsHints such as FORCESEEK or HASH JOIN demand a plan that cannot exist for the query. 8623 The query processor ran out of internal resources and could not produce a query planOne statement is too complex or too large to optimise (huge IN lists, many tables or partitions). 8624 Internal Query Processor Error: could not produce a query planAn optimiser defect stops one statement from compiling; rewrite or simplify the query and apply the latest cumulative update.
No errors in this category match your search. Search the whole library.

Other categories