SQL Server Helper

Tip of the Day : SQL Server Database Design - Twitter Profile and Followers

Error Messages

Home > Tips & Tricks > Error Messages 12001 to 13000

SQL Server Error Messages - Errors 12001 to 13000

SQL Server Error Message - Errors 12001 to 13000

A message number uniquely identifies each error message and the error message text describes the problem. The error message text often includes placeholders for information (such as object names) to be inserted in the error message when it is displayed. Unfortunately, the error message text does not tell you how to solve or work around the problem. In this series of Error Messages list, we will try to provide you with ways on how to overcome or work around certain error messages.

Some error messages are self-explanatory and can easily be fixed, such as "Invalid object name". Others are harder to fix or work around, especially by those who are new to SQL Server. It is the intent of this page and succeeding pages (to come) to assist you in addressing or working around SQL Server error messages.

Error	Severity	Description
12002	16	The requested %S_MSG index on column '%.ls' of table '%.ls' could not be created because the column type is not %S_MSG . Specify a column name that refers to a column with a %S_MSG data type.
12003	16	Could not find spatial tessellation scheme '%.ls' for column of type %.ls. Specify a valid tessellation scheme name in your USING clause.
12004	16	Could not find the default spatial tessellation scheme for the column '%.ls' on table '%.ls'. Make sure that the column reference is correct, or specify the extension scheme in a USING clause.
12005	16	Incorrect parameters were passed to the CREATE %S_MSG statement near '%.*ls'. Validate the statement against the index-creation syntax.
12006	16	Duplicate parameters were passed to the create index statement. Validate the statement against the index-creation syntax.
12007	16	The CREATE %S_MSG statement is missing the required parameter '%.*ls'. Validate the statement against the index-creation syntax.
12008	16	Table '%.*ls' does not have a clustered primary key as required by the %S_MSG index. Make sure that the primary key column exists on the table before creating a %S_MSG index.
12009	16	Could not find the %S_MSG index '%.ls' on table '%.ls'. Either no %S_MSG index with this name exists, or a non-%S_MSG index might be using the same name. Fix the index name, avoiding duplicates. If a relational index has the same name, drop the regular
12010	16	Only one spatial index hint may appear per table, either as the first or the last hinted index.
12011	16	The value of parameter '%.*ls' of CREATE %S_MSG must be less than %d.
12012	16	The value of parameter '%.*ls' of CREATE %S_MSG must be greater than %d.
12013	16	The value of parameter '%.ls' of CREATE %S_MSG must be greater than the value of parameter '%.ls'.
12014	16	The '%.*ls' parameter of CREATE %S_MSG is incompletely defined. If the parameter has more than one part, all the parts must be defined.
12015	16	The index option %.*ls in the CREATE %S_MSG statement has to appear before the general index options.
12016	16	Creating a %S_MSG index requires that the primary key in the base table satisfy the following restrictions. The maximum number of primary-key columns is %d. The maximum combined per-row size of the primary-key columns is %d bytes. The primary key on the
12017	10	The spatial index is disabled or offline
12018	10	The spatial object is not defined in the scope of the predicate
12019	10	Spatial indexes do not support the comparand supplied in the predicate
12020	10	Spatial indexes do not support the comparator supplied in the predicate
12021	10	Spatial indexes do not support the method name supplied in the predicate
12022	10	The comparand references a column that is defined below the predicate
12023	10	The comparand in the comparison predicate is not deterministic
12024	10	The spatial parameter references a column that is defined below the predicate
12025	10	Could not find required binary spatial method in a condition
12026	10	Could not find required comparison predicate
12101	16	Cannot disable change tracking on database '%.*ls' while client connections are waiting on change notification. Please close those connections before disabling change tracking.
12104	15	ALTER DATABASE CURRENT failed because '%.*ls' is a system database. System databases cannot be altered by using the CURRENT keyword. Use the database name to alter a system database.

