Errors 8000 - 8999

8001

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Meta-information is invalid for the Sql Variant parameter.

8003

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Too many parameters were provided in this RPC request. The maximum is %d.

8005

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d: The parameter name is invalid.

8007

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): The chunking format is incorrect for a large object parameter of type 0x%02X.

8009

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X is unknown.

8011

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X (sql_variant) has an invalid length for type-specific metadata.

8013

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X (sql_variant) has an invalid instance length.

8015

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X is an untyped NULL but is marked as an output parameter.

8017

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X has an invalid precision or scale.

8019

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type "0x%02X" (CLR type) has an invalid user type specified.

8021

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type "0x%02X" (CLR type) has an invalid database specified.

8023

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): The supplied value is not a valid instance of data type %.*ls. Check the source data for invalid values. An example of an invalid value is data of numeric type with scale greater than precision.

8025

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): The RPC is marked with the metadata unchanged flag, but data type 0x%02X has a maximum length different from the one sent last time.

8027

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type "0x%02X" (CLR type) has an invalid schema specified.

8029

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) unexpected token encountered processing a table-valued parameter.

8031

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: The chunking format is incorrect for a large object parameter of data type 0x%02X.

8033

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (sql_variant) has an invalid length for type-specific metadata.

8035

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (sql_variant) has an invalid instance length.

8037

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X has an invalid data length or metadata length.

8039

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (CLR type) has an invalid user type specified.

8041

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (CLR type) has an invalid database specified.

8043

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: The supplied value is not a valid instance of data type %.*ls. Check the source data for invalid values. An example of an invalid value is data of numeric type with scale greater than precision.

8045

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (CLR type) has an invalid schema specified.

8047

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has a non-zero length database name specified. Database name is not allowed with a table-valued parameter, only schema name and type name are valid.

8049

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has an invalid type name specified.

8051

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has an invalid column name specified.

8053

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has an invalid column flag specified.

8055

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has invalid column ordering metadata specified.

8057

16

No

Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type). The specified column is computed or default and has ordering or uniqueness set. Ordering and uniqueness can only be set on columns that have client supplied data.

8059

16

No

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter "%.*ls", to a parameterized string has no table type defined.

8061

16

No

The data for table-valued parameter "%.*ls" doesn't conform to the table type of the parameter.

8063

16

No

The incoming tabular data stream (TDS) remote procedure call stream is sending an unlimited length CLR type. Parameter %d ("%.*ls") is defined as type %.*ls. This type is not supported by down-level clients. Send the serialized data of the large CLR type as varbinary(max), or upgrade the client driver to one that supports unlimited CLR types.

8101

16

No

An explicit value for the identity column in table '%.*ls' can only be specified when a column list is used and IDENTITY_INSERT is ON.

8105

16

No

'%.*ls' is not a user table. Cannot perform SET operation.

8107

16

No

IDENTITY_INSERT is already ON for table '%.*ls.%.*ls.%.*ls'. Cannot perform SET operation for table '%.*ls'.

8109

16

No

Attempting to add multiple identity columns to table '%.*ls' using the SELECT INTO statement.

8111

16

No

Cannot define PRIMARY KEY constraint on nullable column in table '%.*ls'.

8113

16

No

Incorrect use of the XML data type method '%.*ls'. A mutator method is expected in this context.

8115

16

No

Arithmetic overflow error converting %ls to data type %ls.

8117

16

No

Operand data type %ls is invalid for %ls operator.

8119

16

No

Column '%.*ls.%.*ls' is invalid in the HAVING clause because it is not contained in an aggregate function and there is no GROUP BY clause.

8121

16

No

Column '%.*ls.%.*ls' is invalid in the HAVING clause because it is not contained in either an aggregate function or the GROUP BY clause.

8124

16

No

Multiple columns are specified in an aggregated expression containing an outer reference. If an expression being aggregated contains an outer reference, then that outer reference must be the only column referenced in the expression.

8126

16

No

Column "%.*ls.%.*ls" is invalid in the ORDER BY clause because it is not contained in an aggregate function and there is no GROUP BY clause.

8128

10

Yes

Using '%s' version '%s' to execute extended stored procedure '%s'. This is an informational message only; no user action is required.

8131

10

Yes

Extended stored procedure DLL '%s' does not export __GetXpVersion(). Refer to the topic "Backward Compatibility Details (Level 1) - Open Data Services" in the documentation for more information.

8133

16

No

