错误码目录 / Microsoft SQL Server
Microsoft SQL Server 错误码目录 · 第 2 / 18 页
本页收录 Microsoft SQL Server 的 17,993 条错误码知识条目,每条均可打开独立详情页,包含错误说明、编号信息、官方文档与公开资料。
- 1761 — Cannot create the foreign key "%.*ls" with the SET NULL referential action, because one or more referencing columns are not nullable.
- 1762 — Cannot create the foreign key "%.*ls" with the SET DEFAULT referential action, because one or more referencing not-nullable columns lack a default con…
- 1763 — Cross-database foreign key references are not supported. Foreign key '%.*ls'.
- 1764 — Computed Column '%.*ls' in table '%.*ls' is invalid for use in '%ls' because it is not persisted.
- 1765 — Foreign key '%.*ls' creation failed. Only NO ACTION and CASCADE referential delete actions are allowed for referencing computed column '%.*ls'.
- 1766 — Foreign key references to temporary tables are not supported. Foreign key '%.*ls'.
- 1767 — Foreign key '%.*ls' references invalid table '%.*ls'.
- 1768 — Foreign key '%.*ls' references object '%.*ls' which is not a user table.
- 1769 — Foreign key '%.*ls' references invalid column '%.*ls' in referencing table '%.*ls'.
- 1770 — Foreign key '%.*ls' references invalid column '%.*ls' in referenced table '%.*ls'.
- 1771 — Cannot create foreign key '%.*ls' because it references object '%.*ls' whose clustered index '%.*ls' is disabled.
- 1772 — Foreign key '%.*ls' is not valid. A system table cannot be used in a foreign key definition.
- 1773 — Foreign key '%.*ls' has implicit reference to object '%.*ls' which does not have a primary key defined on it.
- 1774 — The number of columns in the referencing column list for foreign key '%.*ls' does not match those of the primary key in the referenced table '%.*ls'.
- 1775 — Cannot create foreign key '%.*ls' because it references object '%.*ls' whose PRIMARY KEY index '%.*ls' is disabled.
- 1776 — There are no primary or candidate keys in the referenced table '%.*ls' that match the referencing column list in the foreign key '%.*ls'.
- 1778 — Column '%.*ls.%.*ls' is not the same data type as referencing column '%.*ls.%.*ls' in foreign key '%.*ls'.
- 1779 — Table '%.*ls' already has a primary key defined on it.
- 1781 — Column already has a DEFAULT bound to it.
- 1782 — Cannot drop index '%.*ls' since a partition scheme is not specified for base data.
- 1784 — Cannot create the foreign key '%.*ls' because the referenced column '%.*ls.%.*ls' is a non-persisted computed column.
- 1785 — Introducing FOREIGN KEY constraint '%.*ls' on table '%.*ls' may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO AC…
- 1786 — Either column '%.*ls.%.*ls' or referencing column '%.*ls.%.*ls' in foreign key '%.*ls' is a timestamp column. This data type cannot be used with casca…
- 1787 — Cannot define foreign key constraint '%.*ls' with cascaded DELETE or UPDATE on table '%.*ls' because the table has an INSTEAD OF DELETE or UPDATE TRIG…
- 1788 — Cascading foreign key '%.*ls' cannot be created where the referencing column '%.*ls.%.*ls' is an identity column.
- 1789 — Cannot use CHECKSUM(*) in a computed column, constraint, default definition, or INSERT statement.
- 1790 — The name of a user-defined table type cannot start with a number (#) sign.
- 1791 — A DEFAULT constraint cannot be created on the column '%.*ls' in the table '%.*ls' because the column is a sparse column or sparse column set. Sparse c…
- 1792 — Alter table '%.*ls' failed because the added fixed column might cause existing data to go beyond the maximum allowable table row size of %d bytes.
- 1793 — Cannot federate a temporary table.
- 1794 — Column '%.*ls' is invalid for federating the table '%.*ls'.
- 1795 — Nullable column '%.*ls' cannot be used to federate the table '%.*ls'.
- 1796 — Computed column '%.*ls' cannot be used to federate the table '%.*ls'.
- 1797 — Sparse column '%.*ls' cannot be used to federate the table '%.*ls'.
- 1798 — Federated tables cannot be created in a non-federated database.
- 1799 — Column '%.*ls' cannot be used to federate the table '%.*ls' because it does not match the federation key type.
- 1801 — Database '%.*ls' already exists. Choose a different database name.
- 1802 — CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
- 1803 — The CREATE DATABASE statement failed. The primary file must be at least %d MB to accommodate a copy of the model database.
- 1806 — CREATE DATABASE failed. The default collation of database '%.*ls' cannot be set to '%.*ls'.
- 1807 — Could not obtain exclusive lock on database '%.*ls'. Retry the operation later.
- 1809 — To achieve optimal performance, update all statistics on the '%.*ls' database by running sp_updatestats.
- 1810 — The model database must be updatable before a new database can be created.
- 1812 — CREATE DATABASE failed. COLLATE clause cannot be used with the FOR ATTACH option.
- 1813 — Could not open new database '%.*ls'. CREATE DATABASE is aborted.
- 1814 — Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then…
- 1815 — The %ls property cannot be used with database snapshot files.
- 1816 — Database snapshot on the system database %.*ls is not allowed.
- 1817 — Only the owner of database "%.*s" or the system administrator can create a database snapshot on it.
- 1818 — Primary log file '%ls' is missing and the database was not cleanly shut down so it cannot be rebuilt.
- 1819 — Could not create default log file because the name was too long.
- 1821 — Cannot create a database snapshot on another database snapshot.
- 1822 — The database must be online to have a database snapshot.
- 1823 — A database snapshot cannot be created because it failed to start.
- 1824 — Cannot attach a database that was being restored.
- 1825 — Filegroups and collations cannot be specified for database snapshots.
- 1826 — User-defined filegroups are not allowed on "%ls".
- 1827 — CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of %I64d MB per %S_MSG.
- 1828 — The logical file name "%.*ls" is already in use. Choose a different name.
- 1829 — The FOR ATTACH option requires that at least the primary file be specified.
- 1830 — The files '%ls' and '%ls' are both primary files. A database can only have one primary file.
- 1831 — File ONLINE/OFFLINE syntax cannot be used with CREATE DATABASE.
- 1832 — Cannot attach the file '%.*ls' as database '%.*ls'.%.*ls
- 1833 — File '%ls' cannot be reused until after the next BACKUP LOG operation. If the database is participating in an availability group, a dropped file can b…
- 1834 — The file '%ls' cannot be overwritten. It is being used by database '%.*ls'.
- 1835 — Unable to create/attach any new database because the number of existing databases has reached the maximum number allowed: %d.
- 1836 — Cannot create the default files because the name that was supplied is too long.
- 1837 — The file name "%ls" is too long to create an alternate stream name.
- 1838 — Offline database file(s) have been overwritten while being reverted to online state from a database snapshot. The reverted file might contain invalid …
- 1839 — Could not create default data files because the name '%ls' is a reserved device name.
- 1841 — CREATE DATABASE failed. CONTAINMENT clause cannot be used with the FOR ATTACH option.
- 1842 — The file size, max size cannot be greater than 2147483647 in units of a page size. The file growth cannot be greater than 2147483647 in units of both …
- 1843 — Reverting database '%ls' to the point in time of database snapshot '%ls' with split point LSN %.*ls (0x%ls). This is an informational message only. No…
- 1844 — %ls is not supported on %ls.
- 1845 — Cannot find SQL Volume Shadow Copy Service (VSS) Writer in writer metadata document provided by VSS while creating auto-recovered VSS snapshot for onl…
- 1846 — Cannot find SQL Volume Shadow Copy (VSS) Writer component for database '%ls' while creating auto-recovered VSS snapshot for online DBCC check.
- 1847 — The current version of the operating system doesn't support auto-recovered Volume Shadow Copy (VSS) snapshots.
- 1848 — Volume Shadow Copy Service (VSS) failed to create an auto-recovered snapshot of database '%ls' for online DBCC check.
- 1849 — CREATE DATABASE failed because FILESTREAM filegroups were declared and ALLOW_SNAPSHOT_ISOLATION or READ_COMMITTED_SNAPSHOT is set to ON in the model d…
- 1850 — Cannot attach database '%.*ls' because the file name '%.*ls' is valid on more than one brick.
- 1851 — File name '%.*ls' as relative path is too long after prefixed with default path '%ls'.
- 1852 — Error occurred when shrinking the physical file. Please check ERRORLOG for more detail.
- 1853 — The logical database file '%.*ls' cannot be found. Specify the full path for the file.
- 1854 — The original file name '%.*ls' for logical database file '%.*ls' is too long to be combined with the full path to the new primary data file location.
- 1855 — System table sysfiles1 is corrupted.
- 1856 — Cannot attach file '%.*ls' as database '%.*ls' because this database name is already attached with file '%.*ls'
- 1857 — Cannot attach file '%.*ls' as database '%.*ls' because this file is already in use for database '%.*ls'
- 1858 — Could not create snapshot database because user database is still in recovery.
- 1859 — Create database is not allowed in the model database context. Switch context to other database with USE statement and retry.
- 1860 — Task has been aborted, but %S_MSG of the %S_MSG '%.*ls' may continue in the background. Please check whether the %S_MSG has finished successfully.
- 1900 — Cannot create a clustered index with a predicate clause. Filtered clustered indexes are not supported.
- 1901 — Cannot create index or statistics '%.*ls' on view '%.*ls' because key column '%.*ls' is imprecise, computed and not persisted. Consider removing refer…
- 1902 — Cannot create more than one clustered index on %S_MSG '%.*ls'. Drop the existing clustered index '%.*ls' before creating another.
- 1904 — The %S_MSG '%.*ls' on table '%.*ls' has %d columns in the key list. The maximum limit for %S_MSG key column list is %d.
- 1907 — Cannot recreate index '%.*ls'. The new index definition does not match the constraint being enforced by the existing index.
- 1908 — Column '%.*ls' is partitioning column of the index '%.*ls'. Partition columns for a unique index must be a subset of the index key.
- 1909 — Cannot use duplicate column names in %S_MSG. Column name '%.*ls' listed more than once.
- 1910 — Could not create %S_MSG '%.*ls' because it exceeds the maximum of %d allowed per table or view.
- 1911 — Column name '%.*ls' does not exist in the target table or view.
- 1912 — Could not proceed with index DDL operation on %S_MSG '%.*ls' because it conflicts with another concurrent operation that is already in progress on the…
- 1913 — The operation failed because an index or statistics with name '%.*ls' already exists on %S_MSG '%.*ls'.
- 1914 — Index cannot be created on object '%.*ls' because the object is not a user table or view.
- 1915 — Cannot alter a non-unique index with ignore_dup_key index option. Index '%.*ls' is non-unique.
- 1916 — CREATE INDEX options %ls and %ls are mutually exclusive.
- 1917 — Cannot create, rebuild or drop an index on a local temporary table online. Perform the index operation offline.
- 1919 — Column '%.*ls' in table '%.*ls' is of a type that is invalid for use as a key column in an index.
- 1921 — Invalid %S_MSG '%.*ls' specified.
- 1922 — Filegroup '%.*ls' has no files assigned to it. Tables, indexes, and large object columns cannot be created on this filegroup. Use ALTER DATABASE to ad…
- 1924 — Filegroup '%.*ls' is read-only.
- 1925 — Cannot convert a clustered index to a nonclustered index by using the DROP_EXISTING option. To change the index type from clustered to nonclustered, d…
- 1926 — Cannot create a clustered index because nonclustered index ID %d is on a read-only filegroup.
- 1927 — There are already statistics on table '%.*ls' named '%.*ls'.
- 1929 — Statistics cannot be created on object '%.*ls' because the object is not a user table or view.
- 1930 — Cannot convert a nonclustered index to a clustered index because a foreign key constraint references the index. Remove the foreign key constraint and …
- 1931 — The SQL statement cannot be executed because filegroup '%.*ls' is offline. Use the sys.database_files or sys.master_files catalog view to determine th…
- 1932 — Cannot create a clustered index because nonclustered index ID %d is on an offline filegroup.
- 1934 — %ls failed because the following SET options have incorrect settings: '%.*ls'. Verify that SET options are correct for use with %S_MSG.
- 1935 — Cannot create index. Object '%.*ls' was created with the following SET options off: '%.*ls'.
- 1937 — Cannot create %S_MSG on view '%.*ls' because it references another view '%.*ls'. Consider expanding referenced view's definition by hand in indexed vi…
- 1938 — Index cannot be created on view '%.*ls' because the underlying object '%.*ls' has a different owner.
- 1939 — Cannot create %S_MSG on view '%.*ls' because the view is not schema bound.
- 1940 — Cannot create %S_MSG on view '%.*ls'. It does not have a unique clustered index.
- 1941 — Cannot create nonunique clustered index on view '%.*ls' because only unique clustered indexes are allowed. Consider creating unique clustered index in…
- 1942 — Cannot create %S_MSG on view '%.*ls'. It contains text, ntext, image, FILESTREAM or xml columns.
- 1943 — The index "%.*ls" on table "%.*ls" cannot be reorganized because page level locking is disabled.
- 1944 — Index '%.*ls' was not created because the index key size is at least %d bytes. The %S_MSG index key size cannot exceed %d bytes. If the index key incl…
- 1945 — Warning! The maximum key length for a %S_MSG index is %d bytes. The index '%.*ls' has maximum length of %d bytes. For some combination of large values…
- 1946 — Operation failed. The index entry of length %d bytes for the index '%.*ls' exceeds the maximum length of %d bytes for %S_MSG indexes.
- 1947 — Cannot create %S_MSG on view "%.*ls". The view contains a self join on "%.*ls".
- 1949 — Cannot create %S_MSG on view '%.*ls'. The function '%s' yields nondeterministic results. Use a deterministic system function, or modify the user-defin…
- 1950 — Index on view '%.*ls' cannot be created because the view contains an imprecise expression in a GROUP BY clause
- 1951 — Index on view '%.*ls' cannot be created because the view contains an imprecise expression in the WHERE clause.
- 1952 — Index on view '%.*ls' cannot be created because the view contains an imprecise expression in a join.
- 1953 — Index on view '%.*ls' cannot be created because some arguments are missing in a built-in function.
- 1956 — Cannot create %S_MSG on the '%.*ls' view because it uses the nondeterministic user-defined function '%.*ls'. Remove the reference to the function, or …
- 1957 — Cannot create %S_MSG on view '%.*ls' because view uses imprecise user-defined function '%.*ls'. Consider removing reference to function or altering it…
- 1959 — Cannot create an index on a view or computed column because the compatibility level of this database is less than 80. Use sp_dbcmptlevel to raise the …
- 1961 — Cannot create %S_MSG on view '%.*ls'. The collation cast expression with collation name '%.*ls' is non-deterministic because it is dependent on the op…
- 1962 — Cannot create %S_MSG on view '%.*ls' because column '%.*ls' that is referenced by the view in the WHERE or GROUP BY clause is imprecise. Consider elim…
- 1963 — Cannot create %S_MSG on view "%.*ls". The view contains a convert that is imprecise or non-deterministic.
- 1964 — Cannot create %S_MSG on view "%.*ls". The view contains an imprecise constant.
- 1965 — Cannot create %S_MSG on view "%.*ls". The view contains an imprecise arithmetic operator.
- 1966 — Cannot create %S_MSG on view '%.*ls'. The view contains an imprecise aggregate operator.
- 1967 — Cannot create a new clustered index on a view online.
- 1968 — Cannot convert a nonclustered index to a clustered index online using DROP_EXISTING option.
- 1969 — Default FILESTREAM filegroup is not available in database '%.*ls'.
- 1970 — Warning: Online index operation on table '%.*ls' will proceed but concurrent access to the table may be limited due to residual lock on the table from…
- 1971 — Cannot disable index '%.*ls' on table '%.*ls'. Permission denied to disable foreign key '%.*ls' on table '%.*ls' that uses this index.
- 1972 — Cannot disable clustered index '%.*ls' on table '%.*ls'. Permission denied to alter the referencing view '%.*ls' while disabling its clustered index.
- 1973 — Cannot perform the specified operation on disabled index '%.*ls' on %S_MSG '%.*ls'.
- 1974 — Cannot perform the specified operation on %S_MSG '%.*ls' because its clustered index '%.*ls' is disabled.
- 1975 — Index '%.*ls' row length exceeds the maximum permissible length of '%d' bytes.
- 1976 — Cannot create index or statistics '%.*ls' on view '%.*ls' because cannot verify key column '%.*ls' is precise and deterministic. Consider removing col…
- 1977 — Could not create %S_MSG '%.*ls' on table '%.*ls'. Only XML Index can be created on XML column '%.*ls'.
- 1978 — Column '%.*ls' in table '%.*ls' is of a type that is invalid for use as a key column in an index or statistics.
- 1979 — Cannot use index option ignore_dup_key to alter index '%.*ls' as it enforces a primary or unique constraint.
- 1980 — Index cannot be created on computed column '%.*ls' of table '%.*ls' because the underlying object '%.*ls' has a different owner.
- 1981 — Warning: The maximum length of the row exceeds the permissible limit of %d bytes. For some combination of large values, the insert/update operation wi…
- 1982 — Cannot create %S_MSG on view '%.*ls' because the view references non-deterministic or imprecise member function '%.*ls' on CLR type '%.*ls'. Consider …
- 1983 — Cannot create %S_MSG on view '%.*ls'. The function '%s' yields imprecise results. Use a precise system function, or modify the user-defined function t…
- 1984 — Index '%.*ls' cannot be created or rebuilt. The specified row length for this index using the vardecimal storage format exceeds the maximum allowed le…
- 1985 — Cannot create %S_MSG on view '%.*ls'. It contains one or more XML data type methods.
- 1986 — Cannot replace non-hypothetical index '%.*ls' with a hypothetical index using the DROP_EXISTING option.
- 1987 — Cannot %S_MSG %S_MSG '%.*ls' on %S_MSG '%.*ls' because its %S_MSG is disabled.
- 1988 — Cannot rebuild clustered index '%.*ls' online because it is disabled.
- 1989 — Cannot enable foreign key constraint '%.*ls' as index '%.*ls' on referenced key is disabled.
- 1990 — Cannot define an index on a view with ignore_dup_key index option. Remove ignore_dup_key option and verify that view definition does not allow duplica…
- 1991 — Cannot disable clustered index '%.*ls' on table '%.*ls'. Permission denied to disable foreign key '%.*ls' on table '%.*ls' that references this table.
- 1992 — Warning: Foreign key '%.*ls' on table '%.*ls' referencing table '%.*ls' was disabled as a result of disabling the index '%.*ls'.
- 1993 — Cannot partition an index on a table variable or return table definition in table valued function.
- 1994 — Cannot create or update statistics on view "%.*ls" because both FULLSCAN and NORECOMPUTE options are required.
- 1995 — Cannot rebuild hypothetical index '%.*ls' online.
- 1996 — Could not create index enforcing primary key constraint '%.*ls' using DROP_EXISTING option because table has an XML or spatial index. Drop the XML or …
- 1997 — Could not convert the XML or spatial index '%.*ls' to a relational index by using the DROP_EXISTING option. Drop the XML or spatial index and create a…
- 1998 — Warning: Clustered index '%.*ls' on view '%.*ls' referencing table '%.*ls' was disabled as a result of disabling the index '%.*ls'.
- 1999 — Column '%.*ls' in table '%.*ls' is of a type that is invalid for use as included column in an index.
- 2001 — Cannot use duplicate parameter names. Parameter name '%.*ls' listed more than once.
- 2002 — Cannot create a procedure for replication with group number greater than one.
- 2003 — Procedures with a group number cannot have parameters of XML, CLR or encrypted types. Parameter '%.*ls' of procedure '%.*ls' has type '%ls'.
- 2004 — Procedure '%.*ls' has already been created with group number %d. Create procedure with an unused group number.
- 2005 — The table '%.*ls' is unavailable and needs to be rebuilt. Rebuild the table offline.
- 2007 — The module '%.*ls' depends on the missing object '%.*ls'. The module will still be created; however, it cannot run successfully until the object exist…
- 2008 — The object '%.*ls' is not a procedure so you cannot create another procedure under that group name.
- 2009 — Procedure '%.*ls' was created despite delayed name resolution warnings (if any).
- 2010 — Cannot perform alter on '%.*ls' because it is an incompatible object type.
- 2011 — Index hints within a schema-bound object can be applied only to memory optimized tables.
- 2012 — Variables of CLR type cannot be declared within schema-bound object.
- 2013 — Warning: 'is_ms_shipped' property is turned off for %S_MSG '%.*ls' because you do not have permission to create or alter an object with this property.
- 2014 — Remote access is not allowed from within a schema-bound object.
- 2020 — The dependencies reported for entity "%.*ls" might not include references to all columns. This is either because the entity references an object that …
- 2021 — The referenced entity '%.*ls' was modified during DDL execution. Please retry the operation.
- 2022 — Parsing errors were encountered in the %S_MSG '%.*ls'. The dependencies referenced from this object could not be determined.
- 2023 — Metadata was not updated for the schema-bound object '%ls'.
- 2101 — Cannot %S_MSG a server level %S_MSG for user '%.*ls' since there is no login corresponding to the user.
- 2102 — Cannot %S_MSG %S_MSG '%.*ls' since there is no user for login '%.*ls' in database '%.*ls'.
- 2103 — Cannot %S_MSG trigger '%.*s' because its schema is different from the schema of the target table or view.
- 2104 — Cannot %S_MSG the %S_MSG '%.*ls', because you do not have permission.
- 2108 — Cannot %S_MSG %S_MSG on '%.*ls' as the target is not in the current database.
- 2110 — Cannot alter trigger '%.*ls' on '%.*ls' because this trigger does not belong to this object. Specify the correct trigger name or the correct target ob…
- 2111 — Cannot %S_MSG trigger '%.*ls' on %S_MSG '%.*ls' because an INSTEAD OF %s trigger already exists on this object.
- 2112 — Cannot create trigger '%.*ls' on view '%.*ls' because the view is defined with CHECK OPTION.
- 2113 — Cannot %S_MSG INSTEAD OF DELETE or INSTEAD OF UPDATE TRIGGER '%.*ls' on table '%.*ls'. This is because the table has a FOREIGN KEY with cascading DELE…
- 2114 — Column '%.*ls' cannot be used in an IF UPDATE clause because it is a computed column.
- 2115 — Server level event notifications are disabled as the database msdb does not exist.
- 2116 — Cannot CREATE EVENT NOTIFICATION to database '%.*ls' because it is not a valid broker database.
- 2117 — Cannot %S_MSG INSTEAD OF trigger '%.*ls' on %S_MSG '%.*ls' because the %S_MSG has a FILESTREAM column.
- 2201 — %sDerivation from "anySimpleType" by restriction is not permitted, and derivation by restriction from a type derived from "anySimpleType" by extension…
- 2202 — %sAn error has occurred while compiling the query. To obtain more detailed information about the error, the query must be run by a user with EXECUTE p…
- 2203 — %sOnly 'http://www.w3.org/2001/XMLSchema#decimal?', 'http://www.w3.org/2001/XMLSchema#boolean?' or 'node()*' expressions allowed as predicates, found …
- 2204 — %sOnly 'http://www.w3.org/2001/XMLSchema#boolean?' or 'node()*' expressions allowed in conditions and with logical operators, found '%ls'
- 2205 — %s"%ls" was expected.
- 2206 — %sNamespace prefix 'xml' can only be associated with the URI 'http://www.w3.org/XML/1998/namespace' and this URI cannot be used with other prefixes.
- 2207 — %sOnly non-document nodes can be inserted. Found "%ls".
- 2208 — %sThe URI that starts with '%ls' is too long. Maximum allowed length is %d characters.
- 2209 — %sSyntax error near '%ls'
- 2210 — %sHeterogeneous sequences are not allowed: found '%ls' and '%ls'
- 2211 — %sSingleton (or empty sequence) required, found operand of type '%ls'
- 2212 — %sInvalid source character '%c' (0x%02x) found in an identifier near '%ls'.
- 2213 — %sCannot atomize/apply data() on expression that contains type '%ls' within inferred type '%ls'
- 2214 — %sThe type '%ls' is not an atomic type
- 2215 — %sThe value of attribute '%ls' exceeds 4000 characters, the maximum permitted in XML schema documents
- 2216 — %sInvalid XPath value in "%ls".
- 2217 — %s'%ls' or '%ls' expected
- 2218 — %sThere is no attribute named '@%ls'
- 2219 — %sThere is no attribute named '@%ls' in the type '%ls'.
- 2220 — %sThere is no attribute named '@%ls:%ls'
- 2221 — %sThere is no attribute named '@%ls:%ls' in the type '%ls'.
- 2222 — %sInvalid source character 0x%02x found in an identifier near '%ls'.
- 2223 — %sSyntax error near '%ls', expected an identifier.
- 2225 — %sA string literal was expected
- 2226 — %sThe target of 'insert' must be a single node, found '%ls'
- 2227 — %sThe variable '%ls' was not found in the scope in which it was referenced.
- 2228 — %sThe variable '%ls:%ls' was not found in the scope in which it was referenced.
- 2229 — %sThe name "%ls" does not denote a namespace.
- 2230 — %sThe name "%ls" has already been defined.
- 2231 — %sThe name "%ls" does not denote a defined type.
- 2232 — %sThe name "%ls:%ls" does not denote a defined type.
- 2233 — %sThe operand of "%ls" has an invalid type.
- 2234 — %sThe operator "%ls" cannot be applied to "%ls" and "%ls" operands.
- 2235 — %sAn argument list was applied to a non-function term.
- 2236 — %sThere are not enough actual arguments in the call to function "%ls".
- 2237 — %sDerivation from anyType by extension is not supported in this release.
- 2238 — %sToo many arguments in call to function '%ls'
- 2240 — %sThe target of 'insert into' must be an element/document node, found '%ls'
- 2241 — %sVariable expected: '$name'
- 2242 — %sType specification expected.
- 2243 — %sRelative path expression used without any context
- 2247 — %sThe value is of type "%ls", which is not a subtype of the expected type "%ls".
- 2248 — %sSyntax error near '%ls', expected 'as', 'into', 'before' or 'after'.
- 2249 — %sThe target of 'insert before/after' must be an element/PI/comment/text node, found '%ls'
- 2256 — %sSyntax error near '%ls', expected a "node test".
- 2258 — %sThe position may not be specified when inserting an attribute node, found '%ls'
- 2260 — %sThere is no element named '%ls'
- 2261 — %sThere is no element named '%ls' in the type '%ls'.
- 2262 — %sThere is no element named '%ls:%ls'
- 2263 — %sThere is no element named "%ls:%ls" in the type "%ls".
- 2264 — %sOnly non-document nodes may be deleted, found '%ls'
- 2266 — %sExpected end tag '%ls:%ls'
- 2267 — %sExpected end tag '%ls'
- 2268 — %sEnd tag '/%ls:%ls' has no matching begin tag
- 2269 — %sEnd tag '/%ls' has no matching begin tag
- 2270 — %sDuplicate attribute '%ls:%ls'
- 2271 — %sDuplicate attribute '%ls'
- 2272 — %s'?>' expected
- 2273 — %sUnterminated CDATA section
- 2274 — %sUnterminated string constant (started on line %u)
- 2275 — %sUnterminated XML declaration
- 2276 — %sDerivation from 'QName' by restriction is not supported in this release
- 2277 — %sA tag name may not contain the character '%c'
- 2278 — %sA tag name may not start with the character '%c'
- 2279 — %sA name/token may not start with the character '%c'
- 2280 — %s<! was not followed by a valid construct
- 2281 — %sCannot construct DTDs in XQuery
- 2282 — %sInvalid entity reference
- 2283 — %sThe character '%c' may not be part of an entity reference
- 2284 — %sThe namespace prefix '%ls' has not been defined
- 2285 — %sInvalid numeric entity reference
- 2291 — %sNo root element was found.
- 2292 — %sWhen a type with simple content restricts a type with mixed content, it must have an embedded simple type definition. Location: '%ls'.
- 2293 — %sChoice cannot be empty unless minOccurs is 0. Location: '%ls'.
- 2294 — %s'xml' is not allowed as a processing instruction target.
- 2297 — %sElement <%ls> is not valid at location '%ls'.
- 2298 — %sAttribute '%ls' is not valid at location '%ls'.
- 2299 — %sRequired attribute "%ls" of XSD element "%ls" is missing.
- 2300 — %sRequired sub-element "%ls" of XSD element "%ls" is missing.
- 2301 — %sThe element "%ls" has already been defined.
- 2302 — %sThe name "%ls" has already been defined in this scope.
- 2305 — %sElement or attribute type specified more than once. Location: '%ls'.
- 2306 — %sThe qualified name "%ls" was found in a context where only NCName is allowed.
- 2307 — %sReference to an undefined name '%ls'
- 2308 — %sReference to an undefined name '%ls' within namespace '%ls'
- 2309 — %sThe value of "%ls" is not a valid number.
- 2310 — %sThe attribute "%ls" is declared more than once.
- 2311 — %sThe attribute "%ls" is declared more than once within "%ls".
- 2312 — %sThe value of attribute '%ls' does not conform to the type definition 'http://www.w3.org/2001/XMLSchema#%ls': '%ls'.
- 2313 — %sThe attribute "%ls" cannot have a value of "%ls".
- 2314 — %sThe attribute "%ls" cannot have a negative value.
- 2315 — %sThe attribute "%ls" should have a string value.
- 2316 — %sThe required 'base' attribute is missing. Location: '%ls'.
- 2317 — %sThe base type "%ls" defined on XSD element "%ls" is not a simple type.
- 2319 — %sThis type may not have a '%ls' facet. Location: '%ls'.
- 2320 — %sDuplicate facet '%ls' found at location '%ls'.
- 2321 — %sFacets cannot follow attribute declarations. Found facet '%ls' at location '%ls'.
- 2322 — %sThe element type is not a subclass of the substitution group's head
- 2323 — %sThe end tag '%ls' doesn't match opening tag '%ls' from line %u
- 2324 — %sThe end tag '%ls:%ls' doesn't match opening tag '%ls' from line %u
- 2325 — %sThe end tag '%ls' doesn't match opening tag '%ls:%ls' from line %u
- 2326 — %sThe end tag '%ls:%ls' doesn't match opening tag '%ls:%ls' from line %u
- 2327 — %sThe content or definition of <%ls> is missing.
- 2328 — %sSchema namespace '%ls' doesn't match <include> directive's '%ls'
- 2329 — %sThe string "%ls" is not a valid time duration value.
- 2331 — %sRedefinition has to have itself as base type. Location: '%ls'.
- 2332 — %s'%ls' may not be used with an 'empty' operand
- 2333 — %sInvalid source character 0x%02x
- 2334 — %sInvalid source character '%c' (0x%02x)
- 2335 — %sNewline in character/string constant
- 2336 — %s'%c' is not a valid octal digit (numbers starting with '0' are implicitly octal)
- 2337 — %sThe target of 'replace' must be at most one node, found '%ls'
- 2338 — %sThe second 'replace' operand must contain only nodes, found '%ls'
- 2339 — %sEither a memberType attribute or a simpleType child must be present. Location: '%ls'.
- 2340 — %sComment started on line %u has no end
- 2341 — %sExpected hex character code following '\x'
- 2342 — %sInvalid numeric constant.
- 2343 — %sUnterminated text section - missing `
- 2348 — %sA namespace URI should contain at least one non-whitespace character.
- 2349 — %sAttempt to redefine namespace prefix '%ls'
- 2350 — %sInvalid XML element content
- 2351 — %sExpected 'first' or 'last'
- 2353 — %s'to' or 'insert' or 'delete' expected
- 2354 — %sInvalid source character encoding
- 2355 — %s'else' expected
- 2356 — %sThe target of 'replace value of' must be a non-metadata attribute or an element with simple typed content, found '%ls'
- 2357 — %sA document node may only be replaced with another document node, found '%ls'
- 2358 — %sDerivation with both a 'base' attribute and an embedded type definition is not supported in this release. Location: '%ls'.
- 2359 — %sThe target of '%ls' may not be a constructed node
- 2360 — %sCannot have both a 'name' and 'ref' attribute. Location: '%ls'.
- 2361 — %sThe base type of an XSD extension or restriction type must be a simple type.
- 2362 — %sXSD schema too complex
- 2363 — %sXQuery too complex
- 2364 — %sCannot implicitly convert from '%ls' to '%ls'
- 2365 — %sCannot explicitly convert from '%ls' to '%ls'
- 2366 — %s"%ls" has a circular definition.
- 2367 — %sThe item type of an XSD list type must be a simple type. Location: '%ls'.
- 2368 — %sCannot have element content in a complex type with simple content. Location: '%ls'.
- 2369 — %sCannot have more than one group/sequence/choice/all within a restriction or extension. Location: '%ls'.
- 2370 — %sNo more tokens expected at the end of the XQuery expression. Found '%ls'.
- 2371 — %s'%ls' can only be used within a predicate or XPath selector
- 2372 — %sMetadata attribute '@%ls:%ls' may not be used with '%ls'
- 2373 — %s%ls is not supported with constructed XML
- 2374 — %sA node or set of nodes is required for %ls
- 2375 — %sAggregate function '%ls' expects a sequence argument
- 2376 — %sOperand of a single numeric type expected
- 2377 — %sResult of '%ls' expression is statically 'empty'
- 2378 — %sExpected XML schema document
- 2379 — %sThe name specified is not a valid XML name :'%ls'
- 2380 — %sMixed content is not allowed at location '%ls'.
- 2382 — %sInvalid combination of minOccurs and maxOccurs values, minOccurs has to be less than or equal to maxOccurs. Location: '%ls'.
- 2383 — %sInvalid value '%ls' for the %ls attribute. The value has to be between 0 and %ld.
- 2384 — %sInvalid element occurrence, element '%ls' was found multiple times in the context of element '%ls'
- 2385 — Invalid target namespace specified
- 2386 — %sThe value of '%ls' facet is outside of the allowed range
- 2387 — %sCannot have both 'type' and 'ref' attributes. Location: '%ls'.
- 2388 — %sInvalid element occurrence, element '%ls' has to appear first in the context of '%ls'
- 2389 — %s'%ls' requires a singleton (or empty sequence), found operand of type '%ls'
- 2390 — %sTop-level %s nodes are not supported
- 2391 — %sRedefining XSD schemas is not supported
- 2392 — %s'%ls::' is not a valid axis
- 2393 — %sEither an itemType attribute or a simpleType child must be present. Location: '%ls'.
- 2394 — %sThere is no function '%ls()'
- 2395 — %sThere is no function '%ls:%ls()'
- 2396 — %sAttribute may not appear outside of an element
- 2397 — %sIdentifiers may not contain more than %u characters
- 2398 — %sDuplicate id value found: '%ls'
- 2399 — %sAn attribute cannot have a value of type '%ls', a simple type was expected
- 2431 — Error [%d, %d, %d] occurred while attempting to deallocate workfile extent with extent ID [%d:%d].
- 2501 — Cannot find a table or object with the name "%.*ls". Check the system catalog.
- 2502 — Memory object list dump failed due to temporary inconsistency in the memory object structure. Please try again.
- 2503 — Successfully deleted the physical file '%ls'.
- 2504 — Could not delete the physical file '%ls'. The DeleteFile system function returned error %ls.
- 2505 — The device '%.*ls' does not exist. Use sys.backup_devices to show available devices.
- 2506 — Could not find a table or object name '%.*ls' in database '%.*ls'.
- 2507 — The CONCAT_NULL_YIELDS_NULL option must be set to ON to run DBCC CHECKCONSTRAINTS.
- 2508 — The %.*ls count for object "%.*ls", index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) is incorrect. Run DBCC UPDATEUSAGE.
- 2509 — DBCC CHECKCONSTRAINTS failed due to an internal query error. Please run DBCC CHECKDATABASE to ensure your data consistency.
- 2510 — DBCC %ls error: %ls.
- 2511 — Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Keys out of order on page %S_PGID, slots %d and %d.
- 2512 — Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Duplicate keys on page %S_PGID slot %d and page %S_PGID …
- 2513 — DBCC DBREINDEX cannot be used on memory optimized tables.
- 2514 — A DBCC PAGE error has occurred: %ls.
- 2515 — The page %S_PGID, object ID %d, index ID %d, partition ID %I64d, allocation unit ID %I64d (type %.*ls) has been modified, but is not marked as modifie…
- 2516 — Repair has invalidated the differential bitmap for database %.*ls. The differential backup chain is broken. You must perform a full database backup be…
- 2517 — Bulk-logging has been turned on for database %.*ls. To ensure that all data has been secured, run backup log operations again.
- 2518 — Object ID %ld (object "%.*ls"): Computed columns and CLR types cannot be checked for this object because the common language runtime (CLR) is disabled…
- 2519 — Computed columns and CLR types cannot be checked for object ID %ld (object "%.*ls") because the internal expression evaluator could not be initialized…
- 2520 — Could not find database '%.*ls'. The database either does not exist, or was dropped before a statement tried to use it. Verify if the database exists …
- 2521 — Could not find database ID %d. The database ID either does not exist, or the database was dropped before a statement tried to use it. Verify if the da…
- 2522 — Unable to process index %.*ls of table %.*ls because filegroup %.*ls is invalid.
- 2523 — Filegroup %.*ls is invalid.
- 2524 — Cannot process object ID %ld (object "%.*ls") because it is a Service Broker queue. Try the operation again with the object ID of the corresponding in…
- 2525 — Database file %.*ls is offline.
- 2526 — Incorrect DBCC statement. Check the documentation for the correct DBCC syntax and options.
- 2527 — Unable to process index %.*ls of table %.*ls because filegroup %.*ls is offline.
- 2528 — DBCC execution completed. If DBCC printed error messages, contact your system administrator.
- 2529 — Filegroup %.*ls is offline.
- 2530 — The index "%.*ls" on table "%.*ls" is disabled.
- 2531 — Table error: object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) B-tree level mismatch, page %S_PGID. Level %d does not ma…
- 2532 — One or more WITH options specified are not valid for this command.
- 2533 — Table error: page %S_PGID allocated to object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) was not seen. The page may be i…
- 2534 — Table error: page %S_PGID, whose header indicates that it is allocated to object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*…
- 2536 — DBCC results for '%.*ls'.
- 2537 — Table error: object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, row %d. The record check (%.*ls) failed. T…
- 2538 — File %d. The number of extents = %I64d, used pages = %I64d, and reserved pages = %I64d.
- 2539 — The total number of extents = %I64d, used pages = %I64d, and reserved pages = %I64d in this database.
- 2540 — The system cannot self repair this error.
- 2541 — DBCC UPDATEUSAGE: Usage counts updated for table '%.*ls' (index '%.*ls', partition %ld):
- 2542 — DATA pages %.*ls: changed from (%I64d) to (%I64d) pages.
- 2543 — USED pages %.*ls: changed from (%I64d) to (%I64d) pages.
- 2544 — RSVD pages %.*ls: changed from (%I64d) to (%I64d) pages.
- 2545 — ROWS count: changed from (%I64d) to (%I64d) rows.
- 2546 — Index '%.*ls' on table '%.*ls' is marked as disabled. Rebuild the index to bring it online.
- 2547 — Unable to process object ID %ld (object "%.*ls") because it is a synonym. If the object referenced by the synonym is a table or view, retry the operat…
- 2548 — DBCC: Compaction phase of index '%.*ls' is %d%% complete.
- 2549 — DBCC: Defrag phase of index '%.*ls' is %d%% complete.
- 2550 — The index "%.*ls" (partition %ld) on table "%.*ls" cannot be reorganized because it is being reorganized by another process.
- 2551 — The indexes on table "%.*ls" cannot be reorganized because there is already an online index build or rebuild in progress on the table.
- 2552 — The index "%.*ls" (partition %ld) on table "%.*ls" cannot be reorganized because page level locking is disabled.
- 2553 — Table '%.*ls' will not be available during reorganizing index '%.*ls'. This is because the index reorganization operation performs inside a user trans…
- 2554 — The index "%.*ls" (partition %ld) on table "%.*ls" cannot be reorganized because the filegroup is read-only.
- 2555 — Cannot move all contents of file "%.*ls" to other places to complete the emptyfile operation.
- 2556 — There is insufficient space in the filegroup to complete the emptyfile operation.
- 2557 — User '%.*ls' does not have permission to run DBCC %ls for object '%.*ls'.
- 2558 — %I64d incorrect counts were detected in database '%.*ls'.
- 2559 — The '%ls' and '%ls' options are not allowed on the same statement.
- 2560 — Parameter %d is incorrect for this DBCC statement.
- 2561 — Parameter %d is incorrect for this statement.
- 2562 — Checking FILESTREAM filegroup "%.*ls" (ID %d) is not supported in DBCC CHECKFILEGROUP. Specify a filegroup containing user objects with FILESTREAM dat…
- 2563 — DBCC SHRINKFILE for FILESTREAM containers requires EMPTYFILE option and does not allow any other options.
- 2564 — DBCC SHRINKFILE for %.*ls is aborted. MEMORY_OPTIMIZED_DATA containers are not supported.
- 2565 — DBCC DBREINDEX cannot be used on memory optimized tables.
- 2566 — DBCC DBREINDEX cannot be used on system tables.
- 2567 — DBCC INDEXDEFRAG cannot be used on system table indexes
- 2568 — Page %S_PGID is out of range for this database or is in a log file.
- 2569 — Parameter %d is incorrect for this DBCC statement: %ls.
- 2570 — Page %S_PGID, slot %d in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type "%.*ls"). Column "%.*ls" value is out of range for d…
- 2571 — User '%.*ls' does not have permission to run DBCC %.*ls.
- 2572 — DBCC cannot free DLL '%.*ls'. The DLL is in use.
- 2573 — Could not find table or object ID %.*ls. Check system catalog.
- 2574 — Table error: Page %S_PGID is empty in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). This is not permitted at level …
- 2575 — The Index Allocation Map (IAM) page %S_PGID is pointed to by the next pointer of IAM page %S_PGID in object ID %d, index ID %d, partition ID %I64d, al…
- 2576 — The Index Allocation Map (IAM) page %S_PGID is pointed to by the previous pointer of IAM page %S_PGID in object ID %d, index ID %d, partition ID %I64d…
- 2577 — Chain sequence numbers are out of order in the Index Allocation Map (IAM) chain for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d…
- 2578 — Json corruption found in column "%.*ls" in table '%ls' (ID %d). Data row (%d:%d:%d) identified by (%ls) is corrupted. Please update the column with a …
- 2579 — Table error: Extent %S_PGID in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) is beyond the range of this database.
- 2580 — Table '%.*ls' is either a system or temporary table. DBCC CLEANTABLE cannot be applied to a system or temporary table.
- 2581 — DBCC cannot free the DLL "%.*ls". The DLL is not loaded.
- 2583 — An incorrect number of parameters was given to the DBCC statement.
- 2585 — Cannot find partition number %ld for table "%.*ls".
- 2586 — Cannot find partition number %ld for index "%.*ls", table "%.*ls".
- 2587 — The invalid partition number %ld was specified.
- 2588 — Cannot find partition number %ld for index ID %d, object ID %d.
- 2589 — Repair could not fix all errors on the first attempt.
- 2590 — User "%.*ls" is modifying bytes %d to %d of page %S_PGID in database "%.*ls".
- 2591 — Cannot find a row in the system catalog with the index ID %d for table "%.*ls".
- 2592 — Repair: The %ls index successfully rebuilt for the object "%.*ls" in database "%.*ls".
- 2593 — There are %I64d rows in %I64d pages for object "%.*ls".
- 2594 — Cannot process rowset ID %I64d of object "%.*ls" (ID %d), index "%.*ls" (ID %d), because it resides on filegroup "%.*ls" (ID %d), which was not checke…
- 2595 — Cannot process table "%.*ls" because one of the partitions for its base index exists on the filegroup "%.*ls", which was not checked.
- 2596 — The repair statement was not processed. The database cannot be in read-only mode.
- 2597 — Ignoring trace flag %d. It is either an invalid trace flag or a trace flag that can only be specified during server startup.
- 2598 — Check cannot proceed on any objects belonging to database "%.*ls" because it is currently in recovery.
- 2599 — Cannot switch to in row text in table "%.*ls".
- 2601 — Cannot insert duplicate key row in object '%.*ls' with unique index '%.*ls'. The duplicate key value is %ls.
- 2627 — Violation of %ls constraint '%.*ls'. Cannot insert duplicate key in object '%.*ls'. The duplicate key value is %ls.
- 2628 — String or binary data would be truncated in table '%.*ls', column '%.*ls'. Truncated value: '%.*ls'.
- 2629 — String or binary data would be truncated in object ID '%ld'. Truncated value: '%.*ls'.
- 2700 — There are too many statements in the batch; the maximum number is %d
- 2701 — Database name '%.*ls' ignored, referencing object in tempdb.
- 2702 — Database '%.*ls' does not exist.
- 2703 — Cannot use duplicate column names in the partition columns list. Column name '%.*ls' appears more than once.
- 2704 — Invalid partition scheme '%.*ls' specified.
- 2705 — Column names in each table must be unique. Column name '%.*ls' in table '%.*ls' is specified more than once.
- 2706 — Table '%.*ls' does not exist.
- 2707 — Column '%.*ls' in %S_MSG '%.*ls' cannot be used in an index or statistics or as a partition key because it depends on a non-schemabound object.
- 2709 — Column '%.*ls' in %S_MSG '%.*ls' cannot be used in an index or statistics or as a partition key because it does user or system data access.
- 2710 — You are not the owner specified for the object '%.*ls' in this statement (CREATE, ALTER, TRUNCATE, UPDATE STATISTICS or BULK INSERT).
- 2711 — The definition of object "%.*ls" in the resource database contains the non-ASCII character "%.*ls".
- 2712 — Database '%.*ls' can not be configured as a distribution database because it has change tracking enabled.
- 2714 — There is already an object named '%.*ls' in the database.
- 2715 — Column, parameter, or variable #%d: Cannot find data type %.*ls.
- 2716 — Column, parameter, or variable #%d: Cannot specify a column width on data type %.*ls.
- 2717 — The size (%d) given to the %S_MSG '%.*ls' exceeds the maximum allowed (%d).
- 2719 — Upgrade of database "%.*ls" failed because it contains a user named "sys" which is a reserved user or schema name in this version of SQL Server.
- 2720 — Cannot schema bind %S_MSG '%.*ls' because it references system object '%.*ls'.
- 2722 — Xml data type methods are not allowed in expressions in this context.
- 2724 — Parameter or variable '%.*ls' has an invalid data type.
- 2725 — An online operation cannot be performed for %S_MSG '%.*ls' because the index contains column '%.*ls' of data type text, ntext, image or FILESTREAM. Fo…
- 2726 — Partition function '%.*ls' uses %d columns which does not match with the number of partition columns used to partition the table or index.
- 2727 — Cannot find index '%.*ls'.
- 2728 — Cannot partition on more than %d columns.
- 2729 — Column '%.*ls' in %S_MSG '%.*ls' cannot be used in an index or statistics or as a partition key because it is non-deterministic.
- 2730 — Cannot create procedure '%.*ls' with a group number of %d because a procedure with the same name and a group number of 1 does not currently exist in t…
- 2731 — Column '%.*ls' has invalid width: %d.
- 2732 — Error number %ld is invalid. The number must be from %ld through %ld and it cannot be 50000.
- 2733 — The %ls data type is invalid for return values.
- 2735 — Cannot create primary xml, selective xml or spatial index '%.*ls' on '%.*ls' because PRIMARY KEY constraint contains column(s) of type timestamp.
- 2738 — A table can only have one timestamp column. Because table '%.*ls' already has one, the column '%.*ls' cannot be added.
- 2739 — The text, ntext, and image data types are invalid for local variables.
- 2740 — SET LANGUAGE failed because '%.*ls' is not an official language name or a language alias on this SQL Server.
- 2741 — SET DATEFORMAT date order '%.*ls' is invalid.
- 2742 — SET DATEFIRST %d is out of range.
- 2743 — %ls option requires %S_MSG parameter.
- 2744 — Multiple identity columns specified for table '%.*ls'. Only one identity column per table is allowed.
- 2745 — Process ID %d has raised user error %d, severity %d. SQL Server is terminating this process.
- 2747 — Too many substitution parameters for RAISERROR. Cannot exceed %d substitution parameters.
- 2748 — Cannot specify %ls data type (parameter %d) as a substitution parameter.
- 2749 — Identity column '%.*ls' must be of data type int, bigint, smallint, tinyint, or decimal or numeric with a scale of 0, unencrypted, and constrained to …
- 2750 — Column or parameter #%d: Specified column precision %d is greater than the maximum precision of %d.
- 2751 — Column or parameter #%d: Specified column scale %d is greater than the specified precision of %d.
- 2752 — Identity column '%.*ls' contains invalid SEED.
- 2753 — Identity column '%.*ls' contains invalid INCREMENT.
- 2754 — Error severity levels greater than %d can only be specified by members of the sysadmin role, using the WITH LOG option.
- 2755 — SET DEADLOCK_PRIORITY option is invalid. Valid options are {HIGH | NORMAL | LOW | [%d ... %d] of type integer}.
- 2756 — Invalid value %d for state. State value must not be less than %d.
- 2759 — CREATE SCHEMA failed due to previous errors.
- 2760 — The specified schema name "%.*ls" either does not exist or you do not have permission to use it.
- 2761 — The ROWGUIDCOL property can only be specified on the uniqueidentifier data type.
- 2762 — sp_setapprole was not invoked correctly. Refer to the documentation for more information.
- 2763 — Could not find application role '%.*ls'.
- 2764 — Incorrect password supplied for application role '%.*ls'.
- 2766 — The definition for user-defined data type '%.*ls' has changed.
- 2767 — Could not locate statistics '%.*ls' in the system catalogs.
- 2770 — The SELECT INTO statement cannot have same source and destination tables.
- 2772 — Cannot access temporary tables from within a function.
- 2773 — The collation ID is corrupted because the sort order ID %d is not valid.
- 2774 — Collation ID %d is invalid.
- 2775 — The code page %d is not supported by the server.
- 2778 — Only System Administrator can specify %s option for %s command.
- 2779 — The %S_MSG '%.*ls' is an auto-drop system object. It cannot be used in queries or DDL.
- 2780 — View '%.*ls' is not schemabound.
- 2782 — Cannot create table "%.*ls": A table must have a clustered primary key in order to have XML data type columns.
- 2785 — User-defined functions, user-defined aggregates, CLR types, and methods on CLR types are not allowed in expressions in this context.
- 2786 — The data type of substitution parameter %d does not match the expected type of the format specification.
- 2787 — Invalid format specification: '%.*ls'.
- 2788 — Synonyms are invalid in a schemabound object or a constraint expression.
- 2789 — Must specify a two-part name for %S_MSG '%.*ls' in a schemabound object or a constraint expression.
- 2790 — Cannot use a column of type TEXT, NTEXT, or IMAGE in a constraint expression.
- 2791 — Could not resolve expression for Schema-bound object or constraint.
- 2792 — Cannot specify a sql CLR type in a Schema-bound object or a constraint expression.
- 2793 — Specified owner name '%.*ls' either does not exist or you do not have permission to act on its behalf.
- 2794 — Message text expects more than the maximum number of arguments (%d).
- 2795 — Could not %S_MSG %S_MSG because the new %S_MSG '%.*ls' does not match the FILESTREAM %S_MSG '%.*ls' of the table.
- 2796 — Cannot specify database name with $partition in a Schema-bound object, computed column or constraint expression.
- 2797 — The default schema does not exist.
- 2798 — Cannot create index or statistics '%.*ls' on table '%.*ls' because SQL Server cannot verify that key column '%.*ls' is precise and deterministic. Cons…
- 2799 — Cannot create index or statistics '%.*ls' on table '%.*ls' because the computed column '%.*ls' is imprecise and not persisted. Consider removing colum…
- 2801 — The definition of object '%.*ls' has changed since it was compiled.
- 2802 — SQL Server has encountered %d occurrence(s) of cachestore flush for the '%s' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREE…
- 2803 — SQL Server has encountered %d occurrence(s) of cachestore flush for the '%s' cachestore (part of plan cache) due to some database maintenance or recon…
- 2809 — The request for %S_MSG '%.*ls' failed because '%.*ls' is a %S_MSG object.
- 2812 — Could not find stored procedure '%.*ls'.
- 2813 — "%.*ls" is not supported on this edition of SQL Server.
- 2814 — A possible infinite recompile was detected for SQLHANDLE %hs, PlanHandle %hs, starting offset %d, ending offset %d. The last recompile reason was %d.
- 2815 — A possible infinite recompile was detected for the natively compiled module with ID '%d' in database with ID '%d'.
- 2816 — The metadata for object with id %d has changed. Retry the statement.
- 2817 — '%.*ls' is not supported on the '%.*ls' platform.
- 2818 — The stored procedure '%.*ls' cannot be run since this server has not been enabled for external governance.
- 2819 — Plan Cache Hydration application login failed because feature switch PlanCacheHydrationReplay is not enabled on this server
- 2820 — The feature '%.*ls' is not enabled on this SQL Server instance.
- 2821 — Failed to reload configuration for '%.*ls'. %.*ls
- 2950 — The operation encountered an integer overflow exception.
- 2951 — The operation encountered a bad format exception.
- 2952 — The operation encountered a bad array length exception.
- 3001 — obsolete
- 3002 — Cannot BACKUP or RESTORE a database snapshot.
- 3003 — This BACKUP WITH DIFFERENTIAL will be based on more than one file backup. All those file backups must be restored before attempting to restore this di…
- 3004 — The primary filegroup cannot be backed up as a file backup because the database is using the SIMPLE recovery model. Consider taking a partial backup b…
- 3005 — The differential partial backup is including a read-only filegroup, '%ls'. This filegroup was read-write when the base partial backup was created, but…
- 3006 — The differential backup is not allowed because it would be based on more than one base backup. Multi-based differential backups are not allowed in the…
- 3007 — The backup of the file or filegroup "%ls" is not permitted because it is not online. Container state: "%ls" (%d). Restore status: %d. BACKUP can be pe…
- 3008 — The specified device type is not supported for backup mirroring.
- 3009 — Could not insert a backup or restore history/detail record in the msdb database. This may indicate a problem with the msdb database. The backup/restor…
- 3010 — Invalid backup mirror specification. All mirrors must have the same number of members.
- 3011 — All backup devices must be of the same general class (for example, DISK and TAPE).
- 3012 — VDI ran out of buffer when SQL Server attempted to send differential information to SQL Writer.
- 3013 — %hs is terminating abnormally.
- 3014 — %hs successfully processed %I64d pages in %d.%03d seconds (%d.%03d MB/sec).
- 3015 — %hs is not yet implemented.
- 3016 — Backup of file '%ls' is not permitted because it contains pages subject to an online restore sequence. Complete the restore sequence before taking the…
- 3017 — The restart-checkpoint file '%ls' could not be opened. Operating system error '%ls'. Correct the problem, or reissue the command without RESTART.
- 3018 — The restart-checkpoint file '%ls' was not found. The RESTORE command will continue from the beginning as if RESTART had not been specified.
- 3019 — The restart-checkpoint file '%ls' is from a previous interrupted RESTORE operation and is inconsistent with the current RESTORE command. The restart c…
- 3021 — Cannot perform a backup or restore operation within a transaction.
- 3022 — This backup is a file backup of read-write data from a database that uses the simple recovery model. This is only appropriate if you plan to set the f…
- 3023 — Backup, file manipulation operations (such as ALTER DATABASE ADD FILE) and encryption changes on a database must be serialized. Reissue the statement …
- 3024 — You can only perform a full backup of the master database. Use BACKUP DATABASE to back up the entire master database.
- 3025 — Missing database name. Reissue the statement specifying a valid database name.
- 3027 — The filegroup "%.*ls" is not part of database "%.*ls".
- 3028 — The restart-checkpoint file '%ls' was corrupted and is being ignored. The RESTORE command will continue from the beginning as if RESTART had not been …
- 3030 — Value of '%ls' must be less than or equal to value of '%ls'. Change the values and reissue the BACKUP statement.
- 3031 — Option '%ls' conflicts with option(s) '%ls'. Remove the conflicting option and reissue the statement.
- 3032 — One or more of the options (%ls) are not supported for this statement. Review the documentation for supported options.
- 3033 — BACKUP DATABASE cannot be used on a database opened in emergency mode.
- 3034 — No files were selected to be processed. You may have selected one or more filegroups that have no members.
- 3035 — Cannot perform a differential backup for database "%ls", because a current database backup does not exist. Perform a full database backup by reissuing…
- 3036 — The database "%ls" is in warm-standby state (set by executing RESTORE WITH STANDBY) and cannot be backed up until the entire restore sequence is compl…
- 3038 — The file name "%ls" is invalid as a backup device name. Reissue the BACKUP statement with a valid file name.
- 3039 — Cannot perform a differential backup for file '%ls' because a current file backup does not exist. Reissue BACKUP DATABASE omitting the WITH DIFFERENTI…
- 3040 — An error occurred while informing replication of the backup. The backup will continue, but the replication environment should be inspected.
- 3041 — BACKUP failed to complete the command %.*ls. Check the backup application log for detailed messages.
- 3042 — BACKUP WITH CONTINUE_AFTER_ERROR successfully generated a backup of the damaged database. Refer to the SQL Server error log for information about the …
- 3043 — BACKUP '%ls' detected an error on page (%d:%d) in file '%ls'.
- 3044 — Invalid zero-length device name. Reissue the BACKUP statement with a valid device name.
- 3045 — BACKUP or RESTORE requires the NTFS file system for FILESTREAM and full-text support. The path "%.*ls" is not usable.
- 3046 — Inconsistent metadata has been encountered. The only possible backup operation is a tail-log backup using the WITH CONTINUE_AFTER_ERROR or NO_TRUNCATE…
- 3047 — The BackupDirectory registry key is not configured correctly. This key should specify the root path where disk backup files are stored when full path …
- 3048 — BACKUP LOG WITH TRUNCATE_ONLY cannot operate on database '%ls' because it is configured for database mirroring.
- 3049 — BACKUP detected corruption in the database log. Check the errorlog for more information.
- 3050 — SQL Server could not send the differential information for database file '%ls' of database '%ls\%ls' to the backup application because the differentia…
- 3051 — BACKUP LOG was unable to maintain mirroring consistency for database '%ls'. Database mirroring has been suspended.
- 3052 — BACKUP LOG was unable to log updates for for database '%ls'. Subsequent log backups will be required to advance the backup point from %S_LSN to %S_LSN…
- 3053 — BACKUP '%ls' detected an error on a page in file '%ls'.
- 3054 — Differential file backups can include only read-only data for databases using the simple recovery model. Consider taking a partial backup by specifyin…
- 3055 — Backup destination "%.*ls" supports a FILESTREAM filegroup. This filegroup cannot be used as a backup destination. Rerun the BACKUP statement with a v…
- 3056 — The backup operation has detected an unexpected file in a FILESTREAM container. The backup operation will continue and include file '%ls'.
- 3057 — Invalid device name. The length of the device name provided exceeds supported limit (maximum length is:%d). Reissue the BACKUP statement with a valid …
- 3058 — File or device name exceeds the supported limit (maximum length is:%d) and will be truncated: %.*ls.
- 3059 — This BACKUP or RESTORE command is not supported on a database mirror or secondary replica.
- 3060 — The restart-checkpoint file '%ls' was corrupted. The restored database can not be recovered. Restart the RESTORE sequence.
- 3061 — The restart-checkpoint file '%ls' could not be opened. Operating system error '%ls'. Make the file available and retry the operation or, restart the R…
- 3062 — Cannot backup from a HADRON secondary because it is not in Synchronizing or Synchronized state.
- 3063 — Write to backup block blob device %ls failed. Device has reached its limit of allowed blocks.
- 3064 — Write to backup block blob detected out of order write at offset %ld, last block offset was at %ld.
- 3065 — Attempt to commit the block list for a block blob failed. Blob Name is "%.*ls". Storage Errorcode %ld.
- 3066 — Could not find the database file referenced by the file snapshot %.*ls. Please make sure that the URL points to a valid snapshot on a database file.
- 3067 — Failed while trying to delete file snapshot %.*ls. Error code %ld.
- 3068 — Invalid file snapshot URL. Please make sure that the URL is correctly formed.
- 3069 — Striping a backup set across multiple devices is not permitted for file snapshot backups.
- 3070 — Specifying the WITH options FORMAT and FILE_SNAPSHOT is not permitted.
- 3071 — The database %.*ls is configured for file snapshot point in time restore, log backups are not permitted.
- 3072 — Backup encryption is incompatible with file snapshot backup if TDE is not enabled on the database.
- 3073 — The option WITH FILE_SNAPSHOT is only permitted if all database files are in Azure Storage.
- 3074 — Failed while getting attributes for the file snapshot %.*ls. Error code %ld.
- 3075 — Device name '%.*ls' is not a valid MOVE target when restoring from a File Snapshot Backup.
- 3076 — File Snapshot Backup is only permitted with a single backup device and no additonal mirrored devices.
- 3077 — File snapshot %.*ls not found.
- 3078 — The file name "%ls" is invalid as a backup device name for the specified device type. Reissue the BACKUP statement with a valid file name and device t…
- 3079 — Could not find the blob file %.*ls. Please make sure that the file name points to a valid blob file.
- 3080 — Invalid Backup Path. The length of the default backup path provided exceeds supported limit (maximum length is: %d). Correct the default backup path.
- 3081 — %.*ls '%.*ls' was previously suspended for snapshot backup.
- 3082 — %.*ls '%.*ls' is not suspended for snapshot backup.
- 3083 — Database '%.*ls' acquired suspend locks in session %d.
- 3084 — Database '%.*ls' released suspend locks in session %d.
- 3085 — Database '%.*ls' did not acquire the necessary suspend locks to freeze the database.
- 3086 — %.*ls '%.*ls' successfully suspended for snapshot backup in session %d.
- 3087 — %.*ls '%.*ls' originally suspended for snapshot backup in session %d successfully resumed in session %d.
- 3088 — %.*ls '%.*ls' with dbid %d failed to resume in session %d.
- 3089 — %.*ls '%.*ls' cancelled current resume operation as another resume operation is already in progress.
- 3090 — %.*ls '%.*ls' snapshot backup in progress.
- 3091 — Database '%.*ls' is not allowed to be suspended for snapshot backup.
- 3092 — Database '%.*ls' is specified multiple times in the group snapshot backup statement.
- 3093 — Database count changed while performing snapshot backup. (Expected: %d, Actual: %d).
- 3094 — Server '%.*ls' has no user databases to suspend for snapshot backup.
- 3095 — The backup cannot be performed because 'ENCRYPTION' was requested after the media was formatted with an incompatible structure. To append to this medi…
- 3096 — The Certificate specified for backup encryption has expired.
- 3097 — The Backup cannot be performed because the existing media set is formatted with an incompatible version.
- 3098 — The backup cannot be performed because '%ls' was requested after the media was formatted with an incompatible structure. To append to this media set, …
- 3099 — Backup Encryption options were specified, Backup Encryption support has not been enabled on this version.
- 3101 — Exclusive access could not be obtained because the database is in use.
- 3102 — %ls cannot process database '%ls' because it is in use by this session. It is recommended that the master database be used when performing this operat…
- 3103 — A partial restore sequence cannot be initiated by this command. To initiate a partial restore sequence, use the WITH PARTIAL clause of the RESTORE sta…
- 3104 — RESTORE cannot operate on database '%ls' because it is configured for database mirroring or has joined an availability group. If you intend to restore…
- 3105 — RESTORE cannot restore any more pages into file '%ls' because the maximum number of pages (%d) are already being restored. Either complete the restore…
- 3106 — The filegroup "%ls" is ambiguous. The identity in the backup set does not match the filegroup that is currently defined in the online database. To for…
- 3107 — The file "%ls" is ambiguous. The identity in the backup set does not match the file that is currently defined in the online database. To force the use…
- 3108 — To restore the master database, the server must be running in single-user mode. For information on starting in single-user mode, see "How to: Start an…
- 3109 — Master can only be restored and fully recovered in a single step using a full database backup. Options such as NORECOVERY, STANDBY, and STOPAT are not…
- 3110 — User does not have permission to RESTORE database '%.*ls'.
- 3111 — Page %S_PGID is a control page which cannot be restored in isolation. To repair this page, the entire file must be restored.
- 3112 — Cannot restore any database other than master when the server is in single user mode.
- 3113 — Invalid data was detected.
- 3115 — The database is using the simple recovery model. It is not possible to restore a subset of the read-write data.
- 3116 — The supplied backup is not on the same recovery path as the database, and is ineligible for use for an online file restore.
- 3117 — The log or differential backup cannot be restored because no files are ready to rollforward.
- 3118 — The database "%ls" does not exist. RESTORE can only create a database when restoring either a full backup or a file backup of the primary file.
- 3119 — Problems were identified while planning for the RESTORE statement. Previous messages provide details.
- 3120 — This backup set will not be restored because all data has already been restored to a point beyond the time covered by this backup set.
- 3121 — The file "%ls" is on a recovery path that is inconsistent with application of this backup set. RESTORE cannot continue.
- 3122 — File initialization failed. RESTORE cannot continue.
- 3123 — Invalid database name '%.*ls' specified for backup or restore operation.
- 3125 — The database is using the simple recovery model. The data in the backup it is not consistent with the current state of the database. Restoring more da…
- 3126 — The file "%ls" was not relocated using a relative path during the RESTORE step. A relative location is required when restoring a database from a stand…
- 3127 — The file '%.*ls' of restored database '%ls' is being left in the defunct state because the database is using the simple recovery model and the file is…
- 3128 — File '%ls' has an unsupported page size (%d).
- 3129 — The contents of the file "%ls" are not consistent with a transition into the restore sequence. A restore from a backup set may be required.
- 3130 — The filegroup "%ls" is selected. At the time of backup it was known by the name "%ls"'. RESTORE will continue operating upon the renamed filegroup.
- 3131 — The file "%ls" is selected. At the time of backup it was known by the name "%ls". RESTORE will continue operating upon the renamed file.
- 3132 — The media set has %d media families but only %d are provided. All members must be provided.
- 3133 — The volume on device "%ls" is sequence number %d of media family %d, but sequence number %d of media family %d is expected. Check that the device spec…
- 3134 — The differential base attribute for file '%ls' of database '%ls' has been reset because the file has been restored from a backup taken on a conflictin…
- 3135 — The backup set in file '%ls' was created by %hs and cannot be used for this restore operation.
- 3136 — This differential backup cannot be restored because the database has not been restored to the correct earlier state.
- 3137 — Database cannot be reverted. Either the primary or the snapshot names are improperly specified, all other snapshots have not been dropped, or there ar…
- 3138 — The database cannot be reverted because FILESTREAM BLOBs are present.
- 3139 — Restore to snapshot is not allowed with the master database.
- 3140 — Could not adjust the space allocation for file '%ls'.
- 3141 — The database to be restored was named '%ls'. Reissue the statement using the WITH REPLACE option to overwrite the '%ls' database.
- 3142 — File "%ls" cannot be restored over the existing "%ls". Reissue the RESTORE statement using WITH REPLACE to overwrite pre-existing files, or WITH MOVE …
- 3143 — The data set on device '%ls' is not a SQL Server backup set.
- 3144 — File '%.*ls' was not backed up in file %d on device '%ls'. The file cannot be restored from this backup set.
- 3145 — The STOPAT option is not supported for databases that use the SIMPLE recovery model.
- 3147 — Backup and restore operations are not allowed on database tempdb.
- 3148 — This RESTORE statement is invalid in the current context. The 'Recover Data Only' option is only defined for secondary filegroups when the database is…
- 3149 — The file or filegroup "%ls" is not in a valid state for the "Recover Data Only" option to be used. Only secondary files in the OFFLINE or RECOVERY_PEN…
- 3150 — The master database has been successfully restored. Shutting down SQL Server.
- 3151 — Failed to restore master database. Shutting down SQL Server. Check the error logs, and rebuild the master database. For more information about how to …
- 3153 — The database is already fully recovered.
- 3154 — The backup set holds a backup of a database other than the existing '%ls' database.
- 3155 — The RESTORE operation cannot proceed because one or more files have been added or dropped from the database since the backup set was created.
- 3156 — File '%ls' cannot be restored to '%ls'. Use WITH MOVE to identify a valid location for the file.
- 3159 — The tail of the log for the database "%ls" has not been backed up. Use BACKUP LOG WITH NORECOVERY to backup the log if it contains work you do not wan…
- 3161 — The primary file is unavailable. It must be restored or otherwise made available.
- 3163 — The transaction log was damaged. All data files must be restored before RESTORE LOG can be attempted.
- 3165 — Database '%ls' was restored, however an error was encountered while replication was being restored/removed. The database has been left offline. See th…
- 3166 — RESTORE DATABASE could not drop database '%ls'. Drop the database and then reissue the RESTORE DATABASE statement.
- 3167 — RESTORE could not start database '%ls'.
- 3168 — The backup of the system database on the device %ls cannot be restored because it was created by a different version of the server (%ls) than this ser…
- 3169 — The database was backed up on a server running version %ls. That version is incompatible with this server, which is running version %ls. Either restor…
- 3170 — The STANDBY filename is invalid.
- 3171 — File %ls is defunct and cannot be restored into the online database.
- 3172 — Filegroup %ls is defunct and cannot be restored into the online database.
- 3173 — The STOPAT clause provided with this RESTORE statement indicates that the tail of the log contains changes that must be backed up to reach the target …
- 3174 — The file '%ls' cannot be moved by this RESTORE operation.
- 3175 — RESTORE FILEGROUP="%ls" was specified, but not all of its files are present in the backup set. File "%ls" is missing. RESTORE will continue, but if yo…
- 3176 — File '%ls' is claimed by '%ls'(%d) and '%ls'(%d). The WITH MOVE clause can be used to relocate one or more files.
- 3178 — File %ls is not in the correct state to have this differential backup applied to it.
- 3179 — The system database cannot be moved by RESTORE.
- 3180 — This backup cannot be restored using WITH STANDBY because a database upgrade is needed. Reissue the RESTORE without WITH STANDBY.
- 3181 — Attempting to restore this backup may encounter storage space problems. Subsequent messages will provide details.
- 3182 — The backup set cannot be restored because the database was damaged when the backup occurred. Salvage attempts may exploit WITH CONTINUE_AFTER_ERROR.
- 3183 — RESTORE detected an error on page (%d:%d) in database "%ls" as read from the backup set.
- 3184 — RESTORE WITH CONTINUE_AFTER_ERROR was successful but some damage was encountered. Inconsistencies in the database are possible.
- 3185 — RESTORE cannot apply this backup set because the database is suspect. Restore a backup set that repairs the damage.
- 3186 — The backup set has been damaged. RESTORE will not attempt to apply this backup set.
- 3187 — RESTORE WITH CHECKSUM cannot be specified because the backup set does not contain checksum information.
- 3188 — The backup set was written with damaged data by a BACKUP WITH CONTINUE_AFTER_ERROR.
- 3189 — Damage to the backup set was detected.
- 3190 — Filegroup '%ls' cannot be restored because it does not exist in the backup set.
- 3191 — Restore cannot continue because file '%ls' cannot be written. Ensure that all files in the database are writable.
- 3192 — Restore was successful but deferred transactions remain. These transactions cannot be resolved because there are data that is unavailable. Either use …
- 3193 — Restore Log operations are not permitted for a Log Backup with FILE_SNAPSHOT if bulk operations were present during the backup period. The Restore can…
- 3194 — Page %S_PGID is beyond the end of the file. Only pages that are in the current range of the file can be restored.
- 3195 — Page %S_PGID cannot be restored from this backup set. RESTORE PAGE can only be used from full backup sets or from the first log or differential backup…
- 3196 — RESTORE master WITH SNAPSHOT is not supported. To restore master from a snapshot backup, stop the service and copy the data and log file.
- 3197 — I/O is frozen on database %ls. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
- 3198 — I/O was resumed on database %ls. No user action is required.
- 3199 — RESTORE requires MAXTRANSFERSIZE=%u but %u was specified.
- 3201 — Cannot open backup device '%ls'. Operating system error %ls.
- 3202 — Write on "%ls" failed: %ls
- 3203 — Read on "%ls" failed: %ls
- 3204 — The backup or restore was aborted.
- 3205 — Too many backup devices specified for backup or restore; only %d are allowed.
- 3206 — Backup device '%.*ls' does not exist. To view existing backup devices, use the sys.backup_devices catalog view. To create a new backup device use eith…
- 3207 — Backup or restore requires at least one backup device. Rerun your statement specifying a backup device.
- 3208 — Unexpected end of file while reading beginning of backup set. Confirm that the media contains a valid SQL Server backup set, and see the console error…
- 3209 — Operation is not supported on user instances.
- 3210 — The mirror member in drive "%ls" is inconsistent with the mirror member in drive "%ls".
- 3211 — %d percent processed.
- 3212 — The mirror device "%ls" and the mirror device "%ls" have different device specifications.
- 3213 — Unable to unload one or more tapes. See the error log for details.
- 3214 — Too many backup mirrors are specified. Only %d are allowed.
- 3215 — Use WITH FORMAT to create a new mirrored backup set.
- 3216 — RESTORE REWINDONLY is only applicable to tape devices.
- 3217 — Invalid value specified for %ls parameter.
- 3218 — Backup mirroring is not available in this edition of SQL Server. See Books Online for more details on feature support in different SQL Server editions…
- 3219 — The file or filegroup "%.*ls" cannot be selected for this operation.
- 3220 — The specified URL points to a Block Blob. Backup and Restore operations on Block Blobs are not supported when WITH CREDENTIAL syntax is used.
- 3221 — The ReadFileEx system function executed on file '%ls' only read %d bytes, expected %d.
- 3222 — The WriteFileEx system function executed on file '%ls' only wrote %d bytes, expected %d.
- 3223 — Backup To URL failed to write status messages to the operating system error log.
- 3224 — Cannot create worker thread.
- 3225 — Use of WITH CREDENTIAL syntax is not valid for credentials containing a Shared Access Signature.
- 3226 — Failed to create snapshot for file "%ls".
- 3227 — The backup media on "%ls" is part of media family %d which has already been processed on "%ls". Ensure that backup devices are correctly specified. Fo…
- 3228 — Writing snapshot metadata to backup set for file "%ls" failed due to invalid format.
- 3229 — Request for device '%ls' timed out.
- 3230 — Operation on device '%ls' exceeded retry count.
- 3231 — The media loaded on "%ls" is formatted to support %d media families, but %d media families are expected according to the backup device specification.
- 3232 — The volume mounted on "%ls" does not have the expected backup set identity. The volume may be obsolete due to a more recent overwrite of this media fa…
- 3233 — Invalid Identity Specified for the S3 Credential. Credential Identity should be S3 Access Key.
- 3234 — Logical file '%.*ls' is not part of database '%ls'. Use RESTORE FILELISTONLY to list the logical file names.
- 3235 — The file "%.*ls" is not part of database "%ls". You can only list files that are members of this database.
- 3236 — Write to S3 object storage device %ls failed. Device has reached its limit of %d allowed parts.
- 3238 — The Estimate for the Backup size exceeds the maximum allowed file size on the remote endpoint.
- 3239 — The backup set on device '%ls' uses a feature of the Microsoft Tape Format not supported by SQL Server.
- 3240 — Backup to mirrored media sets requires all mirrors to append. Provide all members of the set, or reformat a new media set.
- 3241 — The media family on device '%ls' is incorrectly formed. SQL Server cannot process this media family.
- 3242 — The file on device '%ls' is not a valid Microsoft Tape Format backup set.
- 3243 — The media family on device '%ls' was created using Microsoft Tape Format version %d.%d. SQL Server supports version %d.%d.
- 3244 — Descriptor block size exceeds %d bytes. Use a shorter name and/or description string and retry the operation.
- 3245 — Could not convert a string to or from Unicode, %ls.
- 3246 — The media family on device '%ls' is marked as nonappendable. Reissue the statement using the INIT option to overwrite the media.
- 3247 — The volume on device '%ls' has the wrong media sequence number (%d). Remove it and insert volume %d.
- 3249 — The volume on device '%ls' is a continuation volume for the backup set. Remove it and insert the volume holding the start of the backup set.
- 3250 — The value '%d' is not within range for the %ls parameter.
- 3251 — The media family on device '%ls' is complete. The device is now being reused for one of the remaining families.
- 3252 — Failed to copy snapshot with name '%ls', timestamp '%ls' to destination '%ls'. Error returned '%ls'.
- 3253 — The block size parameter must supply a value that is a power of 2.
- 3254 — The volume on device '%ls' is empty.
- 3255 — The data set on device '%ls' is a SQL Server backup set not compatible with this version of SQL Server.
- 3256 — The backup set on device '%ls' was terminated while it was being created and is incomplete. RESTORE sequence is terminated abnormally.
- 3257 — There is insufficient free space on disk volume '%ls' to create the database. The database requires %I64u additional free bytes, while only %I64u byte…
- 3258 — The volume on the device "%ls" is not part of the media set that is currently being processed. Ensure that the backup devices are loaded with the corr…
- 3259 — Failed to copy blob with name '%ls', to destination '%ls'. Error returned '%ls'.
- 3260 — An internal buffer has become full.
- 3261 — SQL Server cannot use the virtual device configuration.
- 3262 — The backup set on file %d is valid.
- 3263 — Cannot use the volume on device '%ls' as a continuation volume. It is sequence number %d of family %d for the current media set. Insert a new volume, …
- 3264 — The operation did not proceed far enough to allow RESTART. Reissue the statement without the RESTART qualifier.
- 3265 — The login has insufficient authority. Membership of the sysadmin role is required to use VIRTUAL_DEVICE with BACKUP or RESTORE.
- 3266 — The backup data at the end of "%ls" is incorrectly formatted. Backup sets on the media might be damaged and unusable. To determine the backup sets on …
- 3267 — Insufficient resources to create UMS scheduler.
- 3268 — Cannot use the backup file '%ls' because it was originally formatted with sector size %d and is now on a device with sector size %d.
- 3269 — Cannot restore the file '%ls' because it was originally written with sector size %d; '%ls' is now on a device with sector size %d.
- 3270 — An internal consistency error has occurred. This error is similar to an assert. Contact technical support for assistance.
- 3271 — A nonrecoverable I/O error occurred on file "%ls:" %ls.
- 3272 — The '%ls' device has a hardware sector size of %d, but the block size parameter specifies an incompatible override value of %d. Reissue the statement …
- 3273 — The BUFFERCOUNT parameter must supply a value that allows at least one buffer per backup device.
- 3276 — WITH SNAPSHOT can be used only if the backup set was created WITH SNAPSHOT.
- 3277 — WITH SNAPSHOT must be used with only one virtual device.
- 3278 — Failed to encrypt string %ls
- 3279 — Access is denied due to a password failure
- 3280 — Backups on raw devices are not supported. '%ls' is a raw device.
- 3281 — Released and initiated rewind on '%ls'.
- 3283 — The file "%ls" failed to initialize correctly. Examine the error logs for more details.
- 3284 — Filemark on device '%ls' is not aligned. Re-issue the Restore statement with the same blocksize used to create the backupset: '%d' looks like a possib…
- 3285 — Filemark on device '%ls' appears not to be aligned. The restore operation will proceed using less efficient I/O. To avoid this, re-issue the Restore s…
- 3286 — Backup failed because there is a mismatch in file metadata for file %d.
- 3287 — The file ID %d on device '%ls' is incorrectly formed and can not be read.
- 3288 — Credential name %.*ls does not exist or user does not have permission to access it.
- 3289 — A Backup device of type URL was specified without a Credential, Backup/Restore operation cannot proceed.
- 3290 — Backup to URL received an exception from the remote endpoint. Exception Message: %.*ls
- 3291 — URL device type was specified, and a disallowed option %ls was specified.
- 3292 — A failure occurred while attempting to execute Backup or Restore with a URL device specified. Consult the operating system error log for details.
- 3293 — An error occurred while Backup/Restore to URL was initializing. Error message: %.*ls.
- 3294 — Use of the URL device type is limited to a single device during Backup and Restore operations.
- 3295 — Backup To URL error: Exclusive access to the file %.*ls could not be obtained.
- 3296 — The file %.*ls exists on the remote endpoint, and WITH FORMAT was not specified. Backup cannot proceed.
- 3297 — The URL provided does not meet specified requirements. The URL must be either resolvable as an absolute or relative URI, has or can be composed as an …
- 3298 — Backup/Restore to URL device error: %.*ls.
- 3299 — BackupToUrl initiated.
- 3301 — The transaction log contains a record (logop %d) that is not valid. The log has been corrupted. Restore the database from a full backup, or repair the…
- 3302 — Redoing of logged operations in database '%.*ls' failed to reach end of log at log record ID %S_LSN. This indicates corruption around log record ID %S…
- 3303 — Remote harden of transaction '%.*ls' (ID 0x%016I64x %ls) started at %S_DATE in database '%ls' at LSN %S_LSN failed.
- 3313 — During redoing of a logged operation in database '%.*ls', an error occurred at log record ID %S_LSN. Typically, the specific failure is previously log…
- 3314 — During undoing of a logged operation in database '%.*ls', an error occurred at log record ID %S_LSN. Typically, the specific failure is logged previou…
- 3315 — During rollback, the following process did not hold an expected lock: process %d with mode %d at level %d for row %S_RID in database '%.*ls' under tra…
- 3316 — During undo of a logged operation in database '%.*ls', an error occurred at log record ID %S_LSN. The row was not found. Restore the database from a f…
- 3317 — Async crash recovery failed for database '%.*ls' (database ID %d). Failed to enqueue log block to the parallel redo cache during the MIN_REDO pass due…
- 3401 — Errors occurred during recovery while rolling back a transaction. The transaction was deferred. Restore the bad page or file, and re-run recovery.
- 3402 — The database '%ls' is marked %ls and is in a state that does not allow recovery to be run.
- 3403 — Recovering only master database because traceflag 3608 was specified. This is an informational message only. No user action is required.
- 3404 — Failed to check for new installation or a renamed server at startup. The logic for this check has failed unexpectedly. Run setup again, or fix the pro…
- 3406 — %d transactions rolled forward in database '%.*ls' (%d:%d). This is an informational message only. No user action is required.
- 3407 — %d transactions rolled back in database '%.*ls' (%d:%d). This is an informational message only. No user action is required.
- 3408 — Recovery is complete. This is an informational message only. No user action is required.
- 3409 — Performance counter shared memory setup failed with error %d. Reinstall sqlctr.ini for this instance, and ensure that the instance login account has c…
- 3410 — Data in filegroup %s is offline, and deferred transactions exist. Use RESTORE to recover the filegroup, or drop the filegroup if you never intend to r…
- 3411 — Configuration block version %d is not a valid version number. SQL Server is exiting. Restore the master database or reinstall.
- 3412 — Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuratio…
- 3413 — Database ID %d. Could not mark database as suspect. Getnext NC scan on sys.databases.database_id failed. Refer to previous errors in the error log to …
- 3414 — An error occurred during recovery, preventing the database '%ls' (%d:%d) from restarting. Diagnose the recovery errors and fix them, or restore from a…
- 3415 — Database '%.*ls' cannot be upgraded because it is read-only, has read-only files or the user does not have permissions to modify some of the files. Ma…
- 3416 — The server contains read-only files that must be made writable before the server can be recollated.
- 3417 — Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information abo…
- 3418 — Recovery is unable to defer error %d. Errors can only be deferred in databases using the full recovery model and an active backup log chain.
- 3419 — Recovery for database '%.*ls' is being skipped because it requires an upgrade but is marked for Standby. Use RESTORE DATABASE WITH NORECOVERY to take …
- 3420 — Database snapshot '%ls' has failed an IO operation and is marked suspect. It must be dropped and recreated.
- 3421 — Recovery completed for database %ls (database ID %d) in %I64d second(s) (analysis %I64d ms, redo %I64d ms, undo %I64d ms.) This is an informational me…
- 3422 — Database %ls was shutdown due to error %d in routine '%hs'. Restart for non-snapshot databases will be attempted after all connections to the database…
- 3423 — Info: The server instance was started using multiuser, minimal configuration startup option (-M).
- 3429 — Recovery could not determine the outcome of a cross-database transaction %S_XID, named '%.*ls', in database '%.*ls' (database ID %d:%d). The coordinat…
- 3431 — Could not recover database '%.*ls' (database ID %d) because of unresolved transaction outcomes. Microsoft Distributed Transaction Coordinator (MS DTC)…
- 3434 — Cannot change sort order or locale. An unexpected failure occurred while trying to reindex the server to a new collation. SQL Server is shutting down.…
- 3437 — An error occurred while recovering database '%.*ls'. Unable to connect to Microsoft Distributed Transaction Coordinator (MS DTC) to check the completi…
- 3441 — During startup of warm standby database '%.*ls' (database ID %d), its standby file ('%ls') was inaccessible to the RESTORE statement. The operating sy…
- 3443 — Database '%ls' (database ID %d:%d) was marked for standby or read-only use, but has been modified. The RESTORE LOG statement cannot be performed. Rest…
- 3445 — File '%ls' is not a valid undo file for database '%.*ls (database ID %d). Verify the file path, and specify the correct file.
- 3446 — Primary log file is not available for database '%ls' (%d:%d). The log cannot be backed up.
- 3447 — Could not activate or scan all of the log files for database '%.*ls'.
- 3448 — Rollback encountered a page with a log sequence number (LSN) less than the original log record LSN. Could not undo log record %S_LSN, for transaction …
- 3449 — SQL Server must shut down in order to recover a database (database ID %d). The database is either a user database that could not be shut down or a sys…
- 3450 — Recovery of database '%.*ls' (%d) is %d%% complete (approximately %d seconds remain). Phase %d of 3. This is an informational message only. No user ac…
- 3452 — Recovery of database '%.*ls' (%d) detected possible identity value inconsistency in table ID %d. Run DBCC CHECKIDENT ('%.*ls').
- 3453 — This version cannot redo any index creation or non-logged operation done by SQL Server 7.0. Further roll forward is not possible.
- 3454 — Recovery is writing a checkpoint in database '%.*ls' (%d). This is an informational message only. No user action is required.
- 3456 — Could not redo log record %S_LSN, for transaction ID %S_XID, on page %S_PGID, allocation unit %I64d, database '%.*ls' (database ID %d). Page: LSN = %S…
- 3457 — Transactional file system resource manager '%.*ls' failed to recover. For more information, see the accompanying error message, which determines the a…
- 3458 — Recovery cannot scan database "%.*ls" for dropped allocation units because an unexpected error has occurred. These allocation units cannot be cleaned …
- 3459 — Recovery of database "%.*ls" failed to redo a file add for file "%.*ls". Please delete the file and retry.
- 3460 — Failed to shutdown a database (database ID %d) that contains memory-optimized data. Restart SQL Server to bring the database to a consistent state. If…
- 3461 — Failed to wait for XTP %ls to complete during recovery.
- 3462 — Redo observed a higher LSN on the PFS page %S_PGID for transaction ID %S_XID, database '%.*ls' (database ID %d). Redo LSN: %S_LSN, Page: LSN = %S_LSN,…
- 3463 — An error occurred while recovering database '%.*ls'. Transaction outcome could not be resolved.
- 3464 — An error occurred while resolving the deferred transaction. Transaction outcome: %d, IsDeferred: %ls.
- 3465 — An error occurred while resolving the deferred transaction. Transaction not found.
- 3466 — Restore was successful but deferred transactions remain. These transactions cannot be resolved because there are data or keys in the enclave that is u…
- 3467 — Restore was successful but deferred transactions remain. These transactions cannot be resolved because there are data or keys in the enclave that is u…
- 3468 — Restore failed due to items not being found in the expected restore pipeline queues.
- 3469 — Restore failed due to items not being found in the expected restore pipeline queues.
- 3470 — The recovery of the database "%.*ls" could not redo the file size change for file "%.*ls" because of the missing connection.
- 3471 — The database "%.*ls" could not proceed to recovery due to failure (code 0x%08x) of entering the cluster mode: %ls.
- 3472 — The database '%.*ls' could not complete startup due to GXM catchup failure (0x%08x).
- 3473 — The database "%.*ls" could not complete recovery due to GXM recovered notification failure (code 0x%08x): %ls.
- 3505 — Only the owner of database "%.*ls" or someone with relevant permissions can run the CHECKPOINT statement.
- 3604 — Duplicate key was ignored.
- 3605 — Schema verification failed for database '%.*ls'.
- 3606 — Arithmetic overflow occurred.
- 3607 — Division by zero occurred.
- 3608 — Cannot allocate a GUID for the token.
- 3609 — The transaction ended in the trigger. The batch has been aborted.
- 3611 — %hs SQL Server Execution Times:%hs CPU time not measured under fiber mode, elapsed time = %lu ms.
- 3612 — %hs SQL Server Execution Times:%hs CPU time = %lu ms, elapsed time = %lu ms.
- 3613 — SQL Server parse and compile time: %hs CPU time = %lu ms, elapsed time = %lu ms.
- 3614 — Batch Statistics: Overall Duration = %f ms, CPU time = %f ms, Total logical reads = %lu, physical reads = %lu, remote reads = %lu, logical writes = %l…
- 3615 — Table '%.*ls'. Scan count %d, logical reads %d, physical reads %d, read-ahead reads %d, lob logical reads %d, lob physical reads %d, lob read-ahead re…
- 3616 — An error was raised during trigger execution. The batch has been aborted and the user transaction, if any, has been rolled back.
- 3619 — Could not write a checkpoint record in database %ls because the log is out of space. Contact the database administrator to truncate the log or allocat…
- 3620 — Automatic checkpointing is disabled in database '%.*ls' because the log is out of space. Automatic checkpointing will be enabled when the database own…
- 3621 — The statement has been terminated.
- 3622 — Warning: An invalid floating point operation occurred.
- 3623 — An invalid floating point operation occurred.
- 3624 — A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data c…
- 3625 — '%hs' is not yet implemented.
- 3627 — New parallel operation cannot be started due to too many parallel operations executing at this time. Use the "max worker threads" configuration option…
- 3628 — The Database Engine received a floating point exception from the operating system while processing a user request. Try the transaction again. If the p…
- 3633 — The operating system returned the error '%ls' while attempting '%ls' on '%ls' at '%hs'(%d).
- 3634 — The operating system returned the error '%ls' while attempting '%ls' on '%ls'.
- 3635 — An error occurred while processing '%ls' metadata for database id %d, file id %d, and transaction='%.*ls'. Additional Context='%ls'. Location='%hs'(%d…
- 3636 — An error occurred while processing '%ls' metadata for database id %d file id %d.
- 3637 — A parallel operation cannot be started from a DAC connection.
- 3641 — Total logical reads %lu, physical reads %lu, writes %lu.
- 3642 — Table '%.*ls'. Segment reads %u, segment skipped %u.
- 3643 — The operation elapsed time exceeded the maximum time specified for this operation. The execution has been stopped.
- 3644 — Prefaulter task failed for file %ls with error %d.
- 3645 — Batch Connectivity Statistics: Packets Read Time = %f ms, Packets Read Time Before Exec = %f ms, Packets Write Time = %f ms, Packets Write Time Before…
- 3646 — Thrown by a utility function documented with "fails by throwing an exception that caller MUST catch." Users should not see this error.
- 3647 — The operation is blocked by delayed database version upgrade. The execution hasn't started.
- 3648 — %hsObject '%.*ls'. Tempdb versions read %lu, in-row PVS versions read %lu, off-row PVS versions read %lu, online index PVS versions read %lu.
- 3696 — Internal error while preparing GUID.
- 3697 — Batch Waits Statistics: %ls
- 3701 — Cannot %S_MSG the %S_MSG '%.*ls', because it does not exist or you do not have permission.
- 3702 — Cannot drop database "%.*ls" because it is currently in use.
- 3703 — Cannot detach the %S_MSG '%.*ls' because it is currently in use.
- 3705 — Cannot use DROP %ls with '%.*ls' because '%.*ls' is a %S_MSG. Use %ls.
- 3706 — Cannot %S_MSG a database snapshot.
- 3707 — Cannot detach a suspect or recovery pending database. It must be repaired or dropped.
- 3708 — Cannot %S_MSG the %S_MSG '%.*ls' because it is a system %S_MSG.
- 3709 — Cannot %S_MSG the database while the database snapshot "%.*ls" refers to it. Drop that database first.
- 3710 — Cannot detach an opened database when the server is in minimally configured mode.
- 3716 — The %S_MSG '%.*ls' cannot be dropped because it is bound to one or more %S_MSG.
- 3717 — Cannot drop a default constraint by DROP DEFAULT statement. Use ALTER TABLE to drop a constraint default.
- 3718 — Could not drop index '%.*ls' because the table or clustered index entry cannot be found in the sysindexes system table.
- 3721 — Type '%.*ls' cannot be renamed because it is being referenced by object '%.*ls'.
- 3722 — Task has been aborted, but %S_MSG of the %S_MSG '%.*ls' may continue in the background. Please check whether the %S_MSG has finished successfully.
- 3723 — An explicit DROP INDEX is not allowed on index '%.*ls'. It is being used for %ls constraint enforcement.
- 3724 — Cannot %S_MSG the %S_MSG '%.*ls' because it is being used for replication.
- 3725 — The constraint '%.*ls' is being referenced by table '%.*ls', foreign key constraint '%.*ls'.
- 3726 — Could not drop object '%.*ls' because it is referenced by a FOREIGN KEY constraint.
- 3727 — Could not drop constraint. See previous errors.
- 3728 — '%.*ls' is not a constraint.
- 3729 — Cannot %ls '%.*ls' because it is being referenced by object '%.*ls'.
- 3730 — Cannot drop the default constraint '%.*ls' while it is being used by a foreign key as SET DEFAULT referential action.
- 3732 — Cannot drop type '%.*ls' because it is being referenced by object '%.*ls'. There may be other objects that reference this type.
- 3733 — Constraint '%.*ls' does not belong to table '%.*ls'.
- 3734 — Could not drop the primary key constraint '%.*ls' because the table has an XML or spatial index.
- 3735 — The primary key constraint '%.*ls' on table '%.*ls' cannot be dropped because change tracking is enabled on the table. Change tracking requires a prim…
- 3736 — Cannot drop the %S_MSG '%.*ls' because it is being used for distribution.
- 3737 — Could not delete file '%ls'. See the SQL Server error log for more information.
- 3738 — Deleting database file '%ls'.
- 3739 — Cannot %ls the index '%.*ls' because it is not a statistics collection.
- 3740 — Cannot drop the %S_MSG '%.*ls' because at least part of the table resides on a read-only filegroup.
- 3741 — Cannot drop the %S_MSG '%.*ls' because at least part of the table resides on an offline filegroup.
- 3743 — The database '%.*ls' is enabled for database mirroring. Database mirroring must be removed before you drop the database.
- 3744 — Only a single clause is allowed in a statement where an index is dropped online.
- 3745 — Only a clustered index can be dropped online.
- 3746 — Cannot drop the clustered index of view '%.*ls' because the view is being used for replication.
- 3747 — Cannot drop a clustered index created on a view using drop clustered index clause. Clustered index '%.*ls' is created on view '%.*ls'.
- 3748 — Cannot drop non-clustered index '%.*ls' using drop clustered index clause.
- 3749 — Cannot drop XML Index '%.*ls' using old 'Table.Index' syntax, use 'Index ON Table' syntax instead.
- 3750 — Warning: Index '%.*ls' on %S_MSG '%.*ls' was disabled as a result of disabling the clustered index on the %S_MSG.
- 3751 — Cannot use SP_DROPEXTENDEDPROC or DBCC DROPEXTENDEDPROC with '%.*ls' because '%.*ls' is a %S_MSG. Use %ls.
- 3752 — The database '%.*ls' is currently joined to an availability group. Before you can drop the database, you need to remove it from the availability group…
- 3753 — Cannot %S_MSG the federation member '%.*ls', because the federation root does not exist.
- 3754 — TRUNCATE TABLE statement failed. Index '%.*ls' uses partition function '%.*ls', but table '%.*ls' uses non-equivalent partition function '%.*ls'. Inde…
- 3755 — Cannot drop a database with file snapshots on it. Please detach the database instead of dropping or delete the file snapshots and retry the drop.
- 3756 — TRUNCATE TABLE statement failed. Index '%.*ls' is not partitioned, but table '%.*ls' uses partition function '%.*ls'. Index and table must use an equi…
- 3757 — WAIT_AT_LOW_PRIORITY clause is not permitted without ONLINE = ON option, for drop clustered %S_MSG '%.*ls' on Table '%.*ls'.
- 3758 — Multiple %S_MSG cannot be dropped when WAIT_AT_LOW_PRIORITY clause is specified.
- 3759 — %.*ls constraint '%.*ls' cannot be dropped when WAIT_AT_LOW_PRIORITY clause is used.
- 3760 — Cannot drop index '%.*ls' on view '%.*ls' that has SNAPSHOT_MATERIALIZATION.