错误码目录 / Microsoft SQL Server
Microsoft SQL Server 错误码目录 · 第 1 / 18 页
本页收录 Microsoft SQL Server 的 17,993 条错误码知识条目,每条均可打开独立详情页,包含错误说明、编号信息、官方文档与公开资料。
- 21 — Warning: Fatal error %d occurred at %S_DATE. Note the error and time, and contact your system administrator.
- 53
- 101 — Query not allowed in Waitfor.
- 102 — Incorrect syntax near '%.*ls'.
- 103 — The %S_MSG that starts with '%.*ls' is too long. Maximum length is %d.
- 104 — ORDER BY items must appear in the select list if the statement contains a UNION, INTERSECT or EXCEPT operator.
- 105 — Unclosed quotation mark after the character string '%.*ls'.
- 106 — Too many table names in the query. The maximum allowable is %d.
- 107 — The column prefix '%.*ls' does not match with a table name or alias name used in the query.
- 108 — The ORDER BY position number %ld is out of range of the number of items in the select list.
- 109 — There 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 nu…
- 110 — There 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 n…
- 111 — '%ls' must be the first statement in a query batch.
- 112 — Variables are not allowed in the %ls statement.
- 113 — Missing end comment mark '*/'.
- 114 — Browse mode is invalid for a statement that assigns values to a variable.
- 115 — The FOR UPDATE clause is invalid for statements containing set operators.
- 116 — Only one expression can be specified in the select list when the subquery is not introduced with EXISTS.
- 117 — The %S_MSG name '%.*ls' contains more than the maximum number of prefixes. The maximum is %d.
- 119 — Must pass parameter number %d and subsequent parameters as '@name = value'. After the form '@name = value' has been used, all subsequent parameters mu…
- 120 — The select list for the INSERT statement contains fewer items than the insert list. The number of SELECT values must match the number of INSERT column…
- 121 — The 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…
- 122 — The %ls option is allowed only with %ls syntax.
- 123 — Batch/procedure exceeds maximum length of %d characters.
- 124 — CREATE PROCEDURE contains no statements.
- 125 — Case expressions may only be nested to level %d.
- 126 — Invalid pseudocolumn "%.*ls".
- 127 — A TOP N or FETCH rowcount value may not be negative.
- 128 — The name "%.*s" is not permitted in this context. Valid expressions are constants, constant expressions, and (in some contexts) variables. Column name…
- 129 — Fillfactor %d is not a valid percentage; fillfactor must be between 1 and 100.
- 130 — Cannot perform an aggregate function on an expression containing an aggregate or a subquery.
- 131 — The size (%d) given to the %S_MSG '%.*ls' exceeds the maximum allowed for any data type (%d).
- 132 — The label '%.*ls' has already been declared. Label names must be unique within a query batch or stored procedure.
- 133 — A GOTO statement references the label '%.*ls' but the label has not been declared.
- 134 — The variable name '%.*ls' has already been declared. Variable names must be unique within a query batch or stored procedure.
- 135 — Cannot use a BREAK statement outside the scope of a WHILE statement.
- 136 — Cannot use a CONTINUE statement outside the scope of a WHILE statement.
- 137 — Must declare the scalar variable "%.*ls".
- 138 — Correlation clause in a subquery not permitted.
- 139 — Cannot assign a default value to a local variable.
- 140 — Can only use IF UPDATE within a CREATE TRIGGER statement.
- 141 — A SELECT statement that assigns a value to a variable must not be combined with data-retrieval operations.
- 142 — Incorrect syntax for definition of the '%ls' constraint.
- 143 — A COMPUTE BY item was not found in the order by list. All expressions in the compute by list must also be present in the order by list.
- 144 — Cannot use an aggregate or a subquery in an expression used for the group by list of a GROUP BY clause.
- 145 — ORDER BY items must appear in the select list if SELECT DISTINCT is specified.
- 146 — Could not allocate ancillary table for a subquery. Maximum number of tables in a query (%d) exceeded.
- 147 — An 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 aggrega…
- 148 — Incorrect time syntax in time string '%.*ls' used with WAITFOR.
- 149 — Time value '%.*ls' used with WAITFOR is not a valid value. Check date/time syntax.
- 150 — Time 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.
- 151 — '%.*ls' is an invalid money value.
- 152 — The same large data placement option "%.*ls" has been specified twice.
- 153 — Invalid usage of the option %.*ls in the %ls statement.
- 154 — %S_MSG is not allowed in %S_MSG.
- 155 — '%.*ls' is not a recognized %ls option.
- 156 — Incorrect syntax near the keyword '%.*ls'.
- 157 — An aggregate may not appear in the set list of an UPDATE statement.
- 158 — An aggregate may not appear in the OUTPUT clause.
- 159 — Must specify the table name and index name for the DROP INDEX statement.
- 160 — Rule does not contain a variable.
- 161 — Rule contains more than one variable.
- 162 — Invalid expression in a TOP or OFFSET clause.
- 163 — The compute by list does not match the order by list.
- 164 — Each GROUP BY expression must contain at least one column that is not an outer reference.
- 165 — Privilege %ls may not be granted or revoked.
- 166 — '%ls' does not allow specifying the database name as a prefix to the object name.
- 167 — Cannot create %S_MSG on a temporary object.
- 168 — The floating point value '%.*ls' is out of the range of computer representation (%d bytes).
- 169 — A column has been specified more than once in the order by list. Columns in the order by list must be unique.
- 171 — Browse mode cannot be used with INSERT, SELECT INTO, or UPDATE statements.
- 172 — Cannot use HOLDLOCK in browse mode.
- 173 — The definition for column '%.*ls' must include a data type.
- 174 — The %.*ls function requires %d argument(s).
- 175 — An aggregate may not appear in a computed column expression or check constraint.
- 176 — The FOR BROWSE clause is no longer supported in views.
- 177 — The IDENTITY function can only be used when the SELECT statement has an INTO clause.
- 178 — A RETURN statement with a return value cannot be used in this context.
- 179 — Cannot use the OUTPUT option when passing a constant to a stored procedure.
- 180 — There are too many parameters in this %ls statement. The maximum number is %d.
- 181 — Cannot use the OUTPUT option in a DECLARE, CREATE AGGREGATE or CREATE FUNCTION statement.
- 182 — Table and column names must be supplied for the READTEXT or WRITETEXT utility.
- 183 — The scale (%d) for column '%.*ls' must be within the range %d to %d.
- 184 — DEFAULT cannot be specified more than once for filegroups of the same content type.
- 185 — Data stream is invalid for WRITETEXT statement in bulk form.
- 186 — Data stream missing from WRITETEXT statement.
- 187 — The valid range for MAX_QUEUE_READERS is 0 to 32767.
- 188 — Cannot specify a log file in a CREATE DATABASE statement without also specifying at least one data file.
- 189 — The %ls function requires %d to %d arguments.
- 190 — An invalid date or time was specified in the statement.
- 191 — Some part of your SQL statement is nested too deeply. Rewrite the query or break it up into smaller queries.
- 192 — The scale must be less than or equal to the precision.
- 193 — The object or column name starting with '%.*ls' is too long. The maximum length is %d characters.
- 194 — A SELECT INTO statement cannot contain a SELECT statement that assigns values to a variable.
- 195 — '%.*ls' is not a recognized %S_MSG.
- 196 — SELECT INTO must be the first query in a statement containing a UNION, INTERSECT or EXCEPT operator.
- 197 — EXECUTE cannot be used as a source when inserting into a table variable.
- 198 — Browse mode is invalid for statements containing a UNION, INTERSECT or EXCEPT operator.
- 199 — An INSERT statement cannot contain a SELECT statement that assigns values to a variable.
- 201 — Procedure or function '%.*ls' expects parameter '%.*ls', which was not supplied.
- 202 — Invalid type '%s' for WAITFOR. Supported data types are CHAR/VARCHAR, NCHAR/NVARCHAR, and DATETIME. WAITFOR DELAY supports the INT and SMALLINT data t…
- 203 — The name '%.*ls' is not a valid identifier.
- 204 — Normalization error in node %ls.
- 205 — All queries combined using a UNION, INTERSECT or EXCEPT operator must have an equal number of expressions in their target lists.
- 206 — Operand type clash: %ls is incompatible with %ls
- 207 — Invalid column name '%.*ls'.
- 208 — Invalid object name '%.*ls'.
- 209 — Ambiguous column name '%.*ls'.
- 210 — Conversion failed when converting datetime from binary/varbinary string.
- 211 — Corruption in database ID %I64d, object ID %ld possibly due to schema or catalog inconsistency. Run DBCC CHECKCATALOG.
- 212 — Expression result length exceeds the maximum. %d max, %d found.
- 213 — Column name or number of supplied values does not match table definition.
- 214 — Procedure expects parameter '%ls' of type '%ls'.
- 215 — Parameters supplied for object '%.*ls' which is not a function. If the parameters are intended as a table hint, a WITH keyword is required.
- 216 — Parameters were not supplied for the function '%.*ls'.
- 217 — Maximum stored procedure, function, trigger, or view nesting level exceeded (limit %d).
- 218 — Could not find the type '%.*ls'. Either it does not exist or you do not have the necessary permission.
- 219 — The type '%.*ls' already exists, or you do not have permission to create it.
- 220 — Arithmetic overflow error for data type %ls, value = %ld.
- 221 — FIPS Warning: Implicit conversion from %ls to %ls.
- 222 — The base type "%.*ls" is not a valid base type for the alias data type.
- 223 — Object ID %ld specified as a default for table ID %ld, column ID %d is missing or not of type default.
- 224 — Object ID %ld specified as a rule for table ID %ld, column ID %d is missing or not of type default.
- 225 — The parameters supplied for the %ls "%.*ls" are not valid.
- 226 — %ls statement not allowed within multi-statement transaction.
- 227 — "%.*ls" is not a valid function, property, or field.
- 228 — Method '%.*ls' of type '%.*ls' in assembly '%.*ls' does not return any value.
- 229 — The %ls permission was denied on the object '%.*ls', database '%.*ls', schema '%.*ls'.
- 230 — The %ls permission was denied on the column '%.*ls' of the object '%.*ls', database '%.*ls', schema '%.*ls'.
- 231 — No such default. ID = %ld, database ID = %d.
- 232 — Arithmetic overflow error for type %ls, value = %f.
- 233 — The column '%.*ls' in table '%.*ls' cannot be null.
- 234 — There is insufficient result space to convert a money value to %ls.
- 235 — Cannot convert a char value to money. The char value has incorrect syntax.
- 236 — The conversion from char data type to money resulted in a money overflow error.
- 237 — There is insufficient result space to convert a money value to %ls.
- 239 — Duplicate common table expression name '%.*ls' was specified.
- 240 — Types don't match between the anchor and the recursive part in column "%.*ls" of recursive query "%.*ls".
- 241 — Conversion failed when converting date and/or time from character string.
- 242 — The conversion of a %ls data type to a %ls data type resulted in an out-of-range value.
- 243 — Type %.*ls is not a defined system type.
- 244 — The conversion of the %ls value '%.*ls' overflowed an %hs column. Use a larger integer column.
- 245 — Conversion failed when converting the %ls value '%.*ls' to data type %ls.
- 246 — No anchor member was specified for recursive query "%.*ls".
- 247 — An anchor member was found in the recursive part of recursive query "%.*ls".
- 248 — The conversion of the %ls value '%.*ls' overflowed an int column.
- 249 — The type "%ls" is not comparable. It cannot be used in the %ls clause.
- 251 — Could not allocate ancillary table for query optimization. Maximum number of tables in a query (%d) exceeded.
- 252 — Recursive common table expression '%.*ls' does not contain a top-level UNION ALL operator.
- 253 — Recursive member of a common table expression '%.*ls' has multiple recursive references.
- 254 — Prefixed columns are not allowed in the column list of a PIVOT operator.
- 255 — Pseudocolumns are not allowed in the column list of a PIVOT operator.
- 256 — The data type %ls is invalid for the %ls function. Allowed types are: char/varchar, nchar/nvarchar, and binary/varbinary.
- 257 — Implicit conversion from data type %ls to %ls is not allowed. Use the CONVERT function to run this query.
- 258 — Cannot call methods on %ls.
- 259 — Ad hoc updates to system catalogs are not allowed.
- 260 — Disallowed implicit conversion from data type %ls to data type %ls, table '%.*ls', column '%.*ls'. Use the CONVERT function to run this query.
- 261 — '%.*ls' is not a recognized function.
- 262 — %ls permission denied in database '%.*ls'.
- 263 — Must specify table to select from.
- 264 — The 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 …
- 265 — The column name "%.*ls" specified in the %ls operator conflicts with the existing column name in the %ls argument.
- 266 — Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = %ld, current count = %ld.
- 267 — Object '%.*ls' cannot be found.
- 268 — Cannot run SELECT INTO in this database. The database owner must run sp_dboption to enable this option.
- 270 — Object '%.*ls' cannot be modified.
- 271 — The column "%.*ls" cannot be modified because it is either a computed column or is the result of a UNION operator.
- 272 — Cannot update a timestamp column.
- 273 — Cannot 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 t…
- 275 — Prefixes are not allowed in value or pivot columns of an UNPIVOT operator.
- 276 — Pseudocolumns are not allowed as value or pivot columns of an UNPIVOT operator.
- 277 — The column "%.*ls" is specified multiple times in the column list of the UNPIVOT operator.
- 278 — The text, ntext, and image data types cannot be used in a GROUP BY clause.
- 279 — The text, ntext, and image data types are invalid in this subquery or aggregate expression.
- 280 — Only base table columns are allowed in the TEXTPTR function.
- 281 — %d is not a valid style number when converting from %ls to a character string.
- 282 — The '%.*ls' procedure attempted to return a status of NULL, which is not allowed. A status of 0 will be returned instead.
- 283 — READTEXT cannot be used on inserted or deleted tables within an INSTEAD OF trigger.
- 284 — Rules cannot be bound to text, ntext, or image data types.
- 285 — The READTEXT, WRITETEXT, and UPDATETEXT statements cannot be used with views or functions.
- 286 — The logical tables INSERTED and DELETED cannot be updated.
- 287 — The %ls statement is not allowed within a trigger.
- 288 — The PATINDEX function operates on char, nchar, varchar, nvarchar, text, and ntext data types only.
- 289 — Cannot construct data type %ls, some of the arguments have values which are not valid.
- 290 — Invalid EXECUTE statement using object "%ls", method "%ls".
- 291 — CAST or CONVERT: invalid attributes specified for type '%.*ls'
- 292 — There is insufficient result space to convert a smallmoney value to %ls.
- 293 — Cannot convert char value to smallmoney. The char value has incorrect syntax.
- 294 — The conversion from char data type to smallmoney data type resulted in a smallmoney overflow error.
- 295 — Conversion failed when converting character string to smalldatetime data type.
- 296 — The conversion of char data type to smalldatetime data type resulted in an out-of-range smalldatetime value.
- 297 — The user does not have permission to perform this action.
- 298 — The conversion from datetime data type to smalldatetime data type resulted in a smalldatetime overflow error.
- 300 — %ls permission was denied on object '%.*ls', database '%.*ls'.
- 301 — Query contains an outer-join request that is not permitted.
- 302 — The newsequentialid() built-in function can only be used in a DEFAULT expression for a column of type 'uniqueidentifier' in a CREATE TABLE or ALTER TA…
- 303 — The 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.
- 304 — '%I64d' is out of range for index/statistics option '%.*ls'. See sp_configure option '%ls' for valid values.
- 305 — The XML data type cannot be compared or sorted, except when using the IS NULL operator.
- 306 — The text, ntext, and image data types cannot be compared or sorted, except when using IS NULL or LIKE operator.
- 307 — Index ID %d on table '%.*ls' (specified in the FROM clause) does not exist.
- 308 — Index '%.*ls' on table '%.*ls' (specified in the FROM clause) does not exist.
- 309 — Cannot use index "%.*ls" on table "%.*ls" in a hint. XML indexes are not allowed in hints.
- 310 — The value %d specified for the MAXRECURSION option exceeds the allowed maximum of %d.
- 311 — Cannot use text, ntext, or image columns in the 'inserted' and 'deleted' tables.
- 312 — Cannot reference text, ntext, or image columns in a filter stored procedure.
- 313 — An insufficient number of arguments were supplied for the procedure or function %.*ls.
- 314 — Cannot use GROUP BY ALL with the special tables INSERTED or DELETED.
- 315 — Index "%.*ls" on table "%.*ls" (specified in the FROM clause) is disabled or resides in a filegroup which is not online.
- 316 — The index ID %d on table "%.*ls" (specified in the FROM clause) is disabled or resides in a filegroup which is not online.
- 317 — Table-valued function '%.*ls' cannot have a column alias.
- 318 — The table (and its columns) returned by a table-valued method need to be aliased.
- 319 — Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause,…
- 320 — The compile-time variable value for '%.*ls' in the OPTIMIZE FOR clause must be a literal.
- 321 — "%.*ls" is not a recognized table hints option. If it is intended as a parameter to a table-valued function or to the CHANGETABLE function, ensure tha…
- 322 — The variable "%.*ls" is specified in the OPTIMIZE FOR clause, but is not used in the query.
- 323 — The 'COMPUTE' clause is not allowed in a statement containing an INTERSECT or EXCEPT operator.
- 324 — The 'ALL' version of the %.*ls operator is not supported.
- 325 — Incorrect 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 …
- 326 — Multi-part identifier '%.*ls' is ambiguous. Both columns '%.*ls' and '%.*ls' exist.
- 327 — Function call '%.*ls' is ambiguous: both a user-defined function and a method call with this name exist.
- 328 — A 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.
- 329 — Each GROUP BY expression must contain at least one column reference.
- 330 — The target '%.*ls' of the OUTPUT INTO clause cannot be a view or common table expression.
- 331 — The target table '%.*ls' of the OUTPUT INTO clause cannot have any enabled triggers.
- 332 — The target table '%.*ls' of the OUTPUT INTO clause cannot be on either side of a (primary key, foreign key) relationship. Found reference constraint '…
- 333 — The target table '%.*ls' of the OUTPUT INTO clause cannot have any enabled check constraints or any enabled rules. Found check constraint or rule '%ls…
- 334 — The target table '%.*ls' of the DML statement cannot have any enabled triggers if the statement contains an OUTPUT clause without INTO clause.
- 335 — Function 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 …
- 336 — Incorrect syntax near '%.*ls'. If this is intended to be a common table expression, you need to explicitly terminate the previous statement with a sem…
- 337 — Warning: the floating point value '%.*ls' is too small. It will be interpreted as 0.
- 338 — READEXT, WRITETEXT, and UPDATETEXT statements cannot be used with views, remote tables, and inserted or deleted tables inside triggers.
- 339 — DEFAULT or NULL are not allowed as explicit identity values.
- 340 — Cannot create the trigger "%.*ls" on view "%.*ls". AFTER triggers cannot be created on views.
- 341 — Replication filter procedures may not contain columns of large object, large value, XML or CLR type.
- 342 — Column "%.*ls" is not allowed in this context, and the user-defined function or aggregate "%.*ls" could not be found.
- 343 — Unknown object type '%.*ls' used in a CREATE, DROP, or ALTER statement.
- 344 — Remote function reference '%.*ls' is not allowed, and the column name '%.*ls' could not be found or is ambiguous.
- 345 — Function '%.*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…
- 346 — The parameter "%.*ls" can not be declared READONLY since it is not a table-valued parameter.
- 347 — The table-valued parameter "%.*ls" cannot be declared as an OUTPUT parameter.
- 348 — The table variable "%.*ls" can not be passed to a stored procedure with the OUTPUT option.
- 349 — The procedure "%.*ls" has no parameter named "%.*ls".
- 350 — The column "%.*ls" does not have a valid data type. A column cannot be of a user-defined table type.
- 351 — Column, parameter, or variable %.*ls. : Cannot find data type %.*ls.
- 352 — The table-valued parameter "%.*ls" must be declared with the READONLY option.
- 353 — Function '%.*ls' is not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. This is becaus…
- 354 — The target '%.*ls' of the INSERT statement cannot be a view or common table expression when the FROM clause contains a nested INSERT, UPDATE, DELETE, …
- 355 — The target table '%.*ls' of the INSERT statement cannot have any enabled triggers when the FROM clause contains a nested INSERT, UPDATE, DELETE, or ME…
- 356 — The 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…
- 357 — The target table '%.*ls' of the INSERT statement cannot have any enabled rules when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE…
- 358 — The target table '%.*ls' of the MERGE statement cannot have any enabled rules. Found rule '%ls'.
- 359 — The 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.
- 360 — The 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…
- 361 — The number of target columns that are specified in an INSERT, UPDATE, or MERGE statement exceeds the maximum of %d. This total number includes identit…
- 362 — The 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 colum…
- 363 — The 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 ind…
- 364 — The 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…
- 365 — The 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 …
- 366 — The 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 '%.*…
- 367 — The hint '%.*ls' is valid only with memory optimized tables.
- 368 — The external policy action '%.*ls' was denied on the requested resource.
- 369 — This operation is not supported on Windows Azure SQL Database with the TRCFLG_AUTO_PARTITION_REPLICATE traceflag turned on.
- 370 — Unknown object name.
- 371 — The user does not have the external policy action '%ls' or permission '%.*ls' to perform this action.
- 372 — External access policies needed to validate access are either expired or not found. To force a policy fetch, execute the procedure 'sys.sp_external_po…
- 373 — The %ls permission or external policy action '%ls' was denied on the object '%.*ls', database '%.*ls', schema '%.*ls'.
- 374 — The Babylon engine could not be initialized.
- 375 — The %ls permission was denied on the column '%.*ls' of the object '%.*ls', database '%.*ls', schema '%.*ls' due to a Microsoft Purview Information Pro…
- 401 — Unimplemented statement or expression %ls.
- 402 — The data types %s and %s are incompatible in the %s operator.
- 403 — Invalid operator for data type. Operator equals %ls, type equals %ls.
- 404 — The column reference "%ls.%.*ls" is not allowed because it refers to a base table that is not being modified in this statement.
- 405 — A remote table cannot be used as a DML target in a statement which includes an OUTPUT clause or a nested DML statement.
- 406 — %ls cannot be used in the PIVOT operator because it is not invariant to NULLs.
- 407 — Internal error. The string routine in file %hs, line %d failed with HRESULT 0x%x.
- 408 — A constant expression was encountered in the ORDER BY list, position %i.
- 411 — COMPUTE clause #%d, aggregate expression #%d is not in the select list.
- 412 — The column "%.*ls" is not updatable because it is derived or constant.
- 413 — Correlated parameters or sub-queries are not supported by the inline function "%.*ls".
- 414 — UPDATE is not allowed because the statement updates view "%.*ls" which participates in a join and has an INSTEAD OF UPDATE trigger.
- 415 — DELETE is not allowed because the statement updates view "%.*ls" which participates in a join and has an INSTEAD OF DELETE trigger.
- 416 — The service queue "%.*ls" cannot be directly updated.
- 417 — TOP is not allowed in an UPDATE or DELETE statement against a partitioned view.
- 418 — Objects exposing CLR type columns are not allowed in distributed queries. Use a pass-through query to access the remote object '%.*ls'.
- 421 — The %ls data type cannot be selected as DISTINCT because it is not comparable.
- 422 — Common table expression defined but not used.
- 423 — Xml data type methods are not supported in check constraints. Create a scalar user-defined function to wrap the method invocation. The error occurred …
- 424 — Xml data type methods are not supported in computed column definitions of table variables and return tables of table-valued functions. The error occur…
- 425 — Data type %ls of receiving variable is not equal to the data type %ls of column '%.*ls'.
- 426 — The length %d of the receiving variable is less than the length %d of the column '%.*ls'.
- 427 — Could not load the definition for constraint ID %d in database ID %d. Run DBCC CHECKCATALOG to verify the integrity of the database.
- 428 — Insert bulk cannot be used in a multi-statement batch.
- 432 — Xml data type methods are not supported in check constraints anymore. Please drop the constraint or create a scalar user-defined function to wrap the …
- 434 — Function '%ls' is not allowed in the OUTPUT clause.
- 435 — Xml data type methods are not supported in computed column definitions. Create a scalar user-defined function to wrap the method invocation. The error…
- 438 — Xml data type methods are not allowed in rules. The error occurred at table "%.*ls".
- 440 — Internal query compilation error. The stack overflow could not be handled.
- 441 — Cannot use the '%ls' function on a remote data source.
- 442 — The NEST argument must be a column reference. Expressions are not allowed.
- 443 — Invalid use of a side-effecting operator '%s' within a function.
- 444 — Select statements included within a function cannot return data to a client.
- 445 — COLLATE clause cannot be used on expressions containing a COLLATE clause.
- 446 — Cannot resolve collation conflict between "%ls" and "%ls" in %ls operator for %ls operation.
- 447 — Expression type %ls is invalid for COLLATE clause.
- 448 — Invalid collation '%.*ls'.
- 449 — Collation conflict caused by collate clauses with different collation '%.*ls' and '%.*ls'.
- 450 — Code page translations are not supported for the text data type. From: %d To: %d.
- 451 — Cannot resolve collation conflict between "%ls" and "%ls" in %ls operator occurring in %ls statement column %d.
- 452 — COLLATE clause cannot be used on user-defined data types.
- 453 — Collation '%.*ls' is supported on Unicode data types only and cannot be set at the database or server level.
- 454 — The UNNEST argument must be a nested table column.
- 455 — The last statement included within a function must be a return statement.
- 456 — Implicit conversion of %ls value to %ls cannot be performed because the resulting collation is unresolved due to collation conflict between "%ls" and …
- 457 — Implicit conversion of %ls value to %ls cannot be performed because the collation of the value is unresolved due to a collation conflict between "%ls"…
- 458 — Cannot create the SELECT INTO target table "%.*ls" because the xml column "%.*ls" is typed with a schema collection "%.*ls" from database "%.*ls". Xml…
- 459 — Collation '%.*ls' is supported on Unicode data types only and cannot be applied to char, varchar or text data types.
- 460 — DISTINCT operator is not allowed in the recursive part of a recursive common table expression '%.*ls'.
- 461 — The TOP or OFFSET operator is not allowed in the recursive part of a recursive common table expression '%.*ls'.
- 462 — Outer join is not allowed in the recursive part of a recursive common table expression '%.*ls'.
- 463 — Functions with parameters are not allowed in the recursive part of a recursive common table expression '%.*ls'.
- 464 — Functions with side effects are not allowed in the recursive part of a recursive common table expression '%.*ls'.
- 465 — Recursive references are not allowed in subqueries.
- 466 — UNION operator is not allowed in the recursive part of a recursive common table expression '%.*ls'.
- 467 — GROUP BY, HAVING, or aggregate functions are not allowed in the recursive part of a recursive common table expression '%.*ls'.
- 468 — Cannot resolve the collation conflict between "%.*ls" and "%.*ls" in the %ls operation.
- 469 — An explicit column list must be specified for target table '%.*ls' when table hint KEEPIDENTITY is used and the table contains an identity column.
- 470 — The synonym "%.*ls" referenced synonym "%.*ls". Synonym chaining is not allowed.
- 471 — Only one of the three options, SINGLE_BLOB, SINGLE_CLOB or SINGLE_NCLOB, can be specified.
- 472 — Either a format file or one of the three options SINGLE_BLOB, SINGLE_CLOB, or SINGLE_NCLOB must be specified.
- 473 — The incorrect value "%.*ls" is supplied in the PIVOT operator.
- 474 — Unable to load the computed column definitions for table "%.*ls".
- 475 — Invalid SAMPLE clause. Only table names in the FROM clause of SELECT, UPDATE, and DELETE queries may be sampled.
- 476 — Invalid PERCENT tablesample size "%f" for table "%.*ls". The PERCENT tablesample size must be between 0 and 100.
- 477 — Invalid ROWS value or REPEATABLE seed in the TABLESAMPLE clause for table "%.*ls". The value or seed must be an integer.
- 478 — The TABLESAMPLE clause cannot be used in a view definition or inline table function definition.
- 479 — Invalid ROWS value or REPEATABLE seed "%I64d" in the TABLESAMPLE clause for table "%.*ls". The value or seed must be greater than 0.
- 480 — The TABLESAMPLE clause cannot be used with the table function "%.*ls".
- 481 — The TABLESAMPLE clause cannot be used with the linked server table "%.*ls".
- 482 — Non-constant or invalid expression is in the TABLESAMPLE or the REPEATABLE clause.
- 483 — The OUTPUT clause cannot be used in an INSERT...EXEC statement.
- 484 — Cannot declare more than %d local variables.
- 485 — Views and inline functions cannot return xml columns that are typed with a schema collection registered in a database other than current. Column "%.*l…
- 486 — "%.*ls" does not allow specifying a schema name as a prefix to the assembly name.
- 487 — An invalid option was specified for the statement "%.*ls".
- 488 — %s columns must be comparable. The type of column "%.*ls" is "%s", which is not comparable.
- 489 — The OUTPUT clause cannot be specified because the target view "%.*ls" is a partitioned view.
- 490 — The resync functionality is temporarily disabled.
- 491 — A correlation name must be specified for the bulk rowset in the from clause.
- 492 — Duplicate column names are not allowed in result sets obtained through OPENQUERY and OPENROWSET. The column name "%.*ls" is a duplicate.
- 493 — The 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, …
- 494 — The TABLESAMPLE clause can only be used with local tables.
- 495 — The 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,…
- 496 — The 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…
- 497 — Variables are not allowed in the TABLESAMPLE or REPEATABLE clauses.
- 498 — Invalid value in the TABLESAMPLE or the REPEATABLE clause.
- 499 — Invalid parameter for the getchecksum function.
- 500 — Trying to pass a table-valued parameter with %d column(s) where the corresponding user-defined table type requires %d column(s).
- 502 — The SQL Debugging Interface (SDI) requires that SQL Server, when started as a service, must not log on as System Account. Reset to log on as user acco…
- 503 — Unable to send symbol information to debugger on %ls for connection %d. Debugging disabled.
- 504 — Unable to connect to debugger on %ls (Error = 0x%08x). Ensure that client-side components, such as SQLDBREG.EXE, are installed and registered on %.*ls…
- 505 — The current user account was invoked with SETUSER or SP_SETAPPROLE. Changing databases is not allowed.
- 506 — The invalid escape character "%.*ls" was specified in a %ls predicate.
- 507 — Invalid argument for SET ROWCOUNT. Must be a non-null non-negative integer.
- 508 — Unable to connect to debugger on %ls (Error = 0x%08x). Ensure that client-side components, such as SQLLE.DLL, are installed and registered on %.*ls. D…
- 509 — User name '%.*ls' not found.
- 510 — Cannot create a worktable row larger than allowable maximum. Resubmit your query with the ROBUST PLAN hint.
- 511 — Cannot create a row of size %d which is greater than the allowable maximum row size of %d.
- 512 — Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expressio…
- 513 — A column insert or update conflicts with a rule imposed by a previous CREATE RULE statement. The statement was terminated. The conflict occurred in da…
- 514 — Unable to communicate with debugger on %ls (Error = 0x%08x). Debugging disabled for connection %d.
- 515 — Cannot insert the value NULL into column '%.*ls', table '%.*ls'; column does not allow nulls. %ls fails.
- 516 — Attempt to initialize OLE DB library failed. Check for correct versions of OLE DB DLLs on this computer.
- 517 — Adding a value to a '%ls' column caused an overflow.
- 518 — Cannot convert data type %ls to %ls.
- 520 — SQL Server no longer supports version %d of the SQL Debugging Interface (SDI).
- 521 — Cannot load the DLL %ls, or one of the DLLs it references. Reason: %ls Please insure server-side SQL debugger components are installed.
- 522 — The WAITFOR thread was evicted.
- 523 — A trigger returned a resultset and/or was running with SET NOCOUNT OFF while another outstanding result set was active.
- 524 — A trigger returned a resultset and the server option 'disallow results from triggers' is true.
- 525 — The 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 …
- 526 — %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 q…
- 527 — Implicit conversion between XML types constrained by different XML schema collections is not allowed. Use the CONVERT function to run this query.
- 529 — Explicit conversion from data type %ls to %ls is not allowed.
- 530 — The statement terminated. The maximum recursion %d has been exhausted before statement completion.
- 531 — Cannot set NOCOUNT to OFF inside the trigger execution because the server option "disallow_results_from_triggers" is true or we are inside LOGON trigg…
- 532 — The timestamp (changed to %S_TS) shows that the row has been updated by another user.
- 533 — Cannot set XACT ABORT to OFF inside the trigger execution.
- 534 — '%.*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…
- 535 — The %.*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 prec…
- 536 — Invalid length parameter passed to the %ls function.
- 537 — Invalid length parameter passed to the LEFT or SUBSTRING function.
- 539 — Schema changed after the target table was created. Rerun the Select Into query.
- 540 — There is insufficient system memory to run RAISERROR.
- 541 — There is not enough stack to execute the statement
- 542 — An invalid datetime value was encountered. Value exceeds the year 9999.
- 543 — Creation of a return table failed for the table valued function '%.*ls'.
- 544 — Cannot insert explicit value for identity column in table '%.*ls' when IDENTITY_INSERT is set to OFF.
- 545 — Explicit 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…
- 547 — The %ls statement conflicted with the %ls constraint "%.*ls". The conflict occurred in database "%.*ls", table "%.*ls"%ls%.*ls%ls.
- 548 — The insert failed. It conflicted with an identity range check constraint in database '%.*ls', replicated table '%.*ls'%ls%.*ls%ls. If the identity col…
- 549 — The collation '%.*ls' of receiving variable is not equal to the collation '%.*ls' of column '%.*ls'.
- 550 — The attempted insert or update failed because the target view either specifies WITH CHECK OPTION or spans a view that specifies WITH CHECK OPTION and …
- 551 — The checksum has changed to %d. This shows that the row has been updated by another user.
- 552 — CryptoAPI function '%ls' failed. Error 0x%x: %ls
- 555 — User-defined functions are not yet enabled.
- 556 — INSERT EXEC failed because the stored procedure altered the schema of the target table.
- 557 — Only functions and some extended stored procedures can be executed from within a function.
- 558 — Remote function calls are not allowed within a function.
- 561 — Failed to access file '%.*ls'
- 562 — Failed to access file '%.*ls'. Files can be accessed only through shares
- 563 — The transaction for the INSERT EXEC statement has been rolled back. The INSERT EXEC operation will be terminated.
- 564 — Attempted to create a record with a fixed length of '%d'. Maximum allowable fixed length is '%d'.
- 565 — A stack overflow occurred in the server while compiling the query. Please simplify the query.
- 566 — An error occurred while writing an audit trace. SQL Server is shutting down. Check and correct error conditions such as insufficient disk space, and t…
- 567 — File '%.*ls' is not a recognizable trace file.
- 568 — Encountered an error or an unexpected end of trace file '%.*ls'.
- 569 — The handle that was passed to %ls was invalid.
- 570 — INSTEAD OF triggers do not support direct recursion. The trigger execution failed.
- 571 — The specified attribute value for %ls is invalid.
- 572 — Invalid regular expression "%.*ls" near the offset %d.
- 573 — Evaluation of the regular expression is too complex: '%.*ls'.
- 574 — %ls statement cannot be used inside a user transaction.
- 575 — A LOGON trigger returned a resultset. Modify the LOGON trigger to not return resultsets.
- 576 — Cannot create a row that has sparse data of size %d which is greater than the allowable maximum sparse data size of %d.
- 577 — The value provided for the timeout is not valid. Timeout must be a valid integer between 0 and 2147483647.
- 578 — Insert Exec not allowed in WAITFOR queries.
- 579 — Can not execute WAITFOR query with snapshot isolation level.
- 582 — Offset is greater than the length of the column to be updated in write.
- 583 — Negative offset or length in write.
- 584 — Select Into not allowed in WAITFOR queries.
- 585 — Changing database context is not allowed when populating the resource database.
- 586 — The prepared statement handle %d is not valid in this context. Please verify that current database, user default schema, and ANSI_NULLS and QUOTED_IDE…
- 587 — An invalid delayed CLR type fetch token is provided.
- 588 — Multiple tasks within the session are using the same delayed CLR type fetch token at the same time.
- 589 — This statement has attempted to access data whose access is restricted by the assembly.
- 590 — RPC was aborted without execution.
- 591 — %ls: The formal parameter "%ls" was defined as OUTPUT, but the actual parameter was not declared as OUTPUT.
- 592 — Cannot find %S_MSG ID %d in database ID %d.
- 593 — fn_trace_gettable: XML conversion of trace data for event 165 failed.
- 594 — fn_trace_gettable: XML conversion of trace data is not supported in fiber mode.
- 595 — Bulk Insert with another outstanding result set should be run with XACT_ABORT on.
- 596 — Cannot continue the execution because the session is in the kill state.
- 597 — The execution of in-proc data access is being terminated due to errors in the User Datagram Protocol (UDP).
- 598 — An error occurred while executing CREATE/ALTER DB. Please look at the previous error for more information.
- 599 — %.*ls: The length of the result exceeds the length limit (2GB) of the target large type.
- 601 — Could not continue scan with NOLOCK due to data movement.
- 602 — Could 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 tab…
- 603 — Could 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 reference…
- 605 — Attempt to fetch logical page %S_PGID in database %d failed. It belongs to allocation unit %I64d not to %I64d.
- 606 — Metadata inconsistency. Filegroup id %ld specified for table '%.*ls' does not exist. Run DBCC CHECKDB or CHECKCATALOG.
- 608 — No catalog entry found for partition ID %I64d in database %d. The metadata is inconsistent. Run DBCC CHECKDB to check for a metadata corruption.
- 609 — BTree is not empty when waking up on RowsetBulk.
- 610 — Invalid header value from a page. Run DBCC CHECKDB to check for a data corruption.
- 611 — Cannot insert or update a row because total variable column size, including overhead, is %d bytes more than the limit.
- 613 — Could not find an entry for worktable rowset with partition ID %I64d in database %d.
- 614 — Could not locate bookmark due to data movement.
- 615 — Could not find database ID %d, name '%.*ls'. The database may be offline. Wait a few minutes and try again.
- 617 — Descriptor 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 qu…
- 622 — The filegroup "%.*ls" has no files assigned to it. Tables, indexes, text columns, ntext columns, and image columns cannot be populated on this filegro…
- 627 — Cannot use SAVE TRANSACTION within a distributed transaction.
- 628 — Cannot issue SAVE TRANSACTION when there is no active transaction.
- 645 — The type of filegroup "%.*ls" is not supported by this operation.
- 646 — Filegroup "%.*ls" is not valid for this operation.
- 647 — Cannot disable %ls because a column of object id %d is collated in %ls. Please remove all references to that collation before disabling this feature.
- 648 — Cannot disable %ls because database-default collation is %ls. Please remove all references to that collation before disabling this feature.
- 650 — You can only specify the READPAST lock in the READ COMMITTED or REPEATABLE READ isolation levels.
- 651 — Cannot use the %ls granularity hint on the table "%.*ls" because locking at the specified granularity is inhibited.
- 652 — The index "%.*ls" for table "%.*ls" (RowsetId %I64d) resides on a read-only filegroup ("%.*ls"), which cannot be modified.
- 657 — Could not disable support for %ls in database '%.*ls' because %S_MSG.
- 658 — Could not enable support for %ls in database '%.*ls' because %S_MSG.
- 661 — Cannot enable support for %ls in database '%.*ls' because support for %ls is enabled and both are mutually exclusive.
- 663 — Wait for redo catchup for the database "%.*ls" is taking longer than "%d" seconds for the LSN "%S_LSN".
- 664 — Aborting the query because it is trying to do logical revert on a readable secondary.
- 666 — The maximum system-generated unique value for a duplicate group was exceeded for index with partition ID %I64d. Dropping and re-creating the index may…
- 667 — The index "%.*ls" for table "%.*ls" (RowsetId %I64d) resides on a filegroup ("%.*ls") that cannot be accessed because it is offline, is being restored…
- 669 — The row object is inconsistent. Please rerun the query.
- 670 — Large object (LOB) data for table "%.*ls" resides on an offline filegroup ("%.*ls") that cannot be accessed.
- 671 — Large object (LOB) data for table "%.*ls" resides on a read-only filegroup ("%.*ls"), which cannot be modified.
- 672 — Failed to queue cleanup packets for orphaned rowsets in database "%.*ls". Some disk space may be wasted. Cleanup will be attempted again on database r…
- 673 — Failure to access row object in snapshot isolation. Error code 0x%X.
- 674 — Exception occurred in destructor of RowsetNewSS 0x%p. This error may indicate a problem related to releasing pre-allocated disk blocks used during bul…
- 675 — Worktable with partition ID %I64d was dropped successfully after %d repeated attempts.
- 676 — Error occurred while attempting to drop worktable with partition ID %I64d.
- 677 — Unable to drop worktable with partition ID %I64d after repeated attempts. Worktable is marked for deferred drop. This is an informational message only…
- 678 — Active rowset for partition ID %I64d found at the end of the batch. This error may indicate incorrect exception handling. Use the current activity win…
- 679 — One of the partitions of index '%.*ls' for table '%.*ls'(partition ID %I64d) resides on a filegroup ("%.*ls") that cannot be accessed because it is of…
- 680 — Error [%d, %d, %d] occurred while attempting to drop allocation unit ID %I64d belonging to worktable with partition ID %I64d.
- 681 — Attempting to set a non-NULL-able column's value to NULL.
- 682 — Internal error. Buffer provided to read column value is too small. Run DBCC CHECKDB to check for any corruption.
- 683 — An internal error occurred while trying to convert between variable-length and fixed-length decimal formats. Run DBCC CHECKDB to check for any databas…
- 684 — An internal error occurred while attempting to convert between compressed and uncompressed storage formats. Run DBCC CHECKDB to check for any corrupti…
- 685 — An internal error occurred while attempting to retrieve a backpointer for a heap forwarded record.
- 686 — The maximum level of the B-Tree for rowset %I64d has been reached. SQL Server only supports upto 255 levels.
- 687 — Cannot compress a nchar or nvarchar column that has an odd number of bytes.
- 688 — Operation not allowed due to an active online index build.
- 689 — Operation not allowed because of pending cleanup of online index build. Wait for cleanup to complete and re-run the operation.
- 691 — An internal error occurred. Error code %X.
- 692 — Internal error. Buffer provided to write a fixed column value is too large. Run DBCC CHECKDB to check for any corruption.
- 694 — Internal error. Unable to create a block blob in Azure storage.
- 695 — Internal error. Unable to delete a block blob in Azure storage.
- 696 — Internal error. Unable to gain access to the tombstone table.
- 697 — Internal error. Unable to get a blob storage container.
- 698 — Internal error. Unable to gain access to the blob container accessor.
- 699 — Failure to read data expected in Azure Block Blob Storage. Error code 0x%X.
- 701 — There is insufficient system memory in resource pool '%ls' to run this query.
- 708 — Server is running low on virtual address space or machine is running low on virtual memory. Reserved memory used %d times since startup. Cancel query …
- 709 — The available memory for this SQL Server instance (%I64u MB) is lower than the configured maximum server memory (%I64u MB). This might occur because o…
- 801 — A buffer was encountered with an unexpected status of 0x%x.
- 802 — There is insufficient memory available in the buffer pool.
- 803 — simulated failure (DEBUG only)
- 805 — restore pending
- 806 — audit failure (a page read from disk failed to pass basic integrity checks)
- 807 — (no disk or the wrong disk is in the drive)
- 808 — Insufficient bytes transferred. Common causes are backup configuration, insufficient disk space, or other problems with the storage subsystem such as …
- 810 — The operating system returned error %ls to SQL Server during a %S_MSG at offset %#016I64x in file '%ls'. This is intended to raise only in Azure SQL D…
- 821 — Could 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. Con…
- 822 — Could not start I/O operation for request %S_BLKIOPTR. Contact Technical Support.
- 823 — The 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 l…
- 824 — SQL 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 f…
- 825 — A 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 o…
- 826 — incorrect pageid (expected %d:%d; actual %d:%d)
- 829 — Database ID %d, Page %S_PGID is marked RestorePending, which may indicate disk corruption. To recover from this state, perform a restore.
- 830 — stale 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))
- 831 — Unable to deallocate a kept page.
- 832 — A page that should have been constant has changed (expected checksum: %08x, actual checksum: %08x, database %d, file '%ls', page %S_PGID). This usuall…
- 833 — SQL 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 han…
- 835 — The 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…
- 836 — Database ID %d, stale page %S_PGID is under restoring.
- 837 — The operating system returned error %ls to SQL Server during a %S_MSG at offset %#016I64x in file '%ls'. This error can be caused when a remote IO fai…
- 838 — An asynchronous API call (%ls) hasn't returned in %I64u ms. Non-yielding scheduler errors might occur.
- 844 — 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 : %…
- 845 — Time-out occurred while waiting for buffer latch type %d for page %S_PGID, database ID %d.
- 846 — A 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 :…
- 847 — Timeout 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. Continuin…
- 848 — Using large pages in the memory manager.
- 849 — Using locked pages in the memory manager.
- 850 — %I64u MB of large page memory allocated.
- 851 — the page is in an OFFLINE file which cannot be read
- 852 — Using conventional memory in the memory manager.
- 853 — Latch acquire failed due to too many concurrent latches. type %d, Task 0x%p : %d
- 854 — Machine supports memory error recovery. SQL memory protection is enabled to recover from memory corruption.
- 855 — Uncorrectable hardware memory corruption detected. Your system may become unstable. Please check the operating system error log for more details.
- 856 — SQL Server has detected hardware memory corruption in database '%ls', file ID: %u, page ID; %u, memory address: 0x%I64x and has successfully recovered…
- 857 — Buffer pool extension "%.*ls" has been initialized successfully with size is %I64d MB.
- 858 — Failed to create buffer pool extension of size %I64d MB on path "%.*ls".
- 859 — Buffer pool extension configuration "%.*ls" is in wrong format. The format should be "<extension directory>,<size in GB>".
- 860 — %ls. BUF address %p. Bufno %u. Extension offset %1I64d. Error code %d. Database file id %u. Database file offset %2I64d.
- 861 — Buffer pool extension size must be larger than the physical memory size %I64d MB. Buffer pool extension is not enabled.
- 862 — Attempt to disable buffer pool extension when in state %ls is not allowed.
- 863 — Attempt to enable buffer pool extension when in state %ls is not allowed.
- 864 — Attempted to initialize buffer pool extension of size %1ld KB, but maximum allowed size is %2ld KB.
- 865 — Buffer pool extension is only supported on Standard and Enterprise Editions of SQL Server.
- 866 — Buffer pool extension is not supported on the %ls architecture.
- 867 — Buffer pool extension has been disabled successfully. Deleting buffer pool extension "%.*ls".
- 868 — Buffer pool extension size must be larger than the current memory allocation threshold %I64d MB. Buffer pool extension is not enabled.
- 869 — Buffer pool extension "%.*ls" cannot be closed because %ld asynchronous I/Os are outstanding.
- 870 — BPE feature switch is on!
- 871 — Buffer pool extension size from RG Setting is %d GB (%I64d bytes).
- 872 — Buffer pool extension is already enabled. No action is necessary.
- 873 — Buffer pool extension is already disabled. No action is necessary.
- 874 — Failed to initialize resilient buffer pool extension of size %I64d MB on path "%.*ls".
- 875 — Resilient buffer pool extension "%.*ls" has been started successfully with size is %I64d MB.
- 876 — Failed to startup resilient buffer pool extension of size %I64d MB on path "%.*ls".
- 877 — Resilient buffer pool extension "%.*ls" has been enabled successfully with size %I64d MB.
- 878 — Failed to create resilient buffer pool extension of size %I64d MB on path "%.*ls".
- 879 — Failed to start resilient buffer pool extension because database %d is not memory optimized.
- 880 — Failed to find the metadata of resilient buffer pool extension in database %d.
- 881 — Resilient buffer pool extension is already disabled. No action is necessary.
- 882 — The schema of a table created by InternalBaseTable is corrupt.
- 883 — Could not create the Write Page Recorder table: wpr_bucket_table for database %ls.
- 884 — Could not persist a bucket to the Write Page Recorder table: wpr_bucket_table for database %ls.
- 885 — An internal error occurred. Error code %X. Context: "%ls::%d".
- 886 — Resilient buffer pool extension is already enabled. No action is necessary.
- 887 — Invalid RBPEX operation. Error: %ls.
- 888 — Resilient buffer pool extension must be enabled while running this operation '%ls'.
- 889 — Resilient buffer pool extension must be disabled while running this operation '%ls'.
- 890 — Could not create, retrieve or persist a bucket for the Write Page Recorder in database %ls.
- 891 — Buffer pool extension is not supported on %ls platform.
- 892 — Using shared memory in the memory manager.
- 893 — Failed to release latch. BUF address %p. Database ID %d. File ID %d. Page %S_PGID.
- 894 — Buffer Pool: Allocating %I64u bytes for %I64d hashPages.
- 895 — Hybrid buffer Pool: proposing %I64d hashPages for %I64u GiB of %S_MSG Persistent Memory.
- 896 — Failed to disable buffer pool extension.
- 897 — Buffer pool extension was paused due to error.
- 898 — Buffer Pool scan took %I64d seconds: database ID %d, command '%ls', operation '%ls', scanned buffers %I64d, total iterated buffers %I64d, wait time %I…
- 899 — Failed to disable Resilient buffer pool extension.
- 900 — Failed to start buffer pool extension because the file configuration has changed and is incompatible with the existing one.
- 902 — To change the %ls, the database must be in state in which a checkpoint can be executed.
- 904 — Database %ld cannot be autostarted during server shutdown or startup.
- 905 — Database '%.*ls' cannot be started in this edition of SQL Server because it contains a partition function '%.*ls'. Only Enterprise edition of SQL Serv…
- 907 — The database "%ls" has inconsistent database or file metadata.
- 908 — Filegroup %ls in database %ls is unavailable because it is %ls. Restore or alter the filegroup to be available.
- 909 — Database '%.*ls' cannot be started in this edition of SQL Server because part or all of object '%.*ls' is enabled with data compression or vardecimal …
- 910 — Database '%.*ls' is upgrading script '%.*ls' from level %d to level %d.
- 911 — Database '%.*ls' does not exist. Make sure that the name is entered correctly.
- 912 — Script level upgrade for database '%.*ls' failed because upgrade step '%.*ls' encountered error %d, state %d, severity %d. This is a serious error con…
- 913 — Could 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 …
- 914 — Script level upgrade for database '%.*ls' failed because upgrade step '%.*ls' was aborted before completion. If the abort happened during upgrade of t…
- 915 — Unable to obtain the current script level for database '%.*ls'. If the error happened during startup of the 'master' database, it will prevent the ent…
- 916 — The server principal "%.*ls" is not able to access the database "%.*ls" under the current security context.
- 917 — An upgrade script batch failed to execute for database '%.*ls' due to compilation error. Check the previous error message for the line which caused co…
- 918 — Failed 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 con…
- 919 — User '%.*ls' is changing database script level entry %d to a value of %d.
- 920 — Only members of the sysadmin role can modify the database script level.
- 921 — Database '%.*ls' has not been recovered yet. Wait and try again.
- 922 — Database '%.*ls' is being recovered. Waiting until recovery is finished.
- 923 — Database '%.*ls' is in restricted mode. Only the database owner and members of the dbcreator and sysadmin roles can access it.
- 924 — Database '%.*ls' is already open and can only have one user at a time.
- 925 — Maximum number of databases used for each query has been exceeded. The maximum allowed is %d.
- 926 — Database '%.*ls' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
- 927 — Database '%.*ls' cannot be opened. It is in the middle of a restore.
- 928 — During upgrade, database raised exception %d, severity %d, state %d, address %p. Use the exception number to determine the cause.
- 929 — Unable to close a database that is not currently open. The application should reconnect and try again. If this action does not correct the problem, co…
- 930 — Attempting to reference recovery unit %d in database '%ls' which does not exist. Contact Technical Support.
- 931 — Attempting to reference database fragment %d in database '%ls' which does not exist. Contact Technical Support.
- 932 — SQL Server cannot load database '%.*ls' because change tracking is enabled. The currently installed edition of SQL Server does not support change trac…
- 933 — Database '%.*ls' cannot be started because some of the database functionality is not available in the current edition of SQL Server.
- 934 — SQL Server cannot load database '%.*ls' because Change Data Capture is enabled. The currently installed edition of SQL Server does not support Change …
- 935 — The 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 fu…
- 936 — Database '%.*ls' can not be used in this edition of SQL Server.
- 937 — Database '%.*ls' cannot be upgraded because '%.*ls' functionality is not available in the current edition of SQL Server.
- 938 — The target database version %d is not supported by the current code version %d. Change target version to a supported level and restart the server.
- 939 — Database '%.*ls' cannot be started because it failed to initialize the persistent version store due to error %d. Refer to previous errors in the error…
- 941 — Database '%.*ls' cannot be opened because it is not started. Retry when the database is started.
- 942 — Database '%.*ls' cannot be opened because it is offline.
- 943 — Database '%.*ls' cannot be opened because its version (%d) is later than the current server version (%d).
- 944 — Converting database '%.*ls' from version %d to the current version %d.
- 945 — Database '%.*ls' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
- 946 — Cannot open database '%.*ls' version %d. Upgrade the database to the latest version.
- 947 — Error while closing database '%.*ls'. Check for previous additional errors and retry the operation.
- 948 — The database '%.*ls' cannot be opened because it is version %d. This server supports version %d and earlier. A downgrade path is not supported.
- 949 — tempdb is skipped. You cannot run a query that requires tempdb
- 950 — Database '%.*ls' cannot be upgraded because its non-release version (%d) is not supported by this version of SQL Server. You cannot open a database th…
- 951 — Database '%.*ls' running the upgrade step from version %d to version %d.
- 952 — Database '%.*ls' is in transition. Try the statement later.
- 954 — The database "%.*ls" cannot be opened. It is acting as a mirror database.
- 955 — Database %.*ls is enabled for Database Mirroring, but the database lacks quorum: the database cannot be opened. Check the partner and witness connecti…
- 956 — Database %.*ls is enabled for Database Mirroring, but has not yet synchronized with its partner. Try the operation again later.
- 957 — Database '%.*ls' is enabled for database mirroring or has joined an availability group. The name of the database cannot be changed.
- 958 — The resource database build version is %.*ls. This is an informational message only. No user action is required.
- 959 — The resource database version is %d and this server supports version %d. Restore the correct version or reinstall SQL Server.
- 960 — Warning: 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 SQ…
- 961 — Warning: 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 …
- 962 — Warning: Primary key or Unique constraint "%.*ls" (object_id = %d) in database "%.*ls" was renamed to "%.*ls" because its index was renamed.
- 963 — Warning: Database "%.*ls" was marked suspect because of actions taken during upgrade. See errorlog or eventlog for more information. Use ALTER DATABAS…
- 964 — Warning: System user '%.*ls' was found missing from database '%.*ls' and has been restored. This user is required for SQL Server operation.
- 965 — Warning: A column nullability inconsistency was detected in the metadata of index "%.*ls" (index_id = %d) on object ID %d in database "%.*ls". The ind…
- 966 — Warning: Assembly "%.*ls" in database "%.*ls" has been renamed to "%.*ls" because the name of the assembly conflicts with a system assembly in this ve…
- 967 — Warning: 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 whi…
- 968 — Warning: The XML facet on type "%.*ls" in schema collection "%.*ls" is updated from "%.*ls" to "%.*ls" because Sql Server does not support negative ye…
- 969 — Warning: The default or fixed value on XML element or attribute "%.*ls" in schema collection "%.*ls" is updated from "%.*ls" to "%.*ls" because Sql Se…
- 970 — Warning: 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 im…
- 971 — The resource database has been detected in two different locations. Attaching the resource database in the same directory as sqlservr.exe at '%.*ls' i…
- 972 — Could not use database '%d' during procedure execution.
- 973 — Database %ls was started . However, FILESTREAM is not compatible with the READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION options. Either remove …
- 974 — Attaching the resource database in the same directory as sqlservr.exe at '%.*ls' failed as the database files do not exist.
- 975 — System objects could not be updated in database '%.*ls' because it is read-only.
- 976 — The target database, '%.*ls', is participating in an availability group and is currently not accessible for queries. Either data movement is suspended…
- 977 — Warning: Could not find associated index for the constraint '%.*ls' on object_id '%d' in database '%.*ls'.
- 978 — The target database ('%.*ls') is in an availability group and is currently accessible for connections when the application intent is set to read only.…
- 979 — The target database ('%.*ls') is in an availability group and currently does not allow read only connections. For more information about application i…
- 980 — SQL Server cannot load database '%.*ls' because it contains a columnstore index. The currently installed edition of SQL Server does not support column…
- 981 — Database manager will be using %d target database version.
- 982 — Unable to access the '%.*ls' database because no online secondary replicas are enabled for read-only access. Check the availability group configuratio…
- 983 — Unable to access availability database '%.*ls' because the database replica is not in the PRIMARY or SECONDARY role. Connections to an availability da…
- 984 — Failed to perform a versioned copy of sqlscriptdowngrade.dll from Binn to Binn\Cache folder. VerInstallFile API failed with error code %d.
- 985 — Successfully installed the file '%ls' into folder '%ls'.
- 986 — Couldn't get a clean bootpage for database '%.*ls' after %d tries. This is an informational message only. No user action is required.
- 987 — A duplicate key insert was hit when updating system objects in database '%.*ls'.
- 988 — Unable to access database '%.*ls' because it lacks a quorum of nodes for high availability. Try the operation again later.
- 989 — Failed to take the host database with ID %d offline when one or more of its partition databases is marked as suspect.
- 990 — Taking the host database with ID %d offline because one or more of its partition databases is marked as suspect.
- 991 — Failed to take the host database '%.*ls' offline when one or more of its partition databases is marked as suspect.
- 992 — Failed to get the shared lock on database '%.*ls'.
- 993 — Redo for database '%.*ls' applied version upgrade step from %d to %d.
- 994 — Warning: Index "%.*ls" on "%.*ls"."%.*ls" is disabled because it contains a computed column.
- 995 — Warning: Index "%.*ls" on "%.*ls"."%.*ls" is disabled. It cannot be upgraded as it resides on a read-only filegroup.
- 996 — Warning: Index "%.*ls" on "%.*ls"."%.*ls" is disabled. This columnstore index cannot be upgraded, likely because it exceeds the row size limit of '%d'…
- 997 — Failed to get the update lock on database '%.*ls'.
- 998 — Database '%.*ls' does not exist in server '%.*ls'. Please make sure that the name is entered correctly.
- 999 — Failed to acquire background subresource lock on database '%.*ls' for delayed version upgrade.
- 1001 — Line %d: Length or precision specification %d is invalid.
- 1002 — Line %d: Specified scale %d is invalid.
- 1003 — Line %d: %ls clause allowed only for %ls.
- 1004 — Invalid column prefix '%.*ls': No table name specified
- 1005 — Line %d: Invalid procedure number (%d). Must be between 1 and 32767.
- 1006 — CREATE TRIGGER contains no statements.
- 1007 — The %S_MSG '%.*ls' is out of the range for numeric representation (maximum precision 38).
- 1008 — The SELECT item identified by the ORDER BY number %d contains a variable as part of the expression identifying a column position. Variables are only a…
- 1009 — The keyword DEFAULT is not allowed in DBCC commands.
- 1010 — Invalid escape character '%.*ls'.
- 1011 — The correlation name '%.*ls' is specified multiple times in a FROM clause.
- 1012 — The correlation name '%.*ls' has the same exposed name as table '%.*ls'.
- 1013 — The objects "%.*ls" and "%.*ls" in the FROM clause have the same exposed names. Use correlation names to distinguish them.
- 1014 — A TOP or FETCH clause contains an invalid value.
- 1015 — An aggregate cannot appear in an ON clause unless it is in a subquery contained in a HAVING clause or select list, and the column being aggregated is …
- 1016 — Outer join operators cannot be specified in a query containing joined tables.
- 1017 — The %ls hint cannot be specified more than once.
- 1018 — Incorrect syntax near '%.*ls'. If this is intended as a part of a table hint, A WITH keyword and parenthesis are now required. See SQL Server Books On…
- 1019 — Invalid column list after object name in GRANT/REVOKE statement.
- 1020 — Sub-entity lists (such as column or security expressions) cannot be specified for entity-level permissions.
- 1021 — FIPS Warning: Line %d has the non-ANSI statement '%ls'.
- 1022 — FIPS Warning: Line %d has the non-ANSI clause '%ls'.
- 1023 — Invalid parameter %d specified for %ls.
- 1024 — FIPS Warning: Line %d has the non-ANSI function '%ls'.
- 1025 — FIPS Warning: The length of identifier '%.*ls' exceeds 18.
- 1026 — GOTO cannot be used to jump into a TRY or CATCH scope.
- 1027 — Too many expressions are specified in a CUBE in the GROUP BY clause. The maximum number is %d.
- 1028 — The CUBE, ROLLUP, and GROUPING SETS constructs are not allowed in a GROUP BY ALL clause.
- 1029 — Browse mode is invalid for subqueries and derived tables.
- 1030 — Only constants are allowed here. Time literal is not permitted because it refers to the current date.
- 1031 — Percent values must be between 0 and 100.
- 1032 — Cannot use the column prefix '%.*ls'. This must match the object in the UPDATE clause '%.*ls'.
- 1033 — The ORDER BY clause is invalid in views, inline functions, derived tables, subqueries, and common table expressions, unless TOP, OFFSET or FOR XML is …
- 1034 — Syntax error: Duplicate specification of the action "%.*s" in the trigger declaration.
- 1035 — Incorrect syntax near '%.*ls', expected '%.*ls'.
- 1036 — File option %hs is required in this CREATE/ALTER DATABASE statement.
- 1037 — The CASCADE, WITH GRANT or AS options cannot be specified with statement permissions.
- 1038 — An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias na…
- 1039 — Option '%.*ls' is specified more than once.
- 1040 — The value %d used with MAX_OUTSTANDING_IO_PER_VOLUME is not valid; MAX_OUTSTANDING_IO_PER_VOLUME must be greater than 0 and less than or equal to %d.
- 1041 — Option %.*ls is not allowed for a LOG file.
- 1042 — Conflicting %ls optimizer hints specified.
- 1043 — '%.*ls' is not yet implemented.
- 1044 — Cannot use an existing function name to specify a stored procedure name.
- 1045 — Aggregates are not allowed in this context. Only scalar expressions are allowed.
- 1046 — Subqueries are not allowed in this context. Only scalar expressions are allowed.
- 1047 — Conflicting locking hints specified.
- 1048 — Conflicting cursor options %ls and %ls.
- 1049 — Mixing old and new syntax to specify cursor options is not allowed.
- 1050 — This syntax is only allowed for parameterized queries.
- 1051 — Cursor parameters in a stored procedure must be declared with OUTPUT and VARYING options, and they must be specified in the order CURSOR VARYING OUTPU…
- 1052 — Conflicting %ls options "%ls" and "%ls".
- 1053 — For DROP STATISTICS, you must provide both the object (table or view) name and the statistics name, in the form "objectname.statisticsname".
- 1054 — Syntax '%ls' is not allowed in schema-bound objects.
- 1055 — '%.*ls' is an invalid name because it contains a NULL character or an invalid unicode character.
- 1056 — The number of elements in the select list exceeds the maximum allowed number of %d elements.
- 1057 — The IDENTITY function cannot be used with a SELECT INTO statement containing a UNION, INTERSECT or EXCEPT operator.
- 1058 — Cannot specify both READ_ONLY and FOR READ ONLY on a cursor declaration.
- 1059 — Cannot set or reset the 'parseonly' option within a procedure or function.
- 1060 — The number of rows provided for a TOP or FETCH clauses row count parameter must be an integer.
- 1061 — The text/ntext/image constants are not yet implemented.
- 1062 — The TOP N WITH TIES clause is not allowed without a corresponding ORDER BY clause.
- 1063 — A filegroup cannot be added using ALTER DATABASE ADD FILE. Use ALTER DATABASE ADD FILEGROUP.
- 1064 — A filegroup cannot be used with log files.
- 1065 — The NOLOCK and READUNCOMMITTED lock hints are not allowed for target tables of INSERT, UPDATE, DELETE or MERGE statements.
- 1066 — Warning. Line %d: The option '%ls' is obsolete and has no effect.
- 1067 — The SET SHOWPLAN statements must be the only statements in the batch.
- 1068 — Only one list of index hints per table is allowed.
- 1069 — Index hints are only allowed in a FROM or OPTION clause.
- 1070 — CREATE INDEX option '%.*ls' is no longer supported.
- 1071 — Cannot specify a JOIN algorithm with a remote JOIN.
- 1072 — A REMOTE hint can only be specified with an INNER JOIN clause.
- 1073 — '%.*ls' is not a recognized cursor option for cursor %.*ls.
- 1074 — Creation of temporary functions is not allowed.
- 1075 — RETURN statements in scalar valued functions must include an argument.
- 1076 — Function '%s' requires at least %d argument(s).
- 1077 — INSERT into an identity column not allowed on table variables.
- 1078 — '%.*ls %.*ls' is not a recognized option.
- 1079 — A variable cannot be used to specify a search condition in a fulltext predicate when accessed through a cursor.
- 1080 — The integer value %.*ls is out of range.
- 1081 — %s does not allow specifying the database name as a prefix to the assembly name.
- 1082 — "%.*ls" does not support synchronous trigger registration.
- 1083 — OWNER is not a valid option for EXECUTE AS in the context of server and database level triggers.
- 1084 — '%.*ls' is an invalid event type.
- 1085 — '%.*ls' event type does not support event notifications.
- 1086 — The FOR XML and FOR JSON clauses are invalid in views, inline functions, derived tables, and subqueries when they contain a set operator. To work arou…
- 1087 — Must declare the table variable "%.*ls".
- 1088 — Cannot find the object "%.*ls" because it does not exist or you do not have permissions.
- 1089 — The SET FMTONLY OFF statement must be the last statement in the batch.
- 1090 — Invalid default for parameter %d.
- 1091 — The option "%ls" is not valid for this function.
- 1092 — In this context %d statistics name(s) cannot be specified for option '%ls'.
- 1093 — "%.*ls" is not a valid broker name.
- 1094 — Cannot specify a schema name as a prefix to the trigger name for database and server level triggers.
- 1095 — "%.*ls" has already been specified as an event type.
- 1096 — Default parameter values for CLR types, nvarchar(max), varbinary(max), xml and encrypted types are not supported.
- 1097 — Cannot use If UPDATE within this CREATE TRIGGER statement.
- 1098 — The specified event type(s) is/are not valid on the specified target object.
- 1099 — The ON clause is not valid for this statement.
- 1101 — Could not allocate a new page for database '%.*ls' because of insufficient disk space in filegroup '%.*ls'. Create the necessary space by dropping obj…
- 1102 — IAM page %S_PGID for object ID %ld is incorrect. The %S_MSG ID on page is %ld; should be %ld.
- 1104 — TEMPDB ran out of space during spilling. Create space by dropping objects and/or rewrite the query to consume fewer rows. If the issue still persists,…
- 1105 — Could not allocate space for object '%.*ls'%.*ls in database '%.*ls' because the '%.*ls' filegroup is full. Create disk space by deleting unneeded fil…
- 1119 — Removing IAM page %S_PGID failed because someone else is using the object that this IAM page belongs to.
- 1121 — Space allocator cannot allocate page in database %d.
- 1122 — Table error: Page %S_PGID. Test (%ls) failed. Address 0x%x is not aligned.
- 1123 — Table error: Page %S_PGID. Unexpected page type %d.
- 1124 — Table error: Page %S_PGID. Test (%ls) failed. Slot %d, offset 0x%x is invalid.
- 1125 — Table error: Page %S_PGID. Test (%ls) failed. Slot %d, row extends into free space at 0x%x.
- 1126 — Table error: Page %S_PGID. Test (%ls) failed. Slot %d, offset 0x%x overlaps with the prior row.
- 1127 — Table error: Page %S_PGID. Test (%ls) failed. Values are %ld and %ld.
- 1128 — Table error: Page (%d:%d), row %d. Test (%.*ls) failed. Values are %ld and %ld.
- 1129 — Could not cleanup deferred deallocations from filegroup '%.*ls'.
- 1130 — Error while allocating extent for a worktable. Extent %S_PGID in TEMPDB may have been lost.
- 1131 — Failed to truncate AppendOnlyStorageUnit 0x%p. Will retry next time. This is an informational message only. No user action is required.
- 1132 — The elastic pool has reached its storage limit. The storage usage for the elastic pool cannot exceed (%d) MBs.
- 1133 — The managed instance has reached its storage limit. The storage usage for the managed instance cannot exceed (%d) MBs.
- 1134 — Cannot restore database with data file size larger than max allowed data file size of (%d) MB on Azure SQL.
- 1135 — Cannot restore database with log file size larger than max allowed log file size of (%d) MB on Azure SQL.
- 1136 — The tempdb has reached its storage service limit. The storage usage of the tempdb on the current tier cannot exceed (%d) MBs.
- 1137 — The number of database files for Next-Gen General Purpose instances cannot exceed (%d).
- 1138 — Could not allocate a new page for database 'tempdb' because that would exceed the limit set for workload group '%ls', group_id %d.
- 1139 — Could not allocate a new page for database 'tempdb' because that would exceed the statement-level limit set for workload group '%ls'.
- 1202 — The database-principal '%.*ls' does not exist or user is not a member.
- 1203 — Process ID %d attempted to unlock a resource it does not own: %.*ls. Retry the transaction, because this error may be caused by a timing condition. If…
- 1204 — The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask…
- 1205 — Transaction (Process ID %d) was deadlocked on %.*ls resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
- 1206 — The Microsoft Distributed Transaction Coordinator (MS DTC) has cancelled the distributed transaction.
- 1207 — Can't allocate %u locks on startup, reverting to %u and turning on dynamic lock allocation. Maximum allowed memory usage at startup is %I64u KB.
- 1208 — Could not allocate initial %u lock blocks during startup. Can not start the server.
- 1209 — Could not allocate initial %u lock owner blocks during startup. Can not start the server.
- 1210 — Unable to allocate lock owner block during lock migration. Server halted.
- 1212 — Lock not logged: %-30ls Mode: %s
- 1213 — Error spawning Lock Monitor thread: %ls
- 1214 — Internal Error. There are too many parallel transactions.
- 1215 — A conflicting ABORT_AFTER_WAIT = BLOCKERS request is waiting for existing transactions to rollback. This request cannot be executed. Please retry when…
- 1216 — The DDL statement with ABORT_AFTER_WAIT = BLOCKERS option cannot be completed due to a conflicting system task. The request can abort only user transa…
- 1217 — Process ID %d was killed by an ABORT_AFTER_WAIT = BLOCKERS DDL statement on database_id = %d, object_id = %d.
- 1218 — An ABORT_AFTER_WAIT = BLOCKERS lock request was issued on database_id = %d, object_id = %d. All blocking user sessions will be killed.
- 1219 — Your session has been disconnected because of a high priority DDL operation.
- 1220 — No more lock classes available from transaction.
- 1221 — The Database Engine is attempting to release a group of locks that are not currently held by the transaction. Retry the transaction. If the problem pe…
- 1222 — Lock request time out period exceeded.
- 1223 — Cannot release the application lock (Database Principal: '%.*ls', Resource: '%.*ls') because it is not currently held.
- 1224 — An invalid application lock resource was passed to %ls.
- 1225 — An invalid application lock mode was passed to %ls.
- 1226 — An invalid application lock owner was passed to %ls.
- 1227 — An invalid application lock time-out was passed to %ls.
- 1228 — An invalid parameter "%ls" was passed to the application lock function or procedure.
- 1230 — An invalid database principal was passed to %ls.
- 1231 — Transaction (Process ID %d) was blocked/deadlocked but failed the attempt to generate blocked process/deadlock report.
- 1232 — Failed to acquire lock with lock manager service, it could be due to many reasons including transient service failure.
- 1233 — Transaction (session ID %d) was rolled back due to priority enforcement. A higher-priority transaction was waiting for a resource held by this lower-p…
- 1234 — SET TRANSACTION_PRIORITY option is invalid. Valid options are {HIGH | NORMAL | LOW | [%d ... %d]}.
- 1235 — SET TRANSACTION_PRIORITY is not supported on sessions with Multiple Active Result Sets (MARS) enabled.
- 1236 — Transaction (session ID %d) was rolled back due to priority enforcement while the session was idle. Rerun the transaction.
- 1237 — Setting TRANSACTION_PRIORITY above 0 (NORMAL) requires ALTER ANY CONNECTION or KILL DATABASE CONNECTION permission.
- 1238 — Could not extend all lock partitions during failover. Retry the operation.
- 1401 — Startup of the database-mirroring master thread routine failed for the following reason: %ls. Correct the cause of this error, and restart the SQL Ser…
- 1402 — Witness did not find an entry for database mirroring GUID {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. A configuration mismatch exists. Retry t…
- 1403 — The witness for the mirroring session received error response %d (state %d) from server instance %.*ls for database %.*ls. For more information about …
- 1404 — The command failed because the database mirror is busy. Reissue the command later.
- 1405 — The database "%.*ls" is already enabled for database mirroring.
- 1406 — Unable to force service safely. Remove database mirroring and recover database "%.*ls" to gain access.
- 1407 — The remote copy of database "%.*ls" is not related to the local copy of the database.
- 1408 — The remote copy of database "%.*ls" is not recovered far enough to enable database mirroring or to join it to the availability group. You need to appl…
- 1409 — Database "%.*ls" requires database logs to be restored either on the future mirror database before you can enable database mirroring or on a secondary…
- 1410 — The remote copy of database "%.*ls" is already enabled for database mirroring.
- 1411 — The remote copy of database "%.*ls" has not had enough log backups applied to roll forward all of its files to a common point in time.
- 1412 — The remote copy of database "%.*ls" has not been rolled forward to a point in time that is encompassed in the local copy of the database log.
- 1413 — Communications to the remote server instance '%.*ls' failed before database mirroring was fully started. The ALTER DATABASE command failed. Retry the …
- 1414 — The database is being closed before database mirroring is fully initialized. The ALTER DATABASE command failed.
- 1415 — The database mirroring operation for database "%.*ls" failed. The requested operation could not be performed.
- 1416 — Database "%.*ls" is not configured for database mirroring.
- 1417 — Database mirroring has been disabled by the administrator for database "%.*ls".
- 1418 — The server network address "%.*ls" can not be reached or does not exist. Check the network address name and that the ports for the local and remote en…
- 1419 — The remote copy of database "%.*ls" cannot be opened. Check the database name and ensure that it is in the restoring state, and then reissue the comma…
- 1420 — Database mirroring was unable to obtain the network hostname. Operating system error %ls encountered. Verify the network configuration.
- 1421 — Communications to the remote server instance '%.*ls' failed to complete before its timeout. The ALTER DATABASE command may have not completed. Retry t…
- 1422 — The mirror server instance is not caught up to the recent changes to database "%.*ls". Unable to fail over.
- 1423 — The property name is not supported.
- 1424 — The remote server instance has a more recent value for the property '%.*ls'. Property value not changed.
- 1425 — The property value is invalid for '%.*ls'. Property value not changed.
- 1426 — To issue ALTER DATABASE SET WITNESS, all three server instances must be interconnected, and the mirror database must be caught up. When these conditio…
- 1427 — The server instance '%.*ls' could not act as the witness. The ALTER DATABASE SET WITNESS command failed.
- 1428 — The request is refused because the responding server instance is not in a state to service the request.
- 1429 — The witness server instance name must be distinct from both of the server instances that manage the database. The ALTER DATABASE SET WITNESS command f…
- 1430 — Database '%.*ls' is in an unstable state for removing database mirroring, so recovery may fail. Verify the data after recovery.
- 1431 — Neither the partner nor the witness server instance for database "%.*ls" is available. Reissue the command when at least one of the instances becomes …
- 1432 — Database mirroring is attempting to repair physical page %S_PGID in database "%.*ls" by requesting a copy from the partner.
- 1433 — All three server instances did not remain interconnected for the duration of the ALTER DATABASE SET WITNESS command. There may be no witness associate…
- 1434 — Invalid or unexpected database mirroring %ls message of type %d was received from server %ls, database %.*ls.
- 1435 — %ls received unexpected database mirroring error response: status %u, severity %u, state %u, string %.*ls.
- 1436 — The Service Broker ID for the remote copy of database "%.*ls" does not match the ID on the principal server.
- 1437 — Could not post message '%ls' from server instance '%ls' because there is insufficient memory. Reduce non-essential memory load or increase system memo…
- 1438 — The server instance %ls rejected configure request; read its error log file for more information. The reason %u, and state %u, can be of use for diagn…
- 1439 — There is currently no witness associated with database "%.*ls".
- 1440 — Database mirroring is active with database '%.*ls' as the principal copy. This is an informational message only. No user action is required.
- 1441 — Database mirroring is active with database '%.*ls' as the mirror copy. This is an informational message only. No user action is required.
- 1442 — Database mirroring is inactive for database '%.*ls'. This is an informational message only. No user action is required.
- 1443 — Database mirroring has been terminated for database '%.*ls'. This is an informational message only. No user action is required.
- 1444 — Bypassing recovery for database '%ls' because it is marked as a mirror database, which cannot be recovered. This is an informational message only. No …
- 1445 — Bypassing recovery for database '%ls' because it is marked as an inaccessible database mirroring database. A problem exists with the mirroring session…
- 1446 — The "%.*ls" server instance is already acting as the witness.
- 1447 — ALTER DATABASE "%.*ls" command cannot be executed until both partner server instances are up, running, and connected. Start the partner and reissue th…
- 1448 — The remote copy of database "%.*ls" does not exist. Check the database name and reissue the command.
- 1449 — ALTER DATABASE command failed due to an invalid server connection string.
- 1450 — The ALTER DATABASE command failed because the worker thread cannot be created.
- 1451 — Database mirroring information was not found in the system table.
- 1452 — The partner server instance name must be distinct from the server instance that manages the database. The ALTER DATABASE SET PARTNER command failed.
- 1453 — '%.*ls', the remote mirroring partner for database '%.*ls', encountered error %d, status %d, severity %d. Database mirroring has been suspended. Resol…
- 1454 — Database mirroring will be suspended. Server instance '%.*ls' encountered error %d, state %d, severity %d when it was acting as a mirroring partner fo…
- 1455 — The database mirroring service cannot be forced for database "%.*ls" because the database is not in the correct state to become the principal database…
- 1456 — The ALTER DATABASE command could not be sent to the remote server instance '%.*ls'. The database mirroring configuration was not changed. Verify that …
- 1457 — Synchronization of the mirror database, '%.*ls', was interrupted, leaving the database in an inconsistent state. The ALTER DATABASE command failed. En…
- 1458 — The principal copy of the '%.*ls' database encountered error %d, status %d, severity %d while sending page %S_PGID to the mirror. Database mirroring h…
- 1459 — An error occurred while accessing the database mirroring metadata. Drop mirroring (ALTER DATABASE database_name SET PARTNER OFF) and reconfigure it.
- 1460 — The database "%.*ls" is already configured for database mirroring on the remote server. Drop database mirroring on the remote server to establish a ne…
- 1461 — Database mirroring successfully repaired physical page %S_PGID in database "%.*ls" by obtaining a copy from the partner.
- 1462 — Database mirroring is disabled due to a failed redo operation. Unable to resume.
- 1463 — Database mirroring is not available in the edition of this SQL Server instance. See books online for more details on feature support in different SQL …
- 1464 — Database "%.*ls" is not in a recovering state which is required for a mirror database or secondary database. The remote database must be restored usin…
- 1465 — Database "%.*ls" database is not in full recovery mode on each of the server instances. The full recovery model is required for a database to particip…
- 1466 — Database "%.*ls" is read-only on one of the server instances which is incompatible with participating in database mirroring or in an availability grou…
- 1467 — Database "%.*ls" database is in emergency or suspect mode on one of the partners which is incompatible with participating in database mirroring or in …
- 1468 — The operation cannot be performed on database "%.*ls" because it is involved in a database mirroring session or an availability group. Some operations…
- 1469 — Database "%.*ls" is an auto-close database on one of the partnerswhich is incompatible with participating in database mirroring or in an availability …
- 1470 — The alter database for this partner config values may only be initiated on the current principal server for database "%.*ls".
- 1471 — The database mirroring connection terminated. Out of memory sending message for database "%.*ls".
- 1472 — The database mirroring connection terminated. Communications error sending message for database "%.*ls".
- 1473 — This SQL Server edition does not allow changing the safety level. ALTER DATABASE command failed.
- 1474 — Database mirroring connection error %d '%.*ls' for '%.*ls'.
- 1475 — Database "%.*ls" might contain bulk logged changes that have not been backed up. Take a log backup on the principal database or primary database. Then…
- 1476 — Database mirroring timeout value %d exceeds the maximum value 32767.
- 1477 — The database mirroring safety level must be FULL to manually failover database "%.*ls". Set safety level to FULL and retry.
- 1478 — The mirror database, "%.*ls", has insufficient transaction log data to preserve the log backup chain of the principal database. This may happen if a l…
- 1479 — The mirroring connection to "%.*ls" has timed out for database "%.*ls" after %d seconds without a response. Check the service and network connections.
- 1480 — The %S_MSG database "%.*ls" is changing roles from "%ls" to "%ls" because the mirroring session or availability group failed over due to %S_MSG. This …
- 1481 — Database mirroring could not repair physical page %S_PGID in database "%.*ls". The mirroring partner could not be contacted or did not provide a copy …
- 1482 — Database mirroring failed to get snapshot synchrinization lock.
- 1483 — State information for database '%.*ls' - Hardened Lsn: '%S_LSN' Commit LSN: '%S_LSN' Commit Time: '%S_DATE'
- 1484 — Database Mirroring cannot be set for database '%.*ls' because the database has Accelerated Database Recovery enabled or there are still versions in th…
- 1485 — Database mirroring has been enabled on this instance of SQL Server.
- 1486 — Database Mirroring Transport is disabled in the endpoint configuration.
- 1487 — Database mirroring is starting %d parallel redo thread(s) with database '%.*ls' as the mirror copy. This is an informational message only. No user act…
- 1488 — Database "%.*ls" database is in single user mode which is incompatible with participating in database mirroring or in an availability group. Set datab…
- 1489 — Database Mirroring is disabled on this server due to error %d. Check the errorlog and configuration for more information.
- 1490 — The remote copy of database "%.*ls" has not been restored to a log backup that includes all filestream data files.
- 1491 — Enabling Database Mirroring is not allowed when REMOTE_DATA_ARCHIVE is already enabled on database '%.*ls'.
- 1492 — Enabling Database Mirroring is not allowed when Change Feed is enabled on database '%.*ls'.
- 1493 — Database Mirroring cannot be set for database '%.*ls' because the database has the LEDGER = ON option or contains ledger tables.
- 1494 — Enabling Database Mirroring is not allowed when Change Event Streaming is enabled on database '%.*ls'.
- 1499 — Database mirroring error: status %u, severity %u, state %u, string %.*ls.
- 1501 — Sort failure. Contact Technical Support.
- 1505 — The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name '%.*ls' and the index name '%.*ls'. The duplicate k…
- 1509 — Row comparison failed during sort because of an unknown data type on a key column. Metadata might be corrupt. Contact Technical Support.
- 1510 — Sort failed. Out of space or locks in database '%.*ls'.
- 1511 — Sort cannot be reconciled with transaction log.
- 1522 — Sort operation failed during an index build. The overwriting of the allocation page in database '%.*ls' was prevented by terminating the sort. Run DBC…
- 1523 — Sort failure. The incorrect extent could not be deallocated. Contact Technical Support.
- 1532 — New sort run starting on page %S_PGID found an extent not marked as shared. Retry the transaction. If the problem persists, contact Technical Support.
- 1533 — Cannot share extent %S_PGID. The correct extents could not be identified. Retry the transaction.
- 1534 — Extent %S_PGID not found in shared extent directory. Retry the transaction. If the problem persists, contact Technical Support.
- 1535 — Cannot share extent %S_PGID. Shared extent directory is full. Retry the transaction. If the problem persists, contact Technical Support.
- 1537 — Cannot suspend a sort that is not in row input phase.
- 1538 — Cannot insert a row into a sort when the sort is not in row input phase.
- 1540 — Cannot sort a row of size %d, which is greater than the allowable maximum of %d. Consider resubmitting the query using the ROBUST PLAN hint.
- 1541 — Sort failure. A defective CLR type comparison function is suspected.
- 1542 — BobMgr::GetBuf: Sort Big Output Buffer write not complete after %d seconds.
- 1543 — SQL Server encountered: '%ls' resulting from an attempt to read the following: sort run page %S_PGID, in file '%ls', in database with ID %d. Sort is r…
- 1701 — Creating or altering table '%.*ls' failed because the minimum row size would be %d, including %d bytes of internal overhead. This exceeds the maximum …
- 1702 — CREATE TABLE failed because column '%.*ls' in table '%.*ls' exceeds the maximum of %d columns.
- 1706 — The system table '%.*ls' can only be created or altered during an upgrade.
- 1707 — Cannot specify TEXTIMAGE_ON filegroup for a partitioned table.
- 1708 — Warning: The table "%.*ls" has been created, but its maximum row size exceeds the allowed maximum of %d bytes. INSERT or UPDATE to this table will fai…
- 1709 — Cannot use TEXTIMAGE_ON when a table has no text, ntext, image, varchar(max), nvarchar(max), non-FILESTREAM varbinary(max), xml or large CLR type colu…
- 1710 — Cannot use alias type with rule or default bound to it as a column type in table variable or return table definition in table valued function. Type '%…
- 1711 — Cannot define PRIMARY KEY constraint on column '%.*ls' in table '%.*ls'. The computed column has to be persisted and not nullable.
- 1712 — Online index operations can only be performed in Enterprise edition of SQL Server.
- 1713 — Cannot execute %ls on/using table '%.*ls' since the table is the target table or part of cascading actions of a currently executing trigger.
- 1714 — Alter table failed because unique column IDs have been exhausted for table '%.*ls'.
- 1715 — Foreign key '%.*ls' creation failed. Only NO ACTION referential update action is allowed for referencing computed column '%.*ls'.
- 1716 — FILESTREAM_ON cannot be specified when a table has no FILESTREAM columns. Remove the FILESTREAM_ON clause from the statement, or add a FILESTREAM colu…
- 1717 — FILESTREAM_ON cannot be specified together with a partition scheme in the ON clause.
- 1718 — Change tracking must be enabled on database '%.*ls' before it can be enabled on table '%.*ls'.
- 1719 — FILESTREAM data cannot be placed on an empty filegroup.
- 1720 — Cannot drop FILESTREAM filegroup or partition scheme since table '%.*ls' has FILESTREAM columns.
- 1721 — Altering table '%.*ls' failed because the row size using vardecimal storage format exceeds the maximum allowed table row size of %d bytes.
- 1722 — Cannot %S_MSG %S_MSG '%.*ls' since a partition scheme is not specified for FILESTREAM data.
- 1723 — Cannot %S_MSG %S_MSG '%.*ls' since a partition scheme was specified for FILESTREAM data but not for the table.
- 1724 — Filegroup '%.*ls' is not a FILESTREAM filegroup or partition scheme of FILESTREAM filegroups.
- 1725 — Cannot add FILESTREAM column to %S_MSG '%.*ls' because an INSTEAD OF trigger exists on the %S_MSG.
- 1726 — Cannot add FILESTREAM filegroup or partition scheme since table '%.*ls' has a FILESTREAM filegroup or partition scheme already.
- 1727 — Cannot create non-clustered index '%.*ls' on table '%.*ls' with the FILESTREAM_ON clause.
- 1728 — Cannot create index '%.*ls' on table '%.*ls' because the computed column '%.*ls' uses a FILESTREAM column.
- 1729 — Cannot create table '%.*ls' because the partitioning column '%.*ls' uses a FILESTREAM column.
- 1730 — Creating or altering compressed table '%.*ls' failed because the uncompressed row size would be %d, including %d bytes of internal overhead. This exce…
- 1731 — Cannot create the sparse column '%.*ls' in the table '%.*ls' because an option or data type specified is not valid. A sparse column must be nullable a…
- 1732 — Cannot create the sparse column set '%.*ls' in the table '%.*ls' because a table cannot have more than one sparse column set. Modify the statement so …
- 1733 — Cannot create the sparse column set '%.*ls' in the table '%.*ls' because a sparse column set must be a nullable xml column. Modify the column definiti…
- 1734 — Cannot create the sparse column set '%.*ls' in the table '%.*ls' because the table already contains one or more sparse columns. A sparse column set ca…
- 1735 — Duplicate range-partitioning function specified for the table being created. Remove one of the range-partitioning function specifications and resubmit…
- 1736 — The column '%.*ls' in the table '%.*ls' cannot be referenced in a CHECK constraint or computed column definition because the column is a sparse column…
- 1737 — Duplicate distribution clause specified for the table being created. Remove one of the distribution clauses and resubmit the request.
- 1738 — Cannot create table '%.*ls' with only a column set column and without any non-computed columns in the table.
- 1739 — ALTER TABLE failed because the table has %d variable length columns (including columns that have been dropped but require cleanup). This exceeds the m…
- 1740 — Cannot encrypt the sparse column '%.*ls' in the '%.*ls' table because the table contains a sparse column set.
- 1741 — Cannot create the sparse column set '%.*ls' in the '%.*ls' table because the table contains one or more encrypted sparse columns.
- 1750 — Could not create constraint or index. See previous errors.
- 1752 — Column '%.*ls' in table '%.*ls' is invalid for creating a default constraint.
- 1753 — Column '%.*ls.%.*ls' is not the same length or scale as referencing column '%.*ls.%.*ls' in foreign key '%.*ls'. Columns participating in a foreign ke…
- 1754 — Defaults cannot be created on columns with an IDENTITY attribute. Table '%.*ls', column '%.*ls'.
- 1755 — Defaults cannot be created on columns of data type timestamp. Table '%.*ls', column '%.*ls'.
- 1756 — Skipping FOREIGN KEY constraint '%.*ls' definition for temporary table. FOREIGN KEY constraints are not enforced on local or global temporary tables.
- 1757 — Column '%.*ls.%.*ls' is not of same collation as referencing column '%.*ls.%.*ls' in foreign key '%.*ls'.
- 1758 — Only a single constraint can be added or dropped online with no other operations in the same statement.
- 1759 — Computed column '%.*ls' in table '%.*ls' is not allowed to be used in another computed-column definition.
- 1760 — Constraints of type %ls cannot be created on columns of type %ls.