Error	Severity	Description
12800	16	The reference to temp table name '%.ls' is ambiguous and cannot be resolved. Use either '%.ls' or '%.*ls'.
12801	16	The reference to cursor name '%.ls' is ambiguous and cannot be resolved. Possible candidates are '%.ls' and '%.*ls'.
12803	16	Containment cannot be enabled for database '%.*ls' because it is a system database.
12804	16	Feature or option "%ls" breaches containment in a contained database. Please see Books Online topic Understanding Contained Databases for more information on contained databases.
12805	16	Index name '%.*ls' is too long. Maximum length for temp table index name is %d characters.
12807	16	The option '%.*ls' cannot be set on non-contained database.
12808	16	The option '%.*ls' cannot be set on a database while containment is being set to NONE.
12810	16	The option '%.*ls' was specified multiple times.
12811	16	The user options for the instance must be set to 0 in order to %S_MSG a contained database.
12813	16	Errors were encountered in the %S_MSG '%.ls' during compilation of the object. Either the containment option of the database '%.ls' was changed, or this object was present in model db and the user tried to create a new contained database.
12814	16	The object referenced as '%.ls' resolves differently in the target metadata collation '%.ls' than in the current metadata collation '%.*ls'.
12815	16	The column referenced as '%.ls' resolves differently in the target metadata collation '%.ls' than in the current metadata collation '%.*ls'.
12816	16	The type or XML schema collection referenced as '%.ls' resolves differently in the target metadata collation '%.ls' than in the current metadata collation '%.*ls'.
12817	16	The reference to the variable, parameter or goto label '%.ls' resolves differently in the target metadata collation '%.ls' than in the current metadata collation '%.*ls'.
12818	16	RECONFIGURE failed. Attempting to change the 'contained database authentication' value to 0 while there are existing contained databases requires a RECONFIGURE WITH OVERRIDE.
12819	16	sp_migrate_user_to_contained cannot be used in a non-contained database (a database with CONTAINMENT set to NONE).
12820	16	sp_migrate_user_to_contained can not be used with a user with a password or a user type other than SQL Login.
12821	16	sp_migrate_user_to_contained cannot be used on a user used in the EXECUTE AS clause of a signed module.
12822	16	sp_migrate_user_to_contained cannot be used to copy a password to an old hash algorithm.
12823	16	sp_migrate_user_to_contained can not find the login for user '%.*ls'.
12824	16	The sp_configure value 'contained database authentication' must be set to 1 in order to %S_MSG a contained database. You may need to use RECONFIGURE to set the value_in_use.
12825	16	The database cannot be contained; this functionality is not available in the current edition of SQL Server.
12826	16	RECONFIGURE WITH OVERRIDE set the 'contained database authentication' to 0 while there are contained databases in use. This will disrupt authentication for contained users and will not allow new contained databases to be created.
12827	16	User-named %ls constraint '%.ls' is not allowed on temp table '%.ls' because it is being created in a contained database. Please consult the Books Online topic Understanding Contained Databases for more information on contained databases.
12828	16	User-defined %S_MSG '%.ls' in tempdb cannot be referenced from local temp table '%.ls' because the temp table is being created in a contained database. Please consult the Books Online topic Understanding Contained Databases for more information on conta
12829	16	The stored procedure '%.*ls' refers to a group of numbered stored procedures. Numbered stored procedures are not available in contained databases. Please consult the Books Online topic Understanding Contained Databases for more information on contained da
12830	16	The sp_configure 'user options' setting must be zero if the Database Engine has contained databases.
12831	16	Database '%.*ls' is a contained database. The option 'contained database authentication' setting is 0. Users with passwords will not be able to login to contained databases.
12832	16	The database '%.ls' could not be created or altered to a contained database, because the schema bound %S_MSG '%.ls' depends on builtin function '%s'. In a contained database, the output collation of this builtin function has changed to '%.*ls', which di
12833	16	The database '%.ls' could not be created or altered to a contained database, because the check constraint '%.ls' on table '%.*ls' depends on builtin function '%s'. In a contained database, the output collation of this builtin function has changed to '%.
12834	16	The database '%.ls' could not be created or altered to a contained database, because the computed column '%.ls' on %S_MSG '%.*ls' depends on builtin function '%s'. In a contained database, the output collation of this builtin function has changed to '%.
12835	10	The definition of the %S_MSG '%.ls' was refreshed as part of altering the containment option of the database '%.ls' because the object depends on builtin function '%s'. In a contained database, the output collation of this builtin function has changed t
12836	16	ALTER DATABASE statement failed. The containment option of the database '%.*ls' could not be altered because compilation errors were encountered during validation of SQL modules. See previous errors.
12837	16	CREATE DATABASE statement failed. The contained database '%.*ls' could not be created because compilation errors were encountered during validation of SQL modules. See previous errors.
12838	16	Replication, Change Data Capture and Change Tracking are not supported in contained databases. The database '%.*ls' cannot be altered to a contained database, since it has one of these options turned on.
12839	16	Replication, Change Data Capture and Change Tracking are not supported in contained databases. The option cannot be enabled on the contained database '%s'.
12840	16	CREATE DATABASE failed. Recollating the database failed while creating the partially contained database '%.ls', with a default data collation of '%.ls'.
12841	16	ALTER DATABASE failed. Recollating the database failed while altering the database '%.*ls' to containment='%ls'.
12842	16	The COLLATE CATALOG_DEFAULT clause cannot be used in a constraint, computed column, index filter expression, or any schema-bound object.
12843	16	The containment state of database '%.*ls' does not match the value in master. Contained database functionality will not work as expected. Detach and re-attach the database to correct the database state in master.
12980	16	Supply either %s or %s to identify the log entries.
12981	16	You must specify %s when creating a subplan.
12982	16	Supply either %s or %s to identify the plan or sub-plan to be run.