None of the result expressions in a CASE specification can be NULL.

8135

16

No

Table level constraint does not specify column list, table '%.*ls'.

8137

16

No

Incorrect use of the XML data type method '%.*ls'. A non-mutator method is expected in this context.

8139

16

No

Number of referencing columns in foreign key differs from number of referenced columns, table '%.*ls'.

8141

16

No

Column %ls constraint for column '%.*ls' references another column, table '%.*ls'.

8144

16

No

Procedure or function %.*ls has too many arguments specified.

8146

16

No

Procedure %.*ls has no parameters and arguments were supplied.

8148

16

No

More than one column %ls constraint specified for column '%.*ls', table '%.*ls'.

8150

16

No

Multiple NULL constraints were specified for column '%.*ls', table '%.*ls'.

8152

16

No

String or binary data would be truncated.

8154

15

No

The table '%.*ls' is ambiguous.

8156

15

No

The column '%.*ls' was specified multiple times for '%.*ls'.

8159

15

No

'%.*ls' has fewer columns than were specified in the column list.

8161

15

No

Argument %d of the %.*ls function does not match any of the expressions in the GROUP BY clause.

8164

16

No

An INSERT EXEC statement cannot be nested.

8166

16

No

Constraint name '%.*ls' not permitted. Constraint names cannot begin with a number sign (#).

8168

16

No

Cannot create, drop, enable, or disable more than one constraint, column, or trigger named '%.*ls' in this context. Duplicate names are not allowed.

8170

16

No

Insufficient result space to convert uniqueidentifier value to char.

8172

16

No

The argument %d of the XML data type method "%.*ls" must be a string literal.

8174

16

No

Schema lock with handle %d not found.

8176

16

No

Resync procedure expects value of key '%.*ls', which was not supplied.

8178

16

No

The parameterized query '%.*ls' expects the parameter '%.*ls', which was not supplied.

8180

16

No

Statement(s) could not be prepared.

8183

16

No

Only UNIQUE or PRIMARY KEY constraints can be created on computed columns, while CHECK, FOREIGN KEY, and NOT NULL constraints require that computed columns be persisted.

8185

16

No

Error expanding "*": An incomparable column has been found in an underlying table or view.

8187

16

Yes

The prepared handle %d is currently being used by another command (error state: %d).

8189

16

No

You do not have permission to run '%ls'.

8191

16

No

Replication filter procedures can only contain SELECT, GOTO, IF, WHILE, RETURN, and DECLARE statements.

8193

16

No

Cannot execute a procedure marked FOR REPLICATION.

8196

16

No

Duplicate column specified as ROWGUIDCOL.

8199

16

No

In EXECUTE <procname>, procname can only be a literal or variable of type char, varchar, nchar, or nvarchar.

8302

10

No

CREATE RULE and DROP RULE will be removed in a future version of SQL Server. Avoid using CREATE RULE and DROP RULE in new development work, and plan to modify applications that currently use them. Use check constraints instead, which are created using the CHECK keyword of CREATE TABLE or ALTER TABLE.

8304

10

No

INDEXKEY_PROPERTY will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use the feature. Use sys.index_columns instead.

8306

10

No

Use of level0type with value 'TYPE' in procedure sp_addextendedproperty, sp_updateextendedproperty and sp_dropextendedproperty and in table-valued function fn_listextendedproperty has been deprecated and will be removed in a future version of SQL Server. Types are now schema scoped and hence use level0type with value 'SCHEMA' and level1type with value 'TYPE' for extended properties on TYPE.

8308

10

No

USER_ID will be removed from a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use the feature. Use DATABASE_PRINCIPAL_ID instead.

8311

16

No

Unable to map view of file mapping object '%ls' into SQL Server process address space. SQL Server performance counters are disabled.

8313

16

No

Error in mapping SQL Server performance object/counter indexes to object/counter names. SQL Server performance counters are disabled.

8315

16

No

SQL Server performance counter '%ls' not found in registry. SQL Server performance counters are disabled.

8317

16

No

Cannot query value '%ls' associated with registry key 'HKLM\%ls'. SQL Server performance counters are disabled.

8319

16

No

Windows kernel object '%ls' already exists. It's not owned by the SQL Server service account. SQL Server performance counters are disabled.

8350

10

No

Use of NOLOCK or READUNCOMMITTED hints in the FROM clause of an UPDATE or DELETE statement on the target table of the statement ('%.*ls') is deprecated. These hints have no effect in this location. Microsoft recommends that you remove these hints from this statement. Support for these hints in this location will be removed in a future version of SQL Server.

8352

16

Yes

Cannot find the requested trace template: id = %ls.

8354

16

Yes

Event Tracing for Windows failed to send an event. Send failures with the same error code may not be reported in the future. Error ID: %d, Event class ID: %d, Cause: %ls.

8356

16

Yes

Event Tracing for Windows (ETW) failed to send event. The server has run out of memory. The same send failure may not be reported in the future.

8358

16

Yes

Event Tracing for Windows (ETW) failed to send event. Event message size exceeds limit. The same send failure may not be reported in the future.

8360

16

Yes

SQL Trace failed to send event notification. This may be due to low resource conditions. The same send failure may not be reported in the future.

8380

10

No

SQLOLEDB is no longer a supported provider. Please use SQL Native Client (SQLNCLI) to connect to SQL Server using linked server '%.*ls'.

8382

10

No

Specifying table hints without using a WITH keyword is a deprecated feature and will be removed in a future version.

8384

10

No

Use of space as a separator for table hints is a deprecated feature and will be removed in a future version. Use a comma to separate individual table hints.

8386

10

No

Use of hint "%.*ls" on the target table of INSERT is deprecated because it may be removed in a future version of SQL Server. Modify the INSERT statement to remove the use of this hint.

8388

10

No

The ability to return results from triggers will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it.

8390

10

No

The '::' function calling syntax will be removed in a future version of SQL Server. Replace it with "sys.".

8393

10

No

The ability to not specify a column name when the datatype is timestamp will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it.

8396

10

No

%ls will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. Use %ls instead.

8398

10

No

The use of more than two-part column names will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it.

8401

16

No

This message could not be delivered because the target user with ID %i in database ID %i does not have permission to receive from the queue '%.*ls'.

8403

16

No

The message type '%.*ls' is specified more than once. Remove the duplicate message type.

8405

16

No

An error occurred in the service broker queue rollback handler, while trying to disable a queue. Database ID: %d, Queue ID: %d, Error: %i, State: %i.

8407

16

No

Received a message that contains invalid header fields. This may indicate a network problem or that another application is connected to the Service Broker endpoint.

8409

16

No

This message could not be delivered because the targeted service does not support the service contract. Targeted service: '%.*ls', service contract: '%.*ls'.

8411

16

No

The dialog lifetime value of %d is outside the allowable range of %d to %d. Specify a valid dialog lifetime value.

8413

16

No

The syntax of the broker instance '%.*ls' is invalid. The specified broker instance is too long, the maximum size is 256 bytes.

8415

16

No

The activated task was aborted because the invoked stored procedure '%ls' did not issue COMMIT or ROLLBACK on one or more transactions that it begun.

8418

16

No

The conversation handle is missing. Specify a conversation handle.

8420

16

No

The conversation group is missing. Specify a conversation group.

8422

16

No

The error description is missing. Specify a description of the error.

8424

16

No

The error code and error description are missing. Specify both the error code and description of the error.

8426

16

No

The conversation handle "%.*ls" is not found.

8428

16

No

The message type "%.*ls" is not found.

8430

16

No

The message body failed the configured validation.

8432

16

No

The message cannot be sent because the message type '%.*ls' is marked SENT BY TARGET in the contract, however this service is an Initiator.

8434

16

No

The message cannot be sent because the message type '%.*ls' is marked SENT BY INTITIATOR in the contract, however this service is a Target.

8437

16

No

The message received was sent by a Target service, but the message type '%.*ls' is marked SENT BY INITIATOR in the contract.

8439

16

No

The destination conversation group '%.*ls' is invalid.

8442

16

No

There is no Service Broker active in the database. Change to a database context that contains a Service Broker.

8444

23

Yes

The service queue structure is inconsistent. Possible database corruption. Run DBCC CHECKDB.

8447

16

No

A RECEIVE statement that assigns a value to a variable must not be combined with data retrieval operations.

8457

16

No

The message received was sent by the initiator of the conversation, but the message type '%.*ls' is marked SENT BY TARGET in the contract.

8459

16

No

The message size, including header information, exceeds the maximum allowed of %d.

8461

23

Yes

An internal service broker error detected. Possible database corruption. Run DBCC CHECKDB.

8463

16

No

Failed to read the message body while marshaling a message. This message is a symptom of another problem. Check the SQL Server error log and the Windows event log for additional messages and address the underlying problem. If the problem persists, the database may be damaged. To recover the database, restore the database from a clean backup. If no clean backup is available, consider running DBCC CHECKDB. Note that DBCC CHECKDB may remove data to repair the database.

8469

16

No

Remote service has been altered.

8471

16

No

An SNI call failed during a Service Broker/Database Mirroring transport operation. SNI error '%ls'.

8475

16

No

The conversation endpoint with ID '%ls' and is_initiator: %d has been dropped.

8479

16

No

Used by test in failpoint simulation.

8489

16

No

The dialog has exceeded the specified LIFETIME.

8492

16

No

The service contract '%.*ls' must have at least one message SENT BY INITIATOR or ANY.

8494

16

No

You do not have permission to access the service '%.*ls'.

8498

16

No

The remote service has sent a message of type '%.*ls' that is not part of the local contract.

8501

16

No

MSDTC on server '%.*ls' is unavailable.

8504

20

Yes

The import buffer for this transaction is not valid.

8508

10

No

QueryInterface failed for "%ls": %ls.

8510

20

Yes

Enlist operation failed: %ls. SQL Server could not register with Microsoft Distributed Transaction Coordinator (MS DTC) as a resource manager for this transaction. The transaction may have been stopped by the client or the resource manager.

8512

20

Yes

Microsoft Distributed Transaction Coordinator (MS DTC) commit transaction acknowledgement failed: %hs.

8514

20

Yes

Microsoft Distributed Transaction Coordinator (MS DTC) PREPARE acknowledgement failed: %hs.

8517

20

Yes

Failed to get Microsoft Distributed Transaction Coordinator (MS DTC) PREPARE information: %ls.

8519

16

No

Current Microsoft Distributed Transaction Coordinator (MS DTC) transaction must be committed by remote client.

8521

20

Yes

This awakening state is not valid: slept in %hs; awoke in %hs.

8523

15

No

PREPARE TRAN statement not allowed on MSDTC transaction.

8525

16

No

Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction.

8527

16

Yes

An attempt to create a distributed transaction export token failed with this error: %ls. Contact your Microsoft Distributed Transaction Coordinator (MS DTC) system administrator.

8529

16

No

Unable to extract the Kernel Transaction Manager (KTM) transaction handle from the Microsoft Distributed Transaction Coordinator (MS DTC) transaction: 0x%x.

8531

16

Yes

The Windows kernel transaction manager failed to create the enlistment: 0x%08x.

8533

20

No

Error while waiting for communication from Kernel Transaction Manager (KTM): %d.

8535

16

Yes

A savepoint operation in the Windows transactional file system failed: 0x%x.

8537

16

No

This transaction was aborted by Kernel Transaction Manager (KTM).

8539

10

Yes

The distributed transaction with UOW %ls was forced to commit. MS DTC became temporarily unavailable and forced heuristic resolution of the transaction. This is an informational message only. No user action is required.

8541

10

Yes

System process ID %d tried to terminate the distributed transaction with Unit of Work ID %ls. This message occurs when the client executes a KILL statement on the distributed transaction.

8543

10

Yes

Unable to commit a prepared transaction from the Microsoft Distributed Transaction Coordinator (MS DTC). Shutting down server to initiate resource manager (RM) recovery. When the RM recovers, it will query the transaction manager about the outcome of the in-doubt transaction, and commit or roll back accordingly.

8545

10

Yes

Unknown status '%d' from Reenlist call in rm_resolve.

8547

10

Yes

Resource Manager Creation Failed: %ls

8549

10

Yes

GetWhereaboutsSize call failed: %ls

8551

16

No

CoCreateGuid failed: %ls.

8553

20

No

RegQueryValueEx of \"%hs\" failed: %ls.

8555

10

Yes

RegCloseKey failed: %ls

8557

10

No

The Microsoft Distributed Transaction Coordinator (MS DTC) service could not be contacted. If you would like distributed transaction functionality, please start this service.

8560

10

Yes

Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.

8562

10

Yes

The connection has been lost with Microsoft Distributed Transaction Coordinator (MS DTC). Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) will begin once the connection is re-established. This is an informational message only. No user action is required.

8565

16

Yes

SQL Server failed to prepare DTC transaction. Failure code: %d.

8602

16

No

Indexes used in hints must be explicitly included by the index tuning wizard.

8604

16

No

ALTER TABLE SWITCH statement failed. Table '%.*ls' has a column level check constraint '%.*ls' on column '%.*ls' that is not loadable for semantic validation.

8606

17

No

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 or reduce DOP and rerun the query.

8608

16

No

The query could not be completed due to an online index build operation and must be recompiled.

8618

16

No

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 query has a GROUP BY or ORDER BY clause, consider reducing the number and/or size of the fields in the clause. Consider using prefix (LEFT()) or hash (CHECKSUM()) of fields for grouping or prefix for ordering. Note however that this will change the behavior of the query.

8621

16

No

The query processor ran out of stack space during query optimization. Please simplify the query.

8623

16

Yes

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 you believe you have received this message in error, contact Customer Support Services for more information.

8625

10

No

Warning: The join order has been enforced because a local join hint is used.

8630

17

No

Internal Query Processor Error: The query processor encountered an unexpected error during execution.

8632

17

No

Internal error: An expression services limit has been reached. Please look for potentially complex expressions in your query, and try to simplify them.

8634

17

No

The query processor received an error from a cluster communication layer.

8636

