SQL Server Error Messages 1 to 1000

In this post, we’ll list out the SQL Server Error Messages from the error codes 1 to 1000 and references to the detailed post to know more about the errors and how to fix them when using SQL Server as database in your application.

SQL Server Error Messages 1 to 1000

ErrorCodeSeverityError Message
2120Warning: Fatal error %d occurred at %S_DATE. Note the error and time, and contact your system administrator.
10115Query not allowed in Waitfor.
10215Incorrect syntax near ‘%.*ls’.
10315The %S_MSG that starts with ‘%.*ls’ is too long. Maximum length is %d.
10415ORDER BY items must appear in the select list if the statement contains a UNION, INTERSECT or EXCEPT operator.
10515Unclosed quotation mark after the character string ‘%.*ls’.
10616Too many table names in the query. The maximum allowable is %d.
10715The column prefix ‘%.*ls’ does not match with a table name or alias name used in the query.
10815The ORDER BY position number %ld is out of range of the number of items in the select list.
10915There are more columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement.
11015There are fewer columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement.
11115‘%ls’ must be the first statement in a query batch.
11215Variables are not allowed in the %ls statement.
11315Missing end comment mark ‘*/’.
11415Browse mode is invalid for a statement that assigns values to a variable.
11515The FOR UPDATE clause is invalid for statements containing set operators.
11615Only one expression can be specified in the select list when the subquery is not introduced with EXISTS.
11715The %S_MSG name ‘%.*ls’ contains more than the maximum number of prefixes. The maximum is %d.
11915Must pass parameter number %d and subsequent parameters as ‘@name = value’. After the form ‘@name = value’ has been used, all subsequent parameters must be passed in the form ‘@name = value’.
12015The select list for the INSERT statement contains fewer items than the insert list. The number of SELECT values must match the number of INSERT columns.
12115The select list for the INSERT statement contains more items than the insert list. The number of SELECT values must match the number of INSERT columns.
12215The %ls option is allowed only with %ls syntax.
12315Batch/procedure exceeds maximum length of %d characters.
12415CREATE PROCEDURE contains no statements.
12515Case expressions may only be nested to level %d.
12615Invalid pseudocolumn “%.*ls”.
12715A TOP N or FETCH rowcount value may not be negative.
12815The name “%.*s” is not permitted in this context. Valid expressions are constants, constant expressions, and (in some contexts) variables. Column names are not permitted.
12915Fillfactor %d is not a valid percentage; fillfactor must be between 1 and 100.
13016Cannot perform an aggregate function on an expression containing an aggregate or a subquery.
13115The size (%d) given to the %S_MSG ‘%.*ls’ exceeds the maximum allowed for any data type (%d).
13215The label ‘%.*ls’ has already been declared. Label names must be unique within a query batch or stored procedure.
13315A GOTO statement references the label ‘%.*ls’ but the label has not been declared.
13415The variable name ‘%.*ls’ has already been declared. Variable names must be unique within a query batch or stored procedure.
13515Cannot use a BREAK statement outside the scope of a WHILE statement.
13615Cannot use a CONTINUE statement outside the scope of a WHILE statement.
13715Must declare the scalar variable “%.*ls”.
13815Correlation clause in a subquery not permitted.
13915Cannot assign a default value to a local variable.
14015Can only use IF UPDATE within a CREATE TRIGGER statement.
14115A SELECT statement that assigns a value to a variable must not be combined with data-retrieval operations.
14215Incorrect syntax for definition of the ‘%ls’ constraint.
14415Cannot use an aggregate or a subquery in an expression used for the group by list of a GROUP BY clause.
14515ORDER BY items must appear in the select list if SELECT DISTINCT is specified.
14615Could not allocate ancillary table for a subquery. Maximum number of tables in a query (%d) exceeded.
14715An aggregate may not appear in the WHERE clause unless it is in a subquery contained in a HAVING clause or a select list, and the column being aggregated is an outer reference.
14815Incorrect time syntax in time string ‘%.*ls’ used with WAITFOR.
14915Time value ‘%.*ls’ used with WAITFOR is not a valid value. Check date/time syntax.
15015Time value %d used with MAX_DURATION is not a valid value; MAX_DURATION wait time must be greater or equal to 0 and less or equal to %d.
15115‘%.*ls’ is an invalid money value.
15215The same large data placement option “%.*ls” has been specified twice.
15315Invalid usage of the option %.*ls in the %ls statement.
15415%S_MSG is not allowed in %S_MSG.
15515‘%.*ls’ is not a recognized %ls option.
15615Incorrect syntax near the keyword ‘%.*ls’.
15715An aggregate may not appear in the set list of an UPDATE statement.
15815An aggregate may not appear in the OUTPUT clause.
15915Must specify the table name and index name for the DROP INDEX statement.
16015Rule does not contain a variable.
16115Rule contains more than one variable.
16215Invalid expression in a TOP or OFFSET clause.
16415Each GROUP BY expression must contain at least one column that is not an outer reference.
16516Privilege %ls may not be granted or revoked.
16615‘%ls’ does not allow specifying the database name as a prefix to the object name.
16715Cannot create %S_MSG on a temporary object.
16815The floating point value ‘%.*ls’ is out of the range of computer representation (%d bytes).
16915A column has been specified more than once in the order by list. Columns in the order by list must be unique.
17115Browse mode cannot be used with INSERT, SELECT INTO, or UPDATE statements.
17215Cannot use HOLDLOCK in browse mode.
17315The definition for column ‘%.*ls’ must include a data type.
17415The %.*ls function requires %d argument(s).
17515An aggregate may not appear in a computed column expression or check constraint.
17615The FOR BROWSE clause is no longer supported in views.
17715The IDENTITY function can only be used when the SELECT statement has an INTO clause.
17815A RETURN statement with a return value cannot be used in this context.
17915Cannot use the OUTPUT option when passing a constant to a stored procedure.
18015There are too many parameters in this %ls statement. The maximum number is %d.
18115Cannot use the OUTPUT option in a DECLARE, CREATE AGGREGATE or CREATE FUNCTION statement.
18215Table and column names must be supplied for the READTEXT or WRITETEXT utility.
18315The scale (%d) for column ‘%.*ls’ must be within the range %d to %d.
18416DEFAULT cannot be specified more than once for filegroups of the same content type.
18515Data stream is invalid for WRITETEXT statement in bulk form.
18615Data stream missing from WRITETEXT statement.
18716The valid range for MAX_QUEUE_READERS is 0 to 32767.
18815Cannot specify a log file in a CREATE DATABASE statement without also specifying at least one data file.
18915The %ls function requires %d to %d arguments.
19015An invalid date or time was specified in the statement.
19115Some part of your SQL statement is nested too deeply. Rewrite the query or break it up into smaller queries.
19216The scale must be less than or equal to the precision.
19315The object or column name starting with ‘%.*ls’ is too long. The maximum length is %d characters.
19415A SELECT INTO statement cannot contain a SELECT statement that assigns values to a variable.
19515‘%.*ls’ is not a recognized %S_MSG.
19615SELECT INTO must be the first query in a statement containing a UNION, INTERSECT or EXCEPT operator.
19715EXECUTE cannot be used as a source when inserting into a table variable.
19815Browse mode is invalid for statements containing a UNION, INTERSECT or EXCEPT operator.
19915An INSERT statement cannot contain a SELECT statement that assigns values to a variable.
20116Procedure or function ‘%.*ls’ expects parameter ‘%.*ls’, which was not supplied.
20216Invalid type ‘%s’ for WAITFOR. Supported data types are CHAR/VARCHAR, NCHAR/NVARCHAR, and DATETIME. WAITFOR DELAY supports the INT and SMALLINT data types.
20316The name ‘%.*ls’ is not a valid identifier.
20420Normalization error in node %ls.
20516All queries combined using a UNION, INTERSECT or EXCEPT operator must have an equal number of expressions in their target lists.
20616Operand type clash: %ls is incompatible with %ls
20716Invalid column name ‘%.*ls’.
20816Invalid object name ‘%.*ls’.
20916Ambiguous column name ‘%.*ls’.
21016Conversion failed when converting datetime from binary/varbinary string.
21123Corruption in database ID %I64d, object ID %ld possibly due to schema or catalog inconsistency. Run DBCC CHECKCATALOG.
21216Expression result length exceeds the maximum. %d max, %d found.
21316Column name or number of supplied values does not match table definition.
21416Procedure expects parameter ‘%ls’ of type ‘%ls’.
21516Parameters supplied for object ‘%.*ls’ which is not a function. If the parameters are intended as a table hint, a WITH keyword is required.
21616Parameters were not supplied for the function ‘%.*ls’.
21716Maximum stored procedure, function, trigger, or view nesting level exceeded (limit %d).
21816Could not find the type ‘%.*ls’. Either it does not exist or you do not have the necessary permission.
21916The type ‘%.*ls’ already exists, or you do not have permission to create it.
22016Arithmetic overflow error for data type %ls, value = %ld.
22110FIPS Warning: Implicit conversion from %ls to %ls.
22216The base type “%.*ls” is not a valid base type for the alias data type.
22311Object ID %ld specified as a default for table ID %ld, column ID %d is missing or not of type default.
22411Object ID %ld specified as a rule for table ID %ld, column ID %d is missing or not of type default.
22516The parameters supplied for the %ls “%.*ls” are not valid.
22616%ls statement not allowed within multi-statement transaction.
22715%.*ls is not a valid function, property, or field.
22815Method ‘%.*ls’ of type ‘%.*ls’ in assembly ‘%.*ls’ does not return any value.
22914The %ls permission was denied on the object ‘%.*ls’, database ‘%.*ls’, schema ‘%.*ls’.
23014The %ls permission was denied on the column ‘%.*ls’ of the object ‘%.*ls’, database ‘%.*ls’, schema ‘%.*ls’.
23111No such default. ID = %ld, database ID = %d.
23216Arithmetic overflow error for type %ls, value = %f.
23316The column ‘%.*ls’ in table ‘%.*ls’ cannot be null.
23416There is insufficient result space to convert a money value to %ls.
23516Cannot convert a char value to money. The char value has incorrect syntax.
23616The conversion from char data type to money resulted in a money overflow error.
23716There is insufficient result space to convert a money value to %ls.
23916Duplicate common table expression name ‘%.*ls’ was specified.
24016Types don’t match between the anchor and the recursive part in column “%.*ls” of recursive query “%.*ls”.
24116Conversion failed when converting date and/or time from character string.
24216The conversion of a %ls data type to a %ls data type resulted in an out-of-range value.
24316Type %.*ls is not a defined system type.
24416The conversion of the %ls value ‘%.*ls’ overflowed an %hs column. Use a larger integer column.
24516Conversion failed when converting the %ls value ‘%.*ls’ to data type %ls.
24616No anchor member was specified for recursive query “%.*ls”.
24716An anchor member was found in the recursive part of recursive query “%.*ls”.
24816The conversion of the %ls value ‘%.*ls’ overflowed an int column.
24916The type “%ls” is not comparable. It cannot be used in the %ls clause.
25116Could not allocate ancillary table for query optimization. Maximum number of tables in a query (%d) exceeded.
25216Recursive common table expression ‘%.*ls’ does not contain a top-level UNION ALL operator.
25316Recursive member of a common table expression ‘%.*ls’ has multiple recursive references.
25416Prefixed columns are not allowed in the column list of a PIVOT operator.
25516Pseudocolumns are not allowed in the column list of a PIVOT operator.
25616The data type %ls is invalid for the %ls function. Allowed types are: char/varchar, nchar/nvarchar, and binary/varbinary.
25716Implicit conversion from data type %ls to %ls is not allowed. Use the CONVERT function to run this query.
25815Cannot call methods on %ls.
25916Ad hoc updates to system catalogs are not allowed.
26016Disallowed implicit conversion from data type %ls to data type %ls, table ‘%.*ls’, column ‘%.*ls’. Use the CONVERT function to run this query.
26116‘%.*ls’ is not a recognized function.
26216%ls permission denied in database ‘%.*ls’.
26316Must specify table to select from.
26416The column name ‘%.*ls’ is specified more than once in the SET clause or column list of an INSERT. A column cannot be assigned more than one value in the same clause. Modify the clause to make sure that a column is updated only once. If this statement updates or inserts columns into a view, column aliasing can conceal the duplication in your code.
26516The column name “%.*ls” specified in the %ls operator conflicts with the existing column name in the %ls argument.
26616Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = %ld, current count = %ld.
26716Object ‘%.*ls’ cannot be found.
26816Cannot run SELECT INTO in this database. The database owner must run sp_dboption to enable this option.
27016Object ‘%.*ls’ cannot be modified.
27116The column “%.*ls” cannot be modified because it is either a computed column or is the result of a UNION operator.
27216Cannot update a timestamp column.
27316Cannot insert an explicit value into a timestamp column. Use INSERT with a column list to exclude the timestamp column, or insert a DEFAULT into the timestamp column.
27516Prefixes are not allowed in value or pivot columns of an UNPIVOT operator.
27616Pseudocolumns are not allowed as value or pivot columns of an UNPIVOT operator.
27716The column “%.*ls” is specified multiple times in the column list of the UNPIVOT operator.
27816The text, ntext, and image data types cannot be used in a GROUP BY clause.
27916The text, ntext, and image data types are invalid in this subquery or aggregate expression.
28016Only base table columns are allowed in the TEXTPTR function.
28116%d is not a valid style number when converting from %ls to a character string.
28210The ‘%.*ls’ procedure attempted to return a status of NULL, which is not allowed. A status of 0 will be returned instead.
28316READTEXT cannot be used on inserted or deleted tables within an INSTEAD OF trigger.
28416Rules cannot be bound to text, ntext, or image data types.
28516The READTEXT, WRITETEXT, and UPDATETEXT statements cannot be used with views or functions.
28616The logical tables INSERTED and DELETED cannot be updated.
28716The %ls statement is not allowed within a trigger.
28816The PATINDEX function operates on char, nchar, varchar, nvarchar, text, and ntext data types only.
28916Cannot construct data type %ls, some of the arguments have values which are not valid.
29016Invalid EXECUTE statement using object “%ls”, method “%ls”.
29116CAST or CONVERT: invalid attributes specified for type ‘%.*ls’
29216There is insufficient result space to convert a smallmoney value to %ls.
29316Cannot convert char value to smallmoney. The char value has incorrect syntax.
29416The conversion from char data type to smallmoney data type resulted in a smallmoney overflow error.
29516Conversion failed when converting character string to smalldatetime data type.
29716The user does not have permission to perform this action.
30014%ls permission was denied on object ‘%.*ls’, database ‘%.*ls’.
30116Query contains an outer-join request that is not permitted.
30216The newsequentialid() built-in function can only be used in a DEFAULT expression for a column of type ‘uniqueidentifier’ in a CREATE TABLE or ALTER TABLE statement. It cannot be combined with other operators to form a complex scalar expression.
30316The table ‘%.*ls’ is an inner member of an outer-join clause. This is not allowed if the table also participates in a regular join clause.
30416‘%I64d’ is out of range for index/statistics option ‘%.*ls’. See sp_configure option ‘%ls’ for valid values.
30516The XML data type cannot be compared or sorted, except when using the IS NULL operator.
30616The text, ntext, and image data types cannot be compared or sorted, except when using IS NULL or LIKE operator.
30716Index ID %d on table ‘%.*ls’ (specified in the FROM clause) does not exist.
30816Index ‘%.*ls’ on table ‘%.*ls’ (specified in the FROM clause) does not exist.
30916Cannot use index “%.*ls” on table “%.*ls” in a hint. XML indexes are not allowed in hints.
31015The value %d specified for the MAXRECURSION option exceeds the allowed maximum of %d.
31116Cannot use text, ntext, or image columns in the ‘inserted’ and ‘deleted’ tables.
31216Cannot reference text, ntext, or image columns in a filter stored procedure.
31316An insufficient number of arguments were supplied for the procedure or function %.*ls.
31416Cannot use GROUP BY ALL with the special tables INSERTED or DELETED.
31516Index “%.*ls” on table “%.*ls” (specified in the FROM clause) is disabled or resides in a filegroup which is not online.
31616The index ID %d on table “%.*ls” (specified in the FROM clause) is disabled or resides in a filegroup which is not online.
31716Table-valued function ‘%.*ls’ cannot have a column alias.
31816The table (and its columns) returned by a table-valued method need to be aliased.
31916Incorrect syntax near the keyword ‘with’. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon.
32016The compile-time variable value for ‘%.*ls’ in the OPTIMIZE FOR clause must be a literal.
32115%.*ls is not a recognized table hints option.
32215The variable “%.*ls” is specified in the OPTIMIZE FOR clause, but is not used in the query.
32415The ‘ALL’ version of the %.*ls operator is not supported.
32515Incorrect syntax near ‘%.*ls’. You may need to set the compatibility level of the current database to a higher value to enable this feature. See help for the SET COMPATIBILITY_LEVEL option of ALTER DATABASE.
32616Multi-part identifier ‘%.*ls’ is ambiguous. Both columns ‘%.*ls’ and ‘%.*ls’ exist.
32716Function call ‘%.*ls’ is ambiguous: both a user-defined function and a method call with this name exist.
32816A cursor plan could not be generated for the given statement because the textptr() function was used on a LOB column from one of the base tables.
32916Each GROUP BY expression must contain at least one column reference.
33015The target ‘%.*ls’ of the OUTPUT INTO clause cannot be a view or common table expression.
33115The target table ‘%.*ls’ of the OUTPUT INTO clause cannot have any enabled triggers.
33215The target table ‘%.*ls’ of the OUTPUT INTO clause cannot be on either side of a (primary key, foreign key) relationship. Found reference constraint ‘%ls’.
33315The target table ‘%.*ls’ of the OUTPUT INTO clause cannot have any enabled check constraints or any enabled rules. Found check constraint or rule ‘%ls’.
33415The target table ‘%.*ls’ of the DML statement cannot have any enabled triggers if the statement contains an OUTPUT clause without INTO clause.
33516Function call cannot be used to match a target table in the FROM clause of a DELETE or UPDATE statement. Use function name ‘%.*ls’ without parameters instead.
33615Incorrect syntax near ‘%.*ls’. If this is intended to be a common table expression, you need to explicitly terminate the previous statement with a semi-colon.
33710Warning: the floating point value ‘%.*ls’ is too small. It will be interpreted as 0.
33816READEXT, WRITETEXT, and UPDATETEXT statements cannot be used with views, remote tables, and inserted or deleted tables inside triggers.
33916DEFAULT or NULL are not allowed as explicit identity values.
34016Cannot create the trigger “%.*ls” on view “%.*ls”. AFTER triggers cannot be created on views.
34116Replication filter procedures may not contain columns of large object, large value, XML or CLR type.
34216Column “%.*ls” is not allowed in this context, and the user-defined function or aggregate “%.*ls” could not be found.
34315Unknown object type ‘%.*ls’ used in a CREATE, DROP, or ALTER statement.
34416Remote function reference ‘%.*ls’ is not allowed, and the column name ‘%.*ls’ could not be found or is ambiguous.
34516Function ‘%.*ls’ is not allowed in the OUTPUT clause, because it performs user or system data access, or is assumed to perform this access. A function is assumed by default to perform data access if it is not schemabound.
34615The parameter “%.*ls” can not be declared READONLY since it is not a table-valued parameter.
34716The table-valued parameter “%.*ls” cannot be declared as an OUTPUT parameter.
34816The table variable “%.*ls” can not be passed to a stored procedure with the OUTPUT option.
34916The procedure “%.*ls” has no parameter named “%.*ls”.
35016The column “%.*ls” does not have a valid data type. A column cannot be of a user-defined table type.
35116Column, parameter, or variable %.*ls. : Cannot find data type %.*ls.
35215The table-valued parameter “%.*ls” must be declared with the READONLY option.
35316Function ‘%.*ls’ is not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. This is because the function performs user or system data access, or is assumed to perform this access. By default, a function is assumed to perform data access if it is not schema-bound.
35416The target ‘%.*ls’ of the INSERT statement cannot be a view or common table expression when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
35516The target table ‘%.*ls’ of the INSERT statement cannot have any enabled triggers when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
35616The target table ‘%.*ls’ of the INSERT statement cannot be on either side of a (primary key, foreign key) relationship when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. Found reference constraint ‘%ls’.
35716The target table ‘%.*ls’ of the INSERT statement cannot have any enabled rules when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.  Found rule ‘%ls’.
35816The target table ‘%.*ls’ of the MERGE statement cannot have any enabled rules.  Found rule ‘%ls’.
35916The target ‘%.*ls’ of an OUTPUT INTO clause has an index with the ignore_dup_key option and cannot be used when an OUTPUT clause is also used.
36016The target column list of an INSERT, UPDATE, or MERGE statement cannot contain both a sparse column and the column set that contains the sparse column. Rewrite the statement to include either the sparse column or the column set, but not both.
36116The number of target columns that are specified in an INSERT, UPDATE, or MERGE statement exceeds the maximum of %d. This total number includes identity, timestamp, and columns that have default values. To correct this error, change the query to target a sparse column set instead of single sparse columns.
36216The query processor could not produce a query plan because the name ‘%.*ls’ in the FORCESEEK hint on table or view ‘%.*ls’ did not match the key column names of the index ‘%.*ls’.
36316The query processor could not produce a query plan because the FORCESEEK hint on table or view ‘%.*ls’ cannot be used with the %S_MSG specified by index ‘%.*ls’.
36416The query processor could not produce a query plan because the FORCESEEK hint on view ‘%.*ls’ is used without a NOEXPAND hint. Resubmit the query with the NOEXPAND hint or remove the FORCESEEK hint on the view.
36516The query processor could not produce a query plan because the FORCESEEK hint on table or view ‘%.*ls’ specified more seek columns than the number of key columns in index ‘%.*ls’.
36616The query processor could not produce a query plan because the FORCESEEK hint on table or view ‘%.*ls’ cannot be used with the column store index ‘%.*ls’.
36716The hint ‘%.*ls’ is valid only with memory optimized tables.
36916This operation is not supported on Windows Azure SQL Database with the TRCFLG_AUTO_PARTITION_REPLICATE traceflag turned on.
40116Unimplemented statement or expression %ls.
40216The data types %s and %s are incompatible in the %s operator.
40316Invalid operator for data type. Operator equals %ls, type equals %ls.
40416The column reference “%ls.%.*ls” is not allowed because it refers to a base table that is not being modified in this statement.
40516A remote table cannot be used as a DML target in a statement which includes an OUTPUT clause or a nested DML statement.
40616%ls cannot be used in the PIVOT operator because it is not invariant to NULLs.
40716Internal error. The string routine in file %hs, line %d failed with HRESULT 0x%x.
40816A constant expression was encountered in the ORDER BY list, position %i.
41216The column “%.*ls” is not updatable because it is derived or constant.
41316Correlated parameters or sub-queries are not supported by the inline function “%.*ls”.
41416UPDATE is not allowed because the statement updates view “%.*ls” which participates in a join and has an INSTEAD OF UPDATE trigger.
41516DELETE is not allowed because the statement updates view “%.*ls” which participates in a join and has an INSTEAD OF DELETE trigger.
41616The service queue “%.*ls” cannot be directly updated.
41716TOP is not allowed in an UPDATE or DELETE statement against a partitioned view.
41816Objects exposing CLR type columns are not allowed in distributed queries. Use a pass-through query to access the remote object ‘%.*ls’.
42116The %ls data type cannot be selected as DISTINCT because it is not comparable.
42216Common table expression defined but not used.
42316Xml data type methods are not supported in check constraints. Create a scalar user-defined function to wrap the method invocation. The error occurred at table “%.*ls”.
42416Xml data type methods are not supported in computed column definitions of table variables and return tables of table-valued functions. The error occurred at column “%.*ls”, table “%.*ls”, in the %ls statement.
42516Data type %ls of receiving variable is not equal to the data type %ls of column ‘%.*ls’.
42616The length %d of the receiving variable is less than the length %d of the column ‘%.*ls’.
42720Could not load the definition for constraint ID %d in database ID %d. Run DBCC CHECKCATALOG to verify the integrity of the database.
42816Insert bulk cannot be used in a multi-statement batch.
43216Xml data type methods are not supported in check constraints anymore. Please drop the constraint or create a scalar user-defined function to wrap the method invocation. The error occurred at table “%.*ls”.
43416Function ‘%ls’ is not allowed in the OUTPUT clause.
43516Xml data type methods are not supported in computed column definitions. Create a scalar user-defined function to wrap the method invocation. The error occurred at column “%.*ls”, table “%.*ls”, in the %ls statement.
43816Xml data type methods are not allowed in rules. The error occurred at table “%.*ls”.
44016Internal query compilation error. The stack overflow could not be handled.
44116Cannot use the ‘%ls’ function on a remote data source.
44216The NEST argument must be a column reference. Expressions are not allowed.
44316Invalid use of a side-effecting operator ‘%s’ within a function.
44416Select statements included within a function cannot return data to a client.
44616Cannot resolve collation conflict between “%ls” and “%ls” in %ls operator for %ls operation.
44716Expression type %ls is invalid for COLLATE clause.
44816Invalid collation ‘%.*ls’.
44916Collation conflict caused by collate clauses with different collation ‘%.*ls’ and ‘%.*ls’.
45016Code page translations are not supported for the text data type. From: %d To: %d.
45116Cannot resolve collation conflict between “%ls” and “%ls” in %ls operator occurring in %ls statement column %d.
45216COLLATE clause cannot be used on user-defined data types.
45316Collation ‘%.*ls’ is supported on Unicode data types only and cannot be set at the database or server level.
45416The UNNEST argument must be a nested table column.
45516The last statement included within a function must be a return statement.
45616Implicit conversion of %ls value to %ls cannot be performed because the resulting collation is unresolved due to collation conflict between “%ls” and “%ls” in %ls operator.
45716Implicit conversion of %ls value to %ls cannot be performed because the collation of the value is unresolved due to a collation conflict between “%ls” and “%ls” in %ls operator.
45816Cannot create the SELECT INTO target table “%.*ls” because the xml column “%.*ls” is typed with a schema collection “%.*ls” from database “%.*ls”. Xml columns cannot refer to schemata across databases.
45916Collation ‘%.*ls’ is supported on Unicode data types only and cannot be applied to char, varchar or text data types.
46016DISTINCT operator is not allowed in the recursive part of a recursive common table expression ‘%.*ls’.
46116The TOP or OFFSET operator is not allowed in the recursive part of a recursive common table expression ‘%.*ls’.
46216Outer join is not allowed in the recursive part of a recursive common table expression ‘%.*ls’.
46316Functions with parameters are not allowed in the recursive part of a recursive common table expression ‘%.*ls’.
46416Functions with side effects are not allowed in the recursive part of a recursive common table expression ‘%.*ls’.
46516Recursive references are not allowed in subqueries.
46616UNION operator is not allowed in the recursive part of a recursive common table expression ‘%.*ls’.
46716GROUP BY, HAVING, or aggregate functions are not allowed in the recursive part of a recursive common table expression ‘%.*ls’.
46816Cannot resolve the collation conflict between “%.*ls” and “%.*ls” in the %ls operation.
46916An explicit column list must be specified for target table ‘%.*ls’ when table hint KEEPIDENTITY is used and the table contains an identity column.
47016The synonym “%.*ls” referenced synonym “%.*ls”. Synonym chaining is not allowed.
47116Only one of the three options, SINGLE_BLOB, SINGLE_CLOB or SINGLE_NCLOB, can be specified.
47216Either a format file or one of the three options SINGLE_BLOB, SINGLE_CLOB, or SINGLE_NCLOB must be specified.
47316The incorrect value “%.*ls” is supplied in the PIVOT operator.
47416Unable to load the computed column definitions for table “%.*ls”.
47516Invalid SAMPLE clause. Only table names in the FROM clause of SELECT, UPDATE, and DELETE queries may be sampled.
47616Invalid PERCENT tablesample size “%f” for table “%.*ls”. The PERCENT tablesample size must be between 0 and 100.
47716Invalid ROWS value or REPEATABLE seed in the TABLESAMPLE clause for table “%.*ls”. The value or seed must be an integer.
47816The TABLESAMPLE clause cannot be used in a view definition or inline table function definition.
47916Invalid ROWS value or REPEATABLE seed “%I64d” in the TABLESAMPLE clause for table “%.*ls”. The value or seed must be greater than 0.
48016The TABLESAMPLE clause cannot be used with the table function “%.*ls”.
48116The TABLESAMPLE clause cannot be used with the linked server table “%.*ls”.
48216Non-constant or invalid expression is in the TABLESAMPLE or the REPEATABLE clause.
48316The OUTPUT clause cannot be used in an INSERT…EXEC statement.
48416Cannot declare more than %d local variables.
48516Views and inline functions cannot return xml columns that are typed with a schema collection registered in a database other than current. Column “%.*ls” is typed with the schema collection “%.*ls”, which is registered in database “%.*ls”.
48616%.*ls does not allow specifying a schema name as a prefix to the assembly name.
48716An invalid option was specified for the statement “%.*ls”.
48816%s columns must be comparable. The type of column “%.*ls” is “%s”, which is not comparable.
48916The OUTPUT clause cannot be specified because the target view “%.*ls” is a partitioned view.
49016The resync functionality is temporarily disabled.
49116A correlation name must be specified for the bulk rowset in the from clause.
49216Duplicate column names are not allowed in result sets obtained through OPENQUERY and OPENROWSET. The column name “%.*ls” is a duplicate.
49316The column ‘%.*ls’ that was returned from the nodes() method cannot be used directly. It can only be used with one of the four XML data type methods, exist(), nodes(), query(), and value(), or in IS NULL and IS NOT NULL checks.
49416The TABLESAMPLE clause can only be used with local tables.
49516The return table column “%.*ls” is not the same type as the type it was created with. Drop and recreate the module using a two-part name for the type, or use sp_refreshsqlmodule to refresh its parameters metadata.
49616The parameter “%.*ls” is not the same type as the type it was created with. Drop and recreate the module using a two-part name for the type, or use sp_refreshsqlmodule to refresh its parameters metadata.
49716Variables are not allowed in the TABLESAMPLE or REPEATABLE clauses.
49816Invalid value in the TABLESAMPLE or the REPEATABLE clause.
49916Invalid parameter for the getchecksum function.
50016Trying to pass a table-valued parameter with %d column(s) where the corresponding user-defined table type requires %d column(s).
50516The current user account was invoked with SETUSER or SP_SETAPPROLE. Changing databases is not allowed.
50616The invalid escape character “%.*ls” was specified in a %ls predicate.
50716Invalid argument for SET ROWCOUNT. Must be a non-null non-negative integer.
50911User name ‘%.*ls’ not found.
51016Cannot create a worktable row larger than allowable maximum. Resubmit your query with the ROBUST PLAN hint.
51116Cannot create a row of size %d which is greater than the allowable maximum row size of %d.
51216Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.
51316A column insert or update conflicts with a rule imposed by a previous CREATE RULE statement. The statement was terminated. The conflict occurred in database ‘%.*ls’, table ‘%.*ls’, column ‘%.*ls’.
51516Cannot insert the value NULL into column ‘%.*ls’, table ‘%.*ls’; column does not allow nulls. %ls fails.
51716Adding a value to a ‘%ls’ column caused an overflow.
51816Cannot convert data type %ls to %ls.
52216The WAITFOR thread was evicted.
52316A trigger returned a resultset and/or was running with SET NOCOUNT OFF while another outstanding result set was active.
52416A trigger returned a resultset and the server option ‘disallow results from triggers’ is true.
52516The column that was returned from the nodes() method cannot be converted to the data type %ls. It can only be used with one of the four XML data type methods, exist(), nodes(), query(), and value(), or in IS NULL and IS NOT NULL checks.
52616%ls of XML types constrained by different XML schema collections and/or DOCUMENT/CONTENT option is not allowed. Use the CONVERT function to run this query.
52716Implicit conversion between XML types constrained by different XML schema collections is not allowed. Use the CONVERT function to run this query.
52916Explicit conversion from data type %ls to %ls is not allowed.
53016The statement terminated. The maximum recursion %d has been exhausted before statement completion.
53110Cannot set NOCOUNT to OFF inside the trigger execution because the server option “disallow_results_from_triggers” is true or we are inside LOGON trigger execution.
53216The timestamp (changed to %S_TS) shows that the row has been updated by another user.
53315Cannot set XACT ABORT to OFF inside the trigger execution.
53416‘%.*ls’ failed because it is not supported in the edition of this SQL Server instance ‘%.*ls’. See books online for more details on feature support in different SQL Server editions.
53516The %.*ls function resulted in an overflow. The number of dateparts separating two date/time instances is too large. Try to use %.*ls with a less precise datepart.
53616Invalid length parameter passed to the %ls function.
53716Invalid length parameter passed to the LEFT or SUBSTRING function.
53916Schema changed after the target table was created. Rerun the Select Into query.
54016There is insufficient system memory to run RAISERROR.
54116There is not enough stack to execute the statement
54216An invalid datetime value was encountered. Value exceeds the year 9999.
54316Creation of a return table failed for the table valued function ‘%.*ls’.
54416Cannot insert explicit value for identity column in table ‘%.*ls’ when IDENTITY_INSERT is set to OFF.
54516Explicit value must be specified for identity column in table ‘%.*ls’ either when IDENTITY_INSERT is set to ON or when a replication user is inserting into a NOT FOR REPLICATION identity column.
54716The %ls statement conflicted with the %ls constraint “%.*ls”. The conflict occurred in database “%.*ls”, table “%.*ls”%ls%.*ls%ls.
54816The insert failed. It conflicted with an identity range check constraint in database ‘%.*ls’, replicated table ‘%.*ls’%ls%.*ls%ls. If the identity column is automatically managed by replication, update the range as follows: for the Publisher, execute sp_adjustpublisheridentityrange; for the Subscriber, run the Distribution Agent or the Merge Agent.
54916The collation ‘%.*ls’ of receiving variable is not equal to the collation ‘%.*ls’ of column ‘%.*ls’.
55016The attempted insert or update failed because the target view either specifies WITH CHECK OPTION or spans a view that specifies WITH CHECK OPTION and one or more rows resulting from the operation did not qualify under the CHECK OPTION constraint.
55216CryptoAPI function ‘%ls’ failed. Error 0x%x: %ls
55516User-defined functions are not yet enabled.
55616INSERT EXEC failed because the stored procedure altered the schema of the target table.
55716Only functions and some extended stored procedures can be executed from within a function.
55816Remote function calls are not allowed within a function.
56116Failed to access file ‘%.*ls’
56216Failed to access file ‘%.*ls’. Files can be accessed only through shares
56314The transaction for the INSERT EXEC statement has been rolled back. The INSERT EXEC operation will be terminated.
56416Attempted to create a record with a fixed length of ‘%d’. Maximum allowable fixed length is ‘%d’.
56518A stack overflow occurred in the server while compiling the query. Please simplify the query.
56621An error occurred while writing an audit trace. SQL Server is shutting down. Check and correct error conditions such as insufficient disk space, and then restart SQL Server. If the problem persists, disable auditing by starting the server at the command prompt with the “-f” switch, and using SP_CONFIGURE.
56716File ‘%.*ls’ is not a recognizable trace file.
56816Encountered an error or an unexpected end of trace file ‘%.*ls’.
56916The handle that was passed to %ls was invalid.
57015INSTEAD OF triggers do not support direct recursion. The trigger execution failed.
57116The specified attribute value for %ls is invalid.
57216Invalid regular expression “%.*ls” near the offset %d.
57316Evaluation of the regular expression is too complex: ‘%.*ls’.
57416%ls statement cannot be used inside a user transaction.
57516A LOGON trigger returned a resultset. Modify the LOGON trigger to not return resultsets.
57616Cannot create a row that has sparse data of size %d which is greater than the allowable maximum sparse data size of %d.
57716The value provided for the timeout is not valid. Timeout must be a valid integer between 0 and 2147483647.
57816Insert Exec not allowed in WAITFOR queries.
57916Can not execute WAITFOR query with snapshot isolation level.
58216Offset is greater than the length of the column to be updated in write.
58316Negative offset or length in write.
58416Select Into not allowed in WAITFOR queries.
58516Changing database context is not allowed when populating the resource database.
58616The prepared statement handle %d is not valid in this context.  Please verify that current database, user default schema, and ANSI_NULLS and QUOTED_IDENTIFIER set options are not changed since the handle is prepared.
58716An invalid delayed CLR type fetch token is provided.
58816Multiple tasks within the session are using the same delayed CLR type fetch token at the same time.
58916This statement has attempted to access data whose access is restricted by the assembly.
59016RPC was aborted without execution.
59116%ls: The formal parameter “%ls” was defined as OUTPUT, but the actual parameter was not declared as OUTPUT.
59216Cannot find %S_MSG ID %d in database ID %d.
59310fn_trace_gettable: XML conversion of trace data for event 165 failed.
59410fn_trace_gettable: XML conversion of trace data is not supported in fiber mode.
59516Bulk Insert with another outstanding result set should be run with XACT_ABORT on.
59616Cannot continue the execution because the session is in the kill state.
59716The execution of in-proc data access is being terminated due to errors in the User Datagram Protocol (UDP).
59816An error occurred while executing CREATE/ALTER DB. Please look at the previous error for more information.
59916%.*ls: The length of the result exceeds the length limit (2GB) of the target large type.
60112Could not continue scan with NOLOCK due to data movement.
60221Could not find an entry for table or index with partition ID %I64d in database %d. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.
60321Could not find an entry for table or index with object ID %d (partition ID %I64d) in database %d. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.
60521Attempt to fetch logical page %S_PGID in database %d failed. It belongs to allocation unit %I64d not to %I64d.
60621Metadata inconsistency.  Filegroup id %ld specified for table ‘%.*ls’ does not exist. Run DBCC CHECKDB or CHECKCATALOG.
60816No catalog entry found for partition ID %I64d in database %d. The metadata is inconsistent. Run DBCC CHECKDB to check for a metadata corruption.
60916BTree is not empty when waking up on RowsetBulk.
61016Invalid header value from a page. Run DBCC CHECKDB to check for a data corruption.
61116Cannot insert or update a row because total variable column size, including overhead, is %d bytes more than the limit.
61321Could not find an entry for worktable rowset with partition ID %I64d in database %d.
61416Could not locate bookmark due to data movement.
61521Could not find database ID %d, name ‘%.*ls’. The database may be offline. Wait a few minutes and try again.
61720Descriptor for object ID %ld in database ID %d not found in the hash table during attempt to unhash it. A work table is missing an entry. Rerun the query. If a cursor is involved, close and reopen the cursor.
62216The filegroup “%.*ls” has no files assigned to it. Tables, indexes, text columns, ntext columns, and image columns cannot be populated on this filegroup until a file is added.
62716Cannot use SAVE TRANSACTION within a distributed transaction.
62816Cannot issue SAVE TRANSACTION when there is no active transaction.
65016You can only specify the READPAST lock in the READ COMMITTED or REPEATABLE READ isolation levels.
65116Cannot use the %ls granularity hint on the table “%.*ls” because locking at the specified granularity is inhibited.
65216The index “%.*ls” for table “%.*ls” (RowsetId %I64d) resides on a read-only filegroup (“%.*ls”), which cannot be modified.
65716Could not disable support for %ls in database ‘%.*ls’ because %S_MSG.
65816Could not enable support for %ls in database ‘%.*ls’ because %S_MSG.
66116Cannot enable support for %ls in database ‘%.*ls’ because support for %ls is enabled and both are mutually exclusive.
66310Wait for redo catchup for the database “%.*ls” is taking longer than “%d” seconds for the LSN “%S_LSN”.
66410Aborting the query because it is trying to do logical revert on a readable secondary.
66616The maximum system-generated unique value for a duplicate group was exceeded for index with partition ID %I64d. Dropping and re-creating the index may resolve this; otherwise, use another clustering key.
66716The index “%.*ls” for table “%.*ls” (RowsetId %I64d) resides on a filegroup (“%.*ls”) that cannot be accessed because it is offline, is being restored, or is defunct.
66922The row object is inconsistent. Please rerun the query.
67016Large object (LOB) data for table “%.*ls” resides on an offline filegroup (“%.*ls”) that cannot be accessed.
67116Large object (LOB) data for table “%.*ls” resides on a read-only filegroup (“%.*ls”), which cannot be modified.
67210Failed to queue cleanup packets for orphaned rowsets in database “%.*ls”. Some disk space may be wasted. Cleanup will be attempted again on database restart.
67410Exception occurred in destructor of RowsetNewSS 0x%p. This error may indicate a problem related to releasing pre-allocated disk blocks used during bulk-insert operations. Restart the server to resolve this problem.
67510Worktable with partition ID %I64d was dropped successfully after %d repeated attempts.
67610Error occurred while attempting to drop worktable with partition ID %I64d.
67710Unable to drop worktable with partition ID %I64d after repeated attempts. Worktable is marked for deferred drop. This is an informational message only. No user action is required.
67810Active rowset for partition ID %I64d found at the end of the batch. This error may indicate incorrect exception handling. Use the current activity window in SQL Server Management Studio or the Transact-SQL KILL statement to terminate the server process identifier (SPID) responsible for generating the error.
67916One of the partitions of index ‘%.*ls’ for table ‘%.*ls'(partition ID %I64d) resides on a filegroup (“%.*ls”) that cannot be accessed because it is offline, restoring, or defunct. This may limit the query result.
68010Error [%d, %d, %d] occurred while attempting to drop allocation unit ID %I64d belonging to worktable with partition ID %I64d.
68116Attempting to set a non-NULL-able column’s value to NULL.
68216Internal error. Buffer provided to read column value is too small. Run DBCC CHECKDB to check for any corruption.
68322An internal error occurred while trying to convert between variable-length and fixed-length decimal formats.  Run DBCC CHECKDB to check for any database corruption.
68422An internal error occurred while attempting to convert between compressed and uncompressed storage formats.  Run DBCC CHECKDB to check for any corruption.
68522An internal error occurred while attempting to retrieve a backpointer for a heap forwarded record.
68622The maximum level of the B-Tree for rowset %I64d has been reached. SQL Server only supports upto 255 levels.
68716Cannot compress a nchar or nvarchar column that has an odd number of bytes.
68816Operation not allowed due to an active online index build.
68916Operation not allowed because of pending cleanup of online index build. Wait for cleanup to complete and re-run the operation.
69116An internal error occurred. Error code %X.
69216Internal error. Buffer provided to write a fixed column value is too large. Run DBCC CHECKDB to check for any corruption.
69416Internal error 0x%X. Unable to create a block blob in Azure storage.
69516Internal error. Unable to delete a block blob in Azure storage.
69616Internal error. Unable to gain access to the tombstone table. Result [%x]
69716Internal error. Unable to get a blob storage container.
69816Internal error. Unable to gain access to the blob container accessor.
69916Failure to read data expected in Azure Block Blob Storage. Error code 0x%X.
70119There is insufficient system memory in resource pool ‘%ls’ to run this query.
70810Server is running low on virtual address space or machine is running low on virtual memory. Reserved memory used %d times since startup. Cancel query and re-run, decrease server load, or cancel other applications.
80120A buffer was encountered with an unexpected status of 0x%x.
80217There is insufficient memory available in the buffer pool.
80310simulated failure (DEBUG only)
80510restore pending
80610audit failure (a page read from disk failed to pass basic integrity checks)
80710(no disk or the wrong disk is in the drive)
80810Insufficient bytes transferred. Common causes are backup configuration, insufficient disk space, or other problems with the storage subsystem such as corruption or hardware failure. Check errorlogs/application-logs for detailed messages and correct error conditions.
82120Could not unhash buffer at 0x%p with a buffer page number of %S_PGID and database ID %d with HASHED status set. The buffer was not found. %S_PAGE. Contact Technical Support.
82221Could not start I/O operation for request %S_BLKIOPTR. Contact Technical Support.
82324The operating system returned error %ls to SQL Server during a %S_MSG at offset %#016I64x in file ‘%ls’. Additional messages in the SQL Server error log and operating system error log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
82424SQL Server detected a logical consistency-based I/O error: %ls. It occurred during a %S_MSG of page %S_PGID in database ID %d at offset %#016I64x in file ‘%ls’.  Additional messages in the SQL Server error log or operating system error log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
82510A read of the file ‘%ls’ at offset %#016I64x succeeded after failing %d time(s) with error: %ls. Additional messages in the SQL Server error log and operating system error log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
82610incorrect pageid (expected %d:%d; actual %d:%d)
82921Database ID %d, Page %S_PGID is marked RestorePending, which may indicate disk corruption. To recover from this state, perform a restore.
83010stale page (a page read returned a log sequence number (LSN) (%u:%u:%u) that is older than the last one that was written (%u:%u:%u))
83120Unable to deallocate a kept page (database %d, page %S_PGID).
83224A page that should have been constant has changed (expected checksum: %08x, actual checksum: %08x, database %d, file ‘%ls’, page %S_PGID). This usually indicates a memory failure or other hardware or OS corruption.
83310SQL Server has encountered %d occurrence(s) of I/O requests taking longer than %d seconds to complete on file [%ls] in database id %d.  The OS file handle is 0x%p.  The offset of the latest long I/O is: %#016I64x.  The duration of the long I/O is: %I64u ms.
83516The operating system returned error %ls to SQL Server. It failed creating event for a %S_MSG at offset %#016I64x in file ‘%ls’. Additional messages in the SQL Server error log and operating system error log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
83610Database ID %d, stale page %S_PGID is under restoring.
84410Time out occurred while waiting for buffer latch — type %d, bp %p, page %d:%d, stat %#x, database id: %d, allocation unit id: %I64d%ls, task 0x%p : %d, waittime %d seconds, flags 0x%I64x, owning task 0x%p. Continuing to wait.
84517Time-out occurred while waiting for buffer latch type %d for page %S_PGID, database ID %d.
84610A time-out occurred while waiting for buffer latch — type %d, bp %p, page %d:%d, stat %#x, database id: %d, allocation unit Id: %I64d%ls, task 0x%p : %d, waittime %d seconds, flags 0x%I64x, owning task 0x%p. Not continuing to wait.
84710Timeout occurred while waiting for latch: class ‘%ls’, id %p, type %d, Task 0x%p : %d, waittime %d seconds, flags 0x%I64x, owning task 0x%p. Continuing to wait.
84810Using large pages in the memory manager.
84910Using locked pages in the memory manager.
85010%I64u MB of large page memory allocated.
85110the page is in an OFFLINE file which cannot be read
85210Using conventional memory in the memory manager.
85310Latch acquire failed due to too many concurrent latches. type %d, Task 0x%p : %d
85410Machine supports memory error recovery. SQL memory protection is enabled to recover from memory corruption.
85510Uncorrectable hardware memory corruption detected. Your system may become unstable. Please check the operating system error log for more details.
85610SQL Server has detected hardware memory corruption in database ‘%ls’, file ID: %u, page ID; %u, memory address: 0x%I64x and has successfully recovered the page.
85710Buffer pool extension “%.*ls” has been initialized successfully with size is %I64d MB.
85810Failed to create buffer pool extension of size %I64d MB on path “%.*ls”.
85910Buffer pool extension configuration “%.*ls” is in wrong format. The format should be “<extension directory>,<size in GB>”.
86010%ls. BUF address %p. Bufno %u. Extension offset %1I64d. Error code %d. Database file id %u. Database file offset %2I64d.
86110Buffer pool extension size must be larger than the physical memory size %I64d MB. Buffer pool extension is not enabled.
86210Attempt to disable buffer pool extension when in state %ls is not allowed.
86310Attempt to enable buffer pool extension when in state %ls is not allowed.
86410Attempted to initialize buffer pool extension of size %1ld KB, but maximum allowed size is %2ld KB.
86510Buffer pool extension is only supported on Standard and Enterprise Editions of SQL Server.
86610Buffer pool extension is not supported on the %ls architecture.
86710Buffer pool extension has been disabled successfully. Deleting buffer pool extension “%.*ls”.
86810Buffer pool extension size must be larger than the current memory allocation threshold %I64d MB. Buffer pool extension is not enabled.
86910Buffer pool extension “%.*ls” cannot be closed because %ld asynchronous I/Os are outstanding.
87010BPE feature switch is on!
87110Buffer pool extension size from RG Setting is %d GB (%I64d bytes).
87210Buffer pool extension is already enabled. No action is necessary.
87310Buffer pool extension is already disabled. No action is necessary.
87410Failed to initialize resilient buffer pool extension on path “%.*ls of size %I64d MB”.
87510Resilient buffer pool extension “%.*ls” has been started successfully with size %I64d MB.
87610Failed to startup resilient buffer pool extension of size %I64d MB on path “%.*ls”.
87710Resilient buffer pool extension “%.*ls” has been enabled successfully with size %I64d MB.
87810Failed to create resilient buffer pool extension of size %I64d MB on path “%.*ls”.
87910Failed to start resilient buffer pool extension because database %d is not memory optimized.
88110Resilient buffer pool extension is already disabled. No action is necessary.
88222The schema of a table created by InternalBaseTable is corrupt.
88310Could not create the Write Page Recorder table: wpr_bucket_table for database %ls, inner error: %d, inner state: %d. From %ls.
88516An internal error occurred. Error code %X. Context: “%ls::%d”.
88610Resilient buffer pool extension is already enabled or being enabled. No action is necessary.
88716Invalid RBPEX operation. Error: %ls.
88816Resilient buffer pool extension must be enabled while running this operation ‘%ls’.
88916Resilient buffer pool extension must be disabled while running this operation ‘%ls’.
89010Could not create, retrieve or persist a bucket for the Write Page Recorder in database %ls.
89110Buffer pool extension is not supported on %ls platform.
89210Using shared memory in the memory manager.
89310Failed to release latch. BUF address %p. Database ID %d. File ID %d. Page %S_PGID.
89410Buffer Pool: Allocating %I64u bytes for %I64d hashPages.
89510Hybrid buffer Pool: proposing %I64d hashPages for %I64u GiB of %S_MSG Persistent Memory.
90216To change the %ls, the database must be in state in which a checkpoint can be executed.
90416Database %ld cannot be autostarted during server shutdown or startup.
90521Database ‘%.*ls’ cannot be started in this edition of SQL Server because it contains a partition function ‘%.*ls’. Only Enterprise edition of SQL Server supports partitioning.
90716The database “%ls” has inconsistent database or file metadata.
90810Filegroup %ls in database %ls is unavailable because it is %ls. Restore or alter the filegroup to be available.
90921Database ‘%.*ls’ cannot be started in this edition of SQL Server because part or all of object ‘%.*ls’ is enabled with data compression or vardecimal storage format. Data compression and vardecimal storage format are only supported on SQL Server Enterprise Edition.
91010Database ‘%.*ls’ is upgrading script ‘%.*ls’ from level %d to level %d.
91116Database ‘%.*ls’ does not exist. Make sure that the name is entered correctly.
91221Script level upgrade for database ‘%.*ls’ failed because upgrade step ‘%.*ls’ encountered error %d, state %d, severity %d. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the ‘master’ database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
91322Could not find database ID %d. Database may not be activated yet or may be in transition. Reissue the query once the database is available. If you do not think this error is due to a database that is transitioning its state and this error continues to occur, contact your primary support provider. Please have available for review the Microsoft SQL Server error log and any additional information relevant to the circumstances when the error occurred.
91421Script level upgrade for database ‘%.*ls’ failed because upgrade step ‘%.*ls’ was aborted before completion. If the abort happened during upgrade of the ‘master’ database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
91521Unable to obtain the current script level for database ‘%.*ls’. If the error happened during startup of the ‘master’ database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that script upgrade may run to completion.
91614The server principal “%.*ls” is not able to access the database “%.*ls” under the current security context.
91721An upgrade script batch failed to execute for database ‘%.*ls’ due to compilation error. Check the previous error message for the line which caused compilation to fail.
91821Failed to load the engine script metadata from script DLL ‘%.*ls’. The error code reported by the operating system was %d. This is a serious error condition, which usually indicates a corrupt or incomplete installation. Repairing the SQL Server instance may help resolve this error.
91910User ‘%.*ls’ is changing database script level entry %d to a value of %d.
92020Only members of the sysadmin role can modify the database script level.
92114Database ‘%.*ls’ has not been recovered yet. Wait and try again.
92214Database ‘%.*ls’ is being recovered. Waiting until recovery is finished.
92314Database ‘%.*ls’ is in restricted mode. Only the database owner and members of the dbcreator and sysadmin roles can access it.
92414Database ‘%.*ls’ is already open and can only have one user at a time.
92519Maximum number of databases used for each query has been exceeded. The maximum allowed is %d.
92614Database ‘%.*ls’ cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
92714Database ‘%.*ls’ cannot be opened. It is in the middle of a restore.
92820During upgrade, database raised exception %d, severity %d, state %d, address %p. Use the exception number to determine the cause.
92920Unable to close a database that is not currently open. The application should reconnect and try again. If this action does not correct the problem, contact your primary support provider.
93021Attempting to reference recovery unit %d in database ‘%ls’ which does not exist. Contact Technical Support.
93121Attempting to reference database fragment %d in database ‘%ls’ which does not exist. Contact Technical Support.
93221SQL Server cannot load database ‘%.*ls’ because change tracking is enabled. The currently installed edition of SQL Server does not support change tracking. Either disable change tracking in the database by using a supported edition of SQL Server, or upgrade the instance to one that supports change tracking.
93321Database ‘%.*ls’ cannot be started because some of the database functionality is not available in the current edition of SQL Server.
93421SQL Server cannot load database ‘%.*ls’ because Change Data Capture is enabled. The currently installed edition of SQL Server does not support Change Data Capture. Either restore database without KEEP_CDC option, or upgrade the instance to one that supports Change Data Capture.
93521The script level for ‘%.*ls’ in database ‘%.*ls’ cannot be downgraded from %d to %d, which is supported by this server. This usually implies that a future database was attached and the downgrade path is not supported by the current installation. Install a newer version of SQL Server and re-try opening the database.
93821The target database version %d is not supported by the current code version %d.   Change target version to a supported level and restart the server.
93916Database ‘%.*ls’ cannot be started because it failed to initialize the persistent version store due to error %d. Refer to previous errors in the error log to identify the cause and correct any associated problems.
94116Database ‘%.*ls’ cannot be opened because it is not started. Retry when the database is started.
94214Database ‘%.*ls’ cannot be opened because it is offline.
94314Database ‘%.*ls’ cannot be opened because its version (%d) is later than the current server version (%d).
94410Converting database ‘%.*ls’ from version %d to the current version %d.
94516Database ‘%.*ls’ cannot be opened due to inaccessible files or insufficient memory or disk space.  See the SQL Server errorlog for details.
94614Cannot open database ‘%.*ls’ version %d. Upgrade the database to the latest version.
94716Error while closing database ‘%.*ls’. Check for previous additional errors and retry the operation.
94820The database ‘%.*ls’ cannot be opened because it is version %d. This server supports version %d and earlier. A downgrade path is not supported.
94916tempdb is skipped. You cannot run a query that requires tempdb
95020Database ‘%.*ls’ cannot be upgraded because its non-release version (%d) is not supported by this version of SQL Server. You cannot open a database that is incompatible with this version of sqlservr.exe. You must re-create the database.
95110Database ‘%.*ls’ running the upgrade step from version %d to version %d.
95216Database ‘%.*ls’ is in transition. Try the statement later.
95414The database “%.*ls” cannot be opened. It is acting as a mirror database.
95514Database %.*ls is enabled for Database Mirroring, but the database lacks quorum: the database cannot be opened.  Check the partner and witness connections if configured.
95614Database %.*ls is enabled for Database Mirroring, but has not yet synchronized with its partner. Try the operation again later.
95717Database ‘%.*ls’ is enabled for database mirroring or has joined an availability group. The name of the database cannot be changed.
95810The resource database build version is %.*ls. This is an informational message only. No user action is required.
95920The resource database version is %d and this server supports version %d. Restore the correct version or reinstall SQL Server.
96010Warning: User “sys” (principal_id = %d) in database “%.*ls” has been renamed to “%.*ls”. “sys” is a reserved user or schema name in this version of SQL Server.
96110Warning: Index “%.*ls” (index_id = %d) on object ID %d in database “%.*ls” was renamed to “%.*ls” because its name is a duplicate of another index on the same object.
96210Warning: Primary key or Unique constraint “%.*ls” (object_id = %d) in database “%.*ls” was renamed to “%.*ls” because its index was renamed.
96310Warning: Database “%.*ls” was marked suspect because of actions taken during upgrade. See errorlog or eventlog for more information. Use ALTER DATABASE to bring the database online. The database will come online in restricted_user state.
96410Warning: System user ‘%.*ls’ was found missing from database ‘%.*ls’ and has been restored. This user is required for SQL Server operation.
96510Warning: A column nullability inconsistency was detected in the metadata of index “%.*ls” (index_id = %d) on object ID %d in database “%.*ls”. The index may be corrupt. Run DBCC CHECKTABLE to verify consistency.
96610Warning: Assembly “%.*ls” in database “%.*ls” has been renamed to “%.*ls” because the name of the assembly conflicts with a system assembly in this version of SQL Server.
96710Warning: The index “%.*ls” on “%.*ls”.”%.*ls” is disabled because the XML data bound to it may contain negative values for xs:date and xs:dateTime which are not longer supported.
96810Warning: The XML facet on type “%.*ls” in schema collection “%.*ls” is updated from “%.*ls” to “%.*ls” because Sql Server does not support negative years inside values of type xs:date or xs:dateTime.
96910Warning: The default or fixed value on XML element or attribute “%.*ls” in schema collection “%.*ls” is updated from “%.*ls” to “%.*ls” because Sql Server does not support negative years inside values of type xs:date or xs:dateTime.
97010Warning: The XML instances in the XML column “%.*ls.%.*ls.%.*ls” may contain negative simple type values of type xs:date or xs:dateTime. It will be impossible to run XQuery or build a primary or selective XML index on these XML instances.
97110The resource database has been detected in two different locations. Attaching the resource database in the same directory as sqlservr.exe at ‘%.*ls’ instead of the currently attached resource database at ‘%.*ls’.
97217Could not use database ‘%d’ during procedure execution.
97410Attaching the resource database in the same directory as sqlservr.exe at ‘%.*ls’ failed as the database files do not exist.
97510System objects could not be updated in database ‘%.*ls’ because it is read-only.
97614The target database, ‘%.*ls’, is participating in an availability group and is currently not accessible for queries. Either data movement is suspended or the availability replica is not enabled for read access. To allow read-only access to this and other databases in the availability group, enable read access to one or more secondary availability replicas in the group.  For more information, see the ALTER AVAILABILITY GROUP statement in SQL Server Books Online.
97710Warning: Could not find associated index for the constraint ‘%.*ls’ on object_id ‘%d’ in database ‘%.*ls’.
97814The target database (‘%.*ls’) is in an availability group and is currently accessible for connections when the application intent is set to read only. For more information about application intent, see SQL Server Books Online.
97914The target database (‘%.*ls’) is in an availability group and currently does not allow read only connections. For more information about application intent, see SQL Server Books Online.
98021SQL Server cannot load database ‘%.*ls’ because it contains a columnstore index. The currently installed edition of SQL Server does not support columnstore indexes. Either disable the columnstore index in the database by using a supported edition of SQL Server, or upgrade the instance of SQL Server to a version that supports columnstore index.
98110Database manager will be using %d target database version.
98214Unable to access the ‘%.*ls’ database because no online secondary replicas are enabled for read-only access. Check the availability group configuration to verify that at least one secondary replica is configured for read-only access. Wait for an enabled replica to come online, and retry your read-only operation.
98314Unable to access availability database ‘%.*ls’ because the database replica is not in the PRIMARY or SECONDARY role. Connections to an availability database is permitted only when the database replica is in the PRIMARY or SECONDARY role. Try the operation again later.
98421Failed to perform a versioned copy of sqlscriptdowngrade.dll from Binn to Binn\Cache folder. VerInstallFile API failed with error code %d.
98510Successfully installed the file ‘%ls’ into folder ‘%ls’.
98610Couldn’t get a clean bootpage for database  ‘%.*ls’ after %d tries. This is an informational message only. No user action is required.
98723A duplicate key insert was hit when updating system objects in database ‘%.*ls’.
98814Unable to access database ‘%.*ls’ because it lacks a quorum of nodes for high availability. Try the operation again later.
98916Failed to take the host database with ID %d offline when one or more of its partition databases is marked as suspect.
99016Taking the host database with ID %d offline because one or more of its partition databases is marked as suspect.
99116Failed to take the host database ‘%.*ls’ offline when one or more of its partition databases is marked as suspect.
99216Failed to get the shared lock on database ‘%.*ls’.
99310Redo for database ‘%.*ls’ applied version upgrade step from %d to %d.
99410Warning: Index “%.*ls” on “%.*ls”.”%.*ls” is disabled because it contains a computed column.
99510Warning: Index “%.*ls” on “%.*ls”.”%.*ls” is disabled. It cannot be upgraded as it resides on a read-only filegroup.
99610Warning: Index “%.*ls” on “%.*ls”.”%.*ls” is disabled. This columnstore index cannot be upgraded, likely because it exceeds the row size limit of ‘%d’ bytes.
99716Failed to get the update lock on database ‘%.*ls’.