SQL Server System Errors: 12000 - 12999
List of error messages between 12000 and 12999 in SQL Server 2017.
These error messages are all available by querying the sys.messages
catalog view on the master
database.
message_id | severity | is_event_logged | text |
---|---|---|---|
12002 | 16 | 0 | 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 | 0 | Could not find spatial tessellation scheme '%.*ls' for column of type %.*ls. Specify a valid tessellation scheme name in your USING clause. |
12004 | 16 | 0 | 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 | 0 | Incorrect parameters were passed to the CREATE %S_MSG statement near '%.*ls'. Validate the statement against the index-creation syntax. |
12006 | 16 | 0 | Duplicate parameters were passed to the create index statement. Validate the statement against the index-creation syntax. |
12007 | 16 | 0 | The CREATE %S_MSG statement is missing the required parameter '%.*ls'. Validate the statement against the index-creation syntax. |
12008 | 16 | 0 | 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 | 0 | 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 relational index. |
12010 | 16 | 0 | Only one spatial index hint may appear per table, either as the first or the last hinted index. |
12011 | 16 | 0 | The value of parameter '%.*ls' of CREATE %S_MSG must be less than %d. |
12012 | 16 | 0 | The value of parameter '%.*ls' of CREATE %S_MSG must be greater than %d. |
12013 | 16 | 0 | The value of parameter '%.*ls' of CREATE %S_MSG must be greater than the value of parameter '%.*ls'. |
12014 | 16 | 0 | 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 | 0 | The index option %.*ls in the CREATE %S_MSG statement has to appear before the general index options. |
12016 | 16 | 0 | 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 base table '%.*ls' has %d columns, and contains %d bytes. Alter the base table to satisfy the primary-key restrictions imposed by the %S_MSG index. |
12017 | 10 | 0 | The spatial index is disabled or offline |
12018 | 10 | 0 | The spatial object is not defined in the scope of the predicate |
12019 | 10 | 0 | Spatial indexes do not support the comparand supplied in the predicate |
12020 | 10 | 0 | Spatial indexes do not support the comparator supplied in the predicate |
12021 | 10 | 0 | Spatial indexes do not support the method name supplied in the predicate |
12022 | 10 | 0 | The comparand references a column that is defined below the predicate |
12023 | 10 | 0 | The comparand in the comparison predicate is not deterministic |
12024 | 10 | 0 | The spatial parameter references a column that is defined below the predicate |
12025 | 10 | 0 | Could not find required binary spatial method in a condition |
12026 | 10 | 0 | Could not find required comparison predicate |
12101 | 16 | 0 | Cannot disable change tracking on database '%.*ls' while client connections are waiting on change notification. Please close those connections before disabling change tracking. |
12102 | 16 | 0 | ALTER DATABASE failed because the distribution policy of system databases cannot be changed. |
12103 | 16 | 0 | ALTER DATABASE failed because the distribution policy is invalid. The database distribution policy must be set to either NONE or HASH. For the distribution policy NONE, the number of leading hash columns cannot be specified. For the distribution policy HASH, the number of leading hash columns is optional but cannot be more than 16 columns. |
12104 | 15 | 0 | 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. |
12105 | 10 | 0 | Waiting for the nonqualified transactions to be rolled back on the remote brick %d. |
12106 | 16 | 0 | The path name '%.*ls' is already used by another database file. Change to another valid and UNUSED name. |
12107 | 16 | 0 | Adding a MEMORY_OPTIMIZED_DATA filegroup is not supported for databases that have one or more publications that use sync_method 'database snapshot' or 'database snapshot character'. |
12108 | 16 | 0 | '%d' is out of range for the database scoped configuration option '%.*ls'. See sp_configure option '%ls' for valid values. |
12109 | 16 | 0 | Statement '%.*ls' failed, because it attempted to set the value to '%.*ls' for the primary replica. A settings can only be set to '%.*ls' when the setting is applied to the secondary. |
12110 | 16 | 0 | Statement '%.*ls' failed, because it attempted to set the '%.*ls' option for the secondaries replica while this option is only allowed to be set for the primary. |
12300 | 15 | 0 | Computed columns are not supported with %S_MSG. |
12301 | 15 | 0 | Nullable columns in the index key are not supported with %S_MSG. |
12302 | 15 | 0 | Updating columns that are part of the PRIMARY KEY constraint is not supported with %S_MSG. |
12303 | 15 | 0 | The 'number' clause is not supported with %S_MSG. |
12305 | 15 | 0 | Inline table variables are not supported with %S_MSG. |
12306 | 15 | 0 | Cursors are not supported with %S_MSG. |
12307 | 15 | 0 | Default values for parameters in %S_MSG must be constants. |
12308 | 15 | 0 | Table-valued functions are not supported with %S_MSG. |
12309 | 15 | 0 | Statements of the form INSERT...VALUES... that insert multiple rows are not supported with %S_MSG. |
12310 | 15 | 0 | Common Table Expressions (CTE) are not supported with %S_MSG. |
12311 | 15 | 0 | Subqueries (queries nested inside another query) is only supported in SELECT statements with %S_MSG. |
12312 | 15 | 0 | Partition functions are not supported with %S_MSG. |
12313 | 15 | 0 | User-defined functions are not supported with %S_MSG. |
12314 | 15 | 0 | User-defined methods are not supported with %S_MSG. |
12315 | 15 | 0 | User-defined properties are not supported with %S_MSG. |
12316 | 15 | 0 | User-defined aggregates are not supported with %S_MSG. |
12317 | 15 | 0 | Clustered indexes, which are the default for primary keys, are not supported with %S_MSG. Specify a NONCLUSTERED index instead. |
12318 | 15 | 0 | Browse mode metadata is not supported with %S_MSG. |
12319 | 15 | 0 | Using the FROM clause in an UPDATE statement and specifying a table source in a DELETE statement is not supported with %S_MSG. |
12320 | 15 | 0 | Operations that require a change to the schema version, for example renaming, are not supported with %S_MSG. |
12321 | 15 | 0 | Creating a temporary procedure is not supported with %S_MSG. |
12322 | 15 | 0 | Temporary tables are not supported with %S_MSG. |
12323 | 15 | 0 | Distributed Queries and Multiple Active Result Sets (MARS) are not supported with %S_MSG. |
12324 | 15 | 0 | Distributed transactions (DTC) are not supported with %S_MSG. |
12325 | 15 | 0 | Bound transactions are not supported with %S_MSG. |
12326 | 15 | 0 | Creating a savepoint is not supported with %S_MSG. |
12327 | 15 | 0 | Comparison, sorting, and manipulation of character strings that do not use a *_BIN2 collation is not supported with %S_MSG. |
12328 | 15 | 0 | Indexes on character columns that do not use a *_BIN2 collation are not supported with %S_MSG. |
12329 | 15 | 0 | The data types char(n) and varchar(n) using a collation that has a code page other than 1252 are not supported with %S_MSG. |
12330 | 15 | 0 | Truncation of character strings with an SC collation is not supported with %S_MSG. |
12331 | 15 | 0 | DDL statements ALTER, DROP and CREATE inside user transactions are not supported with %S_MSG. |
12332 | 15 | 0 | Database and server triggers on DDL statements CREATE, ALTER and DROP are not supported with %S_MSG. |
12333 | 15 | 0 | Execution from the dedicated administrator connection (DAC) is not supported with %S_MSG. |
12334 | 15 | 0 | The aggregate functions MIN and MAX used with binary and character string data types is not supported with %S_MSG. |
12336 | 15 | 0 | The use of replication is not supported with %S_MSG. |
12337 | 15 | 0 | The use of the sp_addpublication sync_method's parameters 'database snapshot' and 'database snapshot character' are not supported with %S_MSG. |
12338 | 15 | 0 | The functions LEN and SUBSTRING with an argument in an SC collation are not supported with %S_MSG. |
12339 | 15 | 0 | The use of seed and increment values other than 1 is not supported with %S_MSG. |
12340 | 15 | 0 | The EXECUTE statement in %S_MSG must use an object name. Variables and quoted identifiers are not supported. |
12341 | 15 | 0 | The WITH clause is not supported with EXECUTE statements in %S_MSG. |
12342 | 15 | 0 | The EXECUTE statement in %S_MSG only supports executing natively compiled modules. |
12343 | 16 | 0 | TRIGGER_NESTLEVEL only supports zero or one argument in %S_MSG. |
12344 | 16 | 0 | Only natively compiled modules can be used with %S_MSG. |
12345 | 16 | 0 | Max length data types are not supported as the return type of a natively compiled user defined function. |
12346 | 16 | 0 | Max length defaults are not supported with %S_MSG. |
12347 | 16 | 0 | Max length parameters to user defined functions are not supported in %S_MSG. |
12348 | 16 | 0 | Max length literals not supported in %S_MSG. |
12349 | 16 | 0 | Operation not supported for memory optimized tables having columnstore index. |
12350 | 15 | 0 | DML operations targeting table-valued functions are not supported with %S_MSG. |
12351 | 15 | 0 | Only natively compiled functions can be called with the EXECUTE from inside a natively compiled function. |
12352 | 15 | 0 | System stored procedures that cause schema changes to %S_MSG are not supported inside user transactions. |
12353 | 15 | 0 | Computed columns in indexes on memory optimized tables must be declared as PERSISTED. |
12354 | 15 | 0 | The function %ls with an argument in a Japanese_140 collation is currently not supported with %S_MSG. |
12355 | 15 | 0 | The persistence of a computed column in a memory optimized table cannot be altered. Drop and re-create the column with the desired persistence. |
12401 | 15 | 0 | The %S_MSG option '%S_MSG' was specified more than once. Each option can be specified only once. |
12402 | 11 | 0 | Query with provided query_id (%ld) is not found in the Query Store for database (%ld). Check the query_id value and rerun the command. |
12403 | 11 | 0 | Query plan with provided plan_id (%ld) is not found in the Query Store for database (%ld). Check the plan_id value and rerun the command. |
12404 | 16 | 0 | The command failed because the query store is not in read-write mode for database (%ld). Make sure that the query store is in read-write mode and rerun the command. |
12405 | 16 | 0 | The command failed because the query store is not enabled for database (%ld). Make sure that the query store is enabled for the database and rerun the command. |
12406 | 11 | 0 | Query plan with provided plan_id (%ld) is not found in the Query Store for query (%ld). Check the plan_id value and rerun the command. |
12407 | 18 | 0 | The global instance of the the Query Store Manager is not available. |
12408 | 16 | 0 | An operation to read/write to the Query Store failed. Check the error logs to correct the source of the read/write failure |
12409 | 17 | 0 | Query Store cannot create system task |
12410 | 23 | 0 | Cannot load the Query Store metadata. Try turning the Query Store on manually, or contact customer support to get this addressed. |
12411 | 18 | 0 | Cannot load forced plan from the Query Store |
12412 | 16 | 0 | Internal table access error: failed to access the Query Store internal table with HRESULT: 0x%x. |
12413 | 16 | 0 | Cannot process statement SQL handle. Try querying the sys.query_store_query_text view instead. |
12414 | 16 | 0 | Failed to initialize Query Store for use, so user request cannot be executed. |
12415 | 16 | 0 | Failed to add query to Query Store for database ID %d. |
12417 | 15 | 0 | Only one Query Store option can be given in ALTER DATABASE statement. |
12418 | 16 | 0 | Mutually incompatible options for both database state change and for Query Store given in ALTER DATABASE statement. |
12419 | 16 | 0 | The command failed because Query Store is disabled on the server or database you are using. Contact customer support to get this addressed. |
12420 | 16 | 0 | Cannot perform action because Query Store is not started up for database %.*ls. |
12421 | 14 | 0 | User does not have necessary permissions to execute Query Store stored procedure. |
12422 | 16 | 0 | Query Store interval length could not be changed because there is at least one existing runtime statistics interval set in the future. |
12423 | 16 | 0 | An operation to read/write to the Query Store failed. Partition or delete data, drop indexes, or consult the documentation for possible resolutions. |
12425 | 16 | 0 | Query with provided query id (%ld) cannot be deleted since it has active forcing policy. |
12426 | 16 | 0 | Plan with provided plan id (%ld) cannot be deleted since it has active forcing policy. |
12427 | 16 | 0 | Cannot perform operation on Query Store while it is enabled. Please turn off Query Store for the database and try again. |
12428 | 16 | 0 | The Query Store in database %.*ls is missing internal table %.*ls, possibly due to schema or catalog inconsistency. |
12429 | 16 | 0 | The Query Store in database %.*ls has an invalid structure for internal table %.*ls, possibly due to schema or catalog inconsistency. |
12430 | 16 | 0 | The specified Query Store action is not supported in stored procedure '%.*ls'. |
12431 | 16 | 0 | Query Store stored procedure '%.*ls' could not acquire an update lock over the database. |
12432 | 16 | 0 | Query Store Interval length cannot be changed because an invalid value was provided. Please try again with a valid value (1, 5, 10, 15, 30 & 60). |
12433 | 16 | 0 | Operation failed because Query Store %.*ls is disabled on the server or database you are using. Contact customer support to get this addressed. |
12434 | 16 | 0 | The Query Store in database %.*ls is invalid, possibly due to schema or catalog inconsistency. |
12435 | 16 | 0 | The Query Store in database %.*ls has an invalid structure for internal table %.*ls column %.*ls, possibly due to schema or catalog inconsistency. |
12436 | 17 | 0 | Query Store global Resource Group cannot be determined. |
12437 | 17 | 0 | Query Store global Resource Group cannot be determined. |
12438 | 16 | 0 | Cannot perform action because Query Store cannot be enabled on system database %.*ls. |
12439 | 10 | 1 | Setting database option query_store %ls to %lu for database '%.*ls'. |
12440 | 10 | 1 | Setting database option query_store %ls to %ls for database '%.*ls'. |
12441 | 10 | 0 | Query store is initializing.This is an informational message only; no user action is required. |
12442 | 17 | 0 | Query store flush failed due to internal error. |
12443 | 16 | 1 | Query store cannot set default settings. |
12444 | 16 | 0 | Query plan with plan_id (%ld) cannot be forced for query with query_id (%ld) as plan forcing is not supported for natively compiled plans. |
12445 | 16 | 0 | Cannot set Query Store max_storage_size_mb to %lu. The maximum allowed limit is %lu MB. |
12446 | 16 | 0 | Query Store stored procedure is not available on readable secondary replica. |
12447 | 16 | 0 | Query plan with plan_id (%ld) cannot be forced for query with query_id (%ld) as plan forcing is not supported for this type of statement. |
12449 | 16 | 0 | Query plan cannot be forced for this query as plan forcing is not supported for resumable index builds. |
12500 | 16 | 0 | SELECT INTO not allowed in the CTAS statement. |
12501 | 16 | 0 | Different number of columns in CREATE TABLE and SELECT query. |
12502 | 16 | 0 | Data types cannot be defined using CREATE TABLE AS SELECT syntax. |
12503 | 15 | 0 | Specifying schema elements in the CREATE SCHEMA statement is not supported. |
12504 | 16 | 0 | Distribution column '%.*ls' must be implictly or explictly specified in the insert select query as the target table '%.*ls' is a hash distributed table. |
12600 | 16 | 0 | DBCC CLONEDATABASE is not allowed on this server. |
12601 | 16 | 0 | DBCC CLONEDATABASE is not allowed within a transaction. |
12602 | 16 | 0 | DBCC CLONEDATABASE cannot be executed through MARS connection. |
12603 | 16 | 0 | DBCC CLONEDATABASE does not support cloning system databases. |
12604 | 16 | 0 | Database cannot be read. Check if the database is in offline or suspect mode. |
12605 | 16 | 0 | Failed to create snapshot database. |
12606 | 16 | 0 | Failed to set snapshot database name. |
12607 | 16 | 0 | Specified clone database name '%.*ls' is too long. |
12608 | 16 | 0 | Specified clone database name '%.*ls' already exists. |
12609 | 16 | 0 | Failed to get file attributes. |
12610 | 16 | 0 | Failed to update database registration. |
12611 | 16 | 0 | Failed to get database registration attributes. |
12612 | 16 | 0 | Failed to sync boot page with database registration. |
12613 | 16 | 0 | Too many files or file groups to clone database. |
12614 | 16 | 0 | Failed to get collation name. |
12615 | 16 | 0 | Failed to get database properties. |
12616 | 16 | 0 | Failed to drop partially created cloned database. |
12617 | 16 | 0 | File path of the database is not supported. |
12618 | 16 | 0 | The database has too many objects. |
12619 | 16 | 0 | The database has too long file path to create clone. |
12620 | 10 | 0 | Database cloning for '%.*ls' has started with target as '%.*ls'. |
12621 | 10 | 0 | Database '%.*ls' is a cloned database. A cloned database should be used for diagnostic purposes only and is not supported for use in a production environment. |
12622 | 10 | 0 | Database cloning for '%.*ls' has finished. Cloned database is '%.*ls'. |
12701 | 16 | 0 | Failed to lock external data source object (EDS name: %.*ls). Lock Mode: %.*ls. |
12702 | 16 | 0 | Failed to lock external data source manager. Lock Mode: %.*ls. |
12703 | 16 | 0 | Referenced external data source "%ls" not found. |
12704 | 16 | 0 | Bad or inaccessible location specified in external data source "%ls". |
12705 | 16 | 0 | Referenced external data source "%ls" type is "%ls". Please use BLOB_STORAGE type to reference Azure Blob Storage locations. |
12800 | 16 | 0 | The reference to temp table name '%.*ls' is ambiguous and cannot be resolved. Use either '%.*ls' or '%.*ls'. |
12801 | 16 | 0 | The reference to cursor name '%.*ls' is ambiguous and cannot be resolved. Possible candidates are '%.*ls' and '%.*ls'. |
12803 | 16 | 0 | Containment cannot be enabled for database '%.*ls' because it is a system database. |
12804 | 16 | 0 | 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 | 0 | Index name '%.*ls' is too long. Maximum length for temp table index name is %d characters. |
12807 | 16 | 0 | The option '%.*ls' cannot be set on non-contained database. |
12808 | 16 | 0 | The option '%.*ls' cannot be set on a database while containment is being set to NONE. |
12809 | 16 | 0 | You must remove all users with password before setting the containment property to NONE. |
12810 | 16 | 0 | The option '%.*ls' was specified multiple times. |
12811 | 16 | 0 | The user options for the instance must be set to 0 in order to %S_MSG a contained database. |
12813 | 16 | 0 | 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 | 0 | The object referenced as '%.*ls' resolves differently in the target metadata collation '%.*ls' than in the current metadata collation '%.*ls'. |
12815 | 16 | 0 | The column referenced as '%.*ls' resolves differently in the target metadata collation '%.*ls' than in the current metadata collation '%.*ls'. |
12816 | 16 | 0 | 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 | 0 | 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 | 1 | 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 | 0 | sp_migrate_user_to_contained cannot be used in a non-contained database (a database with CONTAINMENT set to NONE). |
12820 | 16 | 0 | 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 | 0 | sp_migrate_user_to_contained cannot be used on a user used in the EXECUTE AS clause of a signed module. |
12822 | 16 | 0 | sp_migrate_user_to_contained cannot be used to copy a password to an old hash algorithm. |
12823 | 16 | 0 | sp_migrate_user_to_contained can not find the login for user '%.*ls'. |
12824 | 16 | 0 | 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 | 0 | The database cannot be contained; this functionality is not available in the current edition of SQL Server. |
12826 | 16 | 1 | 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 | 0 | 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 | 0 | 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 contained databases. |
12829 | 16 | 0 | 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 databases. |
12830 | 16 | 0 | The sp_configure 'user options' setting must be zero if the Database Engine has contained databases. |
12831 | 16 | 0 | 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 | 1 | 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 differs from the collation used in a non-contained database. |
12833 | 16 | 1 | 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 '%.*ls', which differs from the collation used in a non-contained database. |
12834 | 16 | 1 | 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 '%.*ls', which differs from the collation used in a non-contained database. |
12835 | 10 | 1 | 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 to '%.*ls', which differs from the collation used in a non-contained database. |
12836 | 16 | 1 | 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 | 1 | 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 | 1 | 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 | 1 | 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 | 0 | CREATE DATABASE failed. Recollating the database failed while creating the partially contained database '%.*ls', with a default data collation of '%.*ls'. |
12841 | 16 | 0 | ALTER DATABASE failed. Recollating the database failed while altering the database '%.*ls' to containment='%ls'. |
12842 | 16 | 0 | The COLLATE CATALOG_DEFAULT clause cannot be used in a constraint, computed column, index filter expression, or any schema-bound object. |
12843 | 16 | 1 | 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. |
12844 | 16 | 1 | ALTER DATABASE statement failed; this functionality is not available in the current edition of SQL Server. |
12980 | 16 | 0 | Supply either %s or %s to identify the log entries. |
12981 | 16 | 0 | You must specify %s when creating a subplan. |
12982 | 16 | 0 | Supply either %s or %s to identify the plan or sub-plan to be run. |