16

No

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.

8642

17

No

The query processor could not start the necessary thread resources for parallel query execution.

8645

17

Yes

A timeout occurred while waiting for memory resources to execute the query in resource pool '%ls' (%ld). Rerun the query.

8648

20

Yes

Could not insert a row larger than the page size into a hash table. Resubmit the query using the ROBUST PLAN optimization hint.

8651

17

No

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.

8655

16

No

The query processor is unable to produce a plan because the index '%.*ls' on table or view '%.*ls' is disabled.

8657

17

No

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.

8661

16

No

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.

8663

16

No

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.

8668

16

No

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 select list.

8670

16

No

Query optimizer reached the internal limit of the maximum number of views that can be used during optimization.

8672

16

No

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 ensure a target row matches at most one source row, or use the GROUP BY clause to group the source rows.

8680

17

No

Internal Query Processor Error: The query processor encountered an unexpected error during the processing of a remote query phase.

8683

16

No

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.

8685

16

No

Query cannot be compiled because <CursorStmt> 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.

8687

16

No

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.

8689

16

No

Database '%.*ls', specified in the USE PLAN hint, does not exist. Specify an existing database.

8691

16

No

Query cannot be compiled because USE PLAN hint conflicts with SET %ls ON. Consider setting %ls OFF.

8694

16

No

Cannot execute query because USE PLAN hint conflicts with use of distributed query or full-text operations. Consider removing USE PLAN hint.

8696

16

No

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-element, or a PrimaryNodeId attribute, but not both. PrimaryNodeId of Spool must reference NodeId of an existing RelOp with a Spool sub-element. Consider using unmodified XML showplan as USE PLAN hint.

8698

16

No

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 PLAN hint is one generated automatically by SQL Server for the same query.

8710

16

No

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.

8712

16

No

Index '%.*ls', specified in the USE PLAN hint, does not exist. Specify an existing index, or create an index with the specified name.

8721

15

No

Cannot execute query. TABLE HINT in the OPTION clause leads to ambiguous reference for object '%.*ls'. Consider USE PLAN query hint instead.

8723

15

No

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.

8901

16

No

Table error: Object ID %d has inconsistent metadata. This error cannot be repaired and prevents further processing of this object.

8903

16

No

Extent %S_PGID in database ID %d is allocated in both GAM %S_PGID and SGAM %S_PGID.

8905

16

No

Extent %S_PGID in database ID %d is marked allocated in the GAM, but no SGAM or IAM has allocated it.

8907

16

No

The spatial index, XML index or indexed view '%.*ls' (object ID %d) contains rows that were not produced by the view definition. This does not necessarily represent an integrity issue with the data in this database. For more information about troubleshooting DBCC errors on indexed views, see SQL Server Books Online.

8909

16

No

Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page ID %S_PGID contains an incorrect page ID in its page header. The PageId in the page header = %S_PGID.

8911

10

No

The error has been repaired.

8913

16

No

Extent %S_PGID is allocated to '%ls' and at least one other object.

8915

10

No

File %d (number of mixed extents = %I64d, mixed pages = %I64d).

8917

10

No

Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), index extents %I64d, pages %I64d, mixed extent pages %I64d.

8919

16

No

Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls): The record count in the header (%d) does not match the number of records (%d) found on page %S_PGID.

8921

16

No

Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.

8923

10

No

The repair level on the DBCC statement caused this repair to be bypassed.

8925

16

No

Table error: Cross object linkage: Page %S_PGID, slot %d, in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), refers to page %S_PGID, slot %d, in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls).

8927

16

No

Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls): The ghosted record count in the header (%d) does not match the number of ghosted records (%d) found on page %S_PGID.

8929

16

No

Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls): Errors found in off-row data with ID %I64d owned by %ls record identified by %.*ls

8931

16

No

Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) B-tree level mismatch, page %S_PGID. Level %d does not match level %d from parent %S_PGID.

8933

16

No

Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The low key value on page %S_PGID (level %d) is not >= the key value in the parent %S_PGID slot %d.

8935

16

No

Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The previous link %S_PGID on page %S_PGID does not match the previous page %S_PGID that the parent %S_PGID, slot %d expects for this page.

8937

16

No

Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). B-tree page %S_PGID has two parent nodes %S_PGID, slot %d and %S_PGID, slot %d.

8939

16

No

Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%hs) failed. Values are %ld and %ld.

8941

16

No

Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%hs) failed. Slot %d, offset 0x%x is invalid.

8943

16

No

Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%hs) failed. Slot %d, row extends into free space at 0x%x.

8945

16

No

Table error: Object ID %d, index ID %d will be rebuilt.

8947

16

No

Table error: Multiple IAM pages for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) contain allocations for the same interval. IAM pages %S_PGID and %S_PGID.

8949

10

No

%.*ls fixed %d allocation errors and %d consistency errors in table '%ls' (object ID %d).

8951

16

No

Table error: table '%ls' (ID %d). Data row does not have a matching index row in the index '%ls' (ID %d). Possible missing or invalid keys for the index row matching:

8953

10

No

Repair: Deleted off-row data column with ID %I64d, for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) on page %S_PGID, slot %d.

8955

16

No

Data row (%d:%d:%d) identified by (%ls) with index values '%ls'.

8957

10

Yes

%lsDBCC %ls (%ls%ls%ls)%ls executed by %ls found %d errors and repaired %d errors. Elapsed time: %d hours %d minutes %d seconds. %.*ls

8959

16

No

Table error: IAM page %S_PGID for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) is linked in the IAM chain for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) by page %S_PGID.

8961

16

No

Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d does not match its reference from page %S_PGID, slot %d.

8963

16

No

Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d has type %d. It cannot be placed on a page of type %d.

8965

16

No

Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d is referenced by page %S_PGID, slot %d, but was not seen in the scan.

8967

16

No

An internal error occurred in DBCC that prevented further processing. Contact Customer Support Services.

8969

16

No

Table error: IAM chain linkage error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The next page for IAM page %S_PGID is %S_PGID, but the previous link for page %S_PGID is %S_PGID.

8971

16

No

Forwarded row mismatch: Object ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) page %S_PGID, slot %d points to forwarded row page %S_PGID, slot %d; the forwarded row points back to page %S_PGID, slot %d

8973

16

No

CHECKTABLE object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) processing encountered page %S_PGID, slot %d twice.

8975

10

No

DBCC cross-rowset check failed for object '%.*ls' (object ID %d) due to internal query error %d, severity %d, state %d. Refer to Books Online for more information on this error.

8977

16

No

Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Parent node for page %S_PGID was not encountered.

8979

16

No

Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID is missing references from parent (unknown) and previous (page %S_PGID) nodes. Possible bad root entry in system catalog.

8981

16

No

Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The next pointer of %S_PGID refers to page %S_PGID. Neither %S_PGID nor its parent were encountered. Possible bad chain linkage.

8983

10

No

File %d. Extents %I64d, used pages %I64d, reserved pages %I64d, mixed extents %I64d, mixed pages %I64d.

8985

16

No

Could not locate file '%.*ls' for database '%.*ls' in sys.database_files. The file either does not exist, or was dropped.

8987

16

No

No help available for DBCC statement '%.*ls'.

8989

10

No

%.*ls found %d allocation errors and %d consistency errors in database '%ls'.

8991

16

No

0x%p to 0x%p is not a valid address range.

8993

16

No

Object ID %d, forwarding row page %S_PGID, slot %d points to page %S_PGID, slot %d. Did not encounter forwarded row. Possible allocation error.

8995

16

No

System table '%.*ls' (object ID %d, index ID %d) is in filegroup %d. All system tables must be in filegroup %d.

8997

16

No

Service Broker Msg %d, State %d: %.*ls

8999

10

No

Database tempdb allocation errors prevent further %ls processing.