错误码目录 / Microsoft SQL Server
Microsoft SQL Server 错误码目录 · 第 8 / 18 页
本页收录 Microsoft SQL Server 的 17,993 条错误码知识条目,每条均可打开独立详情页,包含错误说明、编号信息、官方文档与公开资料。
- 13502 — System-versioned table cannot have more than one 'GENERATED ALWAYS AS ROW START' column.
- 13503 — System-versioned table cannot have more than one 'GENERATED ALWAYS AS ROW END' column.
- 13504 — Temporal 'GENERATED ALWAYS AS ROW START' column definition missing.
- 13505 — Temporal 'GENERATED ALWAYS AS ROW END' column definition missing.
- 13506 — System-versioned table SYSTEM_TIME period definition start column name not matching 'GENERATED ALWAYS AS ROW START' column name.
- 13507 — System-versioned table SYSTEM_TIME period definition end column name not matching 'GENERATED ALWAYS AS ROW END' column name.
- 13508 — System-versioned table cannot have more than one SYSTEM_TIME period definition.
- 13509 — Cannot create generated always column when SYSTEM_TIME period is not defined.
- 13510 — Cannot set SYSTEM_VERSIONING to ON when SYSTEM_TIME period is not defined.
- 13511 — Specified object '%.*ls' cannot be used as history table.
- 13512 — You cannot specify SYSTEM_VERSIONING clause more than once.
- 13513 — SYSTEM_TIME period columns cannot have different datatype precision.
- 13514 — History table '%.*ls' is already in use.
- 13515 — Setting SYSTEM_VERSIONING to ON failed because history table '%.*ls' has custom unique keys defined. Consider dropping all unique keys and trying agai…
- 13516 — Setting SYSTEM_VERSIONING to ON failed because history table '%.*ls' has foreign keys defined. Consider dropping all foreign keys and trying again.
- 13517 — Setting SYSTEM_VERSIONING to ON failed because history table '%.*ls' has table or column constraints defined. Consider dropping all table and column c…
- 13518 — Setting SYSTEM_VERSIONING to ON failed because history table '%.*ls' has IDENTITY column specification. Consider dropping all IDENTITY column specific…
- 13519 — Setting SYSTEM_VERSIONING to ON failed because history table '%.*ls' has computed column specification. Consider dropping all computed column specific…
- 13520 — Setting SYSTEM_VERSIONING to ON failed because history table '%.*ls' is not available or it is placed on a read-only file group.
- 13521 — Setting SYSTEM_VERSIONING to ON failed because history table '%.*ls' is configured for change data capture. Consider dropping this configuration and t…
- 13522 — Setting SYSTEM_VERSIONING to ON failed because history table '%.*ls' has triggers defined. Consider dropping all triggers and trying again.
- 13523 — Setting SYSTEM_VERSIONING to ON failed because table '%.*ls' has %d columns and table '%.*ls' has %d columns.
- 13524 — Setting SYSTEM_VERSIONING to ON failed because column '%.*ls' at ordinal %d in history table '%.*ls' has a different name than the column '%.*ls' at t…
- 13525 — Setting SYSTEM_VERSIONING to ON failed because column '%.*ls' has data type %s in history table '%.*ls' which is different from corresponding column t…
- 13526 — Setting SYSTEM_VERSIONING to ON failed because column '%.*ls' does not have the same collation in tables '%.*ls' and '%.*ls'.
- 13527 — Setting SYSTEM_VERSIONING to ON failed because column '%.*ls' does not have the same CLR type in tables '%.*ls' and '%.*ls'.
- 13528 — Setting SYSTEM_VERSIONING to ON failed because column '%.*ls' does not have the same ANSI trimming semantics in tables '%.*ls' and '%.*ls'.
- 13529 — Setting SYSTEM_VERSIONING to ON failed because column '%.*ls' does not have the same XML Schema Collection in tables '%.*ls' and '%.*ls'.
- 13530 — Setting SYSTEM_VERSIONING to ON failed because system column '%.*ls' in history table '%.*ls' corresponds to a period column in table '%.*ls' and cann…
- 13531 — Setting SYSTEM_VERSIONING to ON failed because column '%.*ls' does not have the same nullability attribute in tables '%.*ls' and '%.*ls'.
- 13532 — Setting SYSTEM_VERSIONING to ON failed because system-versioned tables cannot have FILESTREAM columns.
- 13533 — Setting SYSTEM_VERSIONING to ON failed because column '%.*ls' does not have the same sparse storage attribute in tables '%.*ls' and '%.*ls'.
- 13534 — Setting SYSTEM_VERSIONING to ON failed because column '%.*ls' does not have the same column set property in tables '%.*ls' and '%.*ls'.
- 13535 — Data modification failed on system-versioned table '%.*ls' because transaction time was earlier than period start time for affected records.
- 13536 — Cannot insert an explicit value into a GENERATED ALWAYS column in table '%.*ls'. Use INSERT with a column list to exclude the GENERATED ALWAYS column,…
- 13537 — Cannot update GENERATED ALWAYS columns in table '%.*ls'.
- 13538 — You do not have the required permissions to complete the operation.
- 13539 — Setting SYSTEM_VERSIONING to ON failed because history table '%.*ls' is not specified in two-part name format.
- 13540 — Setting SYSTEM_VERSIONING to ON failed because table '%.*ls' contains invalid records with end of period set before start.
- 13541 — Setting SYSTEM_VERSIONING to ON failed because history table '%.*ls' contains invalid records with end of period set before start.
- 13542 — ADD PERIOD FOR SYSTEM_TIME on table '%.*ls' failed because there are open records with start of period set to a value in the future.
- 13543 — Setting SYSTEM_VERSIONING to ON failed because history table '%.*ls' contains invalid records with end of period set to a value in the future.
- 13544 — Temporal FOR SYSTEM_TIME clause can only be used with system-versioned tables. '%.*ls' is not a system-versioned table.
- 13545 — Truncate failed on table '%.*ls' because it is not a supported operation on system-versioned tables.
- 13546 — Switching out partition failed on table '%.*ls' because it is not a supported operation on system-versioned tables. Consider setting SYSTEM_VERSIONING…
- 13547 — Switching in partition failed on history table '%.*ls' because it is not a supported operation on system-versioned tables. Consider setting SYSTEM_VER…
- 13548 — Cannot alter column '%.*ls' on table '%.*ls' because it is not a supported operation on system-versioned temporal tables.
- 13549 — Setting FILESTREAM ON failed on table '%.*ls' because it is not a supported operation on system-versioned temporal tables.
- 13550 — Add column operation failed on table '%.*ls' because it is not a supported operation on system-versioned temporal tables.
- 13551 — Drop column operation failed on table '%.*ls' because it is not a supported operation on system-versioned temporal tables.
- 13552 — Drop table operation failed on table '%.*ls' because it is not a supported operation on system-versioned temporal tables.
- 13553 — System versioned temporal table '%.*ls' must have primary key defined.
- 13554 — Memory-optimized table '%.*ls' cannot contain system-time PERIOD.
- 13555 — System versioned temporal table '%.*ls' cannot have FILESTREAM columns.
- 13556 — Table '%.*ls' is a FileTable. System versioning cannot be used on FileTables.
- 13557 — Cannot drop PRIMARY KEY constraint from a system-versioned temporal table '%.*ls'.
- 13558 — Cannot add PRIMARY KEY constraint to a temporal history table '%.*ls'.
- 13559 — Cannot insert rows in a temporal history table '%.*ls'.
- 13560 — Cannot delete rows from a temporal history table '%.*ls'.
- 13561 — Cannot update rows in a temporal history table '%.*ls'.
- 13562 — Cannot perform MERGE operation on temporal history table '%.*ls'.
- 13563 — Enabling Change Tracking for a temporal history table '%.*ls' is not allowed.
- 13564 — Adding CHECK constraint to a temporal history table '%.*ls' is not allowed.
- 13565 — Foreign key '%.*ls' is not valid. A temporal history table cannot be used in a foreign key definition.
- 13566 — Temporal table '%.*ls' is already in use.
- 13567 — Temporal history table '%.*ls' cannot be created in a 'tempdb' database.
- 13568 — System-versioned temporal table '%.*ls' cannot be created in a 'tempdb' database.
- 13569 — Cannot create a trigger on a system-versioned temporal table '%.*ls'.
- 13570 — The use of replication is not supported with system-versioned temporal table '%s'
- 13571 — Enabling Change Data Capture for a temporal history table '%ls' is not allowed.
- 13572 — Creating table variables containing PERIOD is not allowed.
- 13573 — Setting SYSTEM_VERSIONING to ON failed because history table '%.*ls' contains overlapping records.
- 13574 — Setting SYSTEM_VERSIONING to ON failed because temporal history table '%.*ls' contains SYSTEM_TIME period.
- 13575 — ADD PERIOD FOR SYSTEM_TIME failed because table '%.*ls' contains records where end of period is not equal to MAX datetime.
- 13576 — DML operations are not allowed because system-versioned temporal table '%.*ls' is in read-only mode.
- 13577 — ALTER TABLE SWITCH statement failed on table '%.*ls' because target table has SYSTEM_TIME PERIOD while source table does not have it.
- 13578 — ALTER TABLE SWITCH statement failed on table '%.*ls' because target and source tables have different SYSTEM_TIME PERIOD definitions.
- 13579 — Setting SYSTEM_VERSIONING to ON failed because column '%.*ls' does not use identical encryption in tables '%.*ls' and '%.*ls'.
- 13580 — Setting SYSTEM_VERSIONING to ON failed because history table '%.*ls' has ROWGUID column specification. Consider dropping all ROWGUID column specificat…
- 13581 — Setting SYSTEM_VERSIONING to ON failed because column '%.*ls' does not have the same masking functions in tables '%.*ls' and '%.*ls'.
- 13582 — Setting SYSTEM_VERSIONING to ON failed because table '%.*ls' has a FOREIGN KEY with cascading DELETE or UPDATE.
- 13583 — Cannot add UNIQUE KEY constraint to a temporal history table '%.*ls'.
- 13584 — Flush has not been executed for table because appropriate lock could not be obtained or it does not exist anymore.
- 13585 — Computed column is defined with a user-defined function which is not allowed with system-versioned table '%.*ls' because it performs user or system da…
- 13586 — Temporal FOR SYSTEM_TIME clause cannot be used on remote data source '%.*ls'.
- 13587 — Period column '%.*ls' in a system-versioned temporal table cannot be nullable.
- 13588 — Column '%.*ls' in table '%.*ls' cannot be dropped because it is a part of period definition.
- 13589 — Column '%.*ls' in table '%.*ls' cannot be specified as 'GENERATED ALWAYS' in ALTER COLUMN statement.
- 13590 — Temporal FOR SYSTEM_TIME clause can only be set once per temporal table. '%.*ls' has more than one temporal FOR SYSTEM_TIME clause.
- 13591 — SYSTEM_VERSIONING is not turned ON for table '%.*ls'.
- 13592 — Cannot drop SYSTEM_TIME period from table '%.*ls' when SYSTEM_VERSIONING is ON.
- 13593 — SYSTEM_TIME period cannot be dropped from table '%.*ls', because SYSTEM_TIME period does not exist.
- 13594 — Table '%.*ls' does not contain SYSTEM_TIME period '%.*ls'.
- 13595 — Temporal history table name '%.*ls' is not correct for current table '%.*ls'.
- 13596 — SYSTEM_VERSIONING is already turned ON for table '%.*ls'.
- 13597 — Temporal SYSTEM_TIME period is already defined on table '%.*ls'.
- 13598 — Temporal SYSTEM_TIME period cannot be defined on history table '%.*ls'.
- 13599 — Period column '%.*ls' in a system-versioned temporal table cannot be altered.
- 13600 — FOR JSON AUTO requires at least one table for generating JSON objects. Use FOR JSON PATH or add a FROM clause with a table name.
- 13601 — Property '%.*ls' cannot be generated in JSON output due to a conflict with another column name or alias. Use different names and aliases for each colu…
- 13602 — The FOR JSON clause is not allowed in a %ls statement.
- 13603 — Property '%.*ls' cannot be generated in JSON output due to invalid character in the column name or alias. Column name or alias that contains '..', sta…
- 13604 — FOR JSON cannot serialize CLR objects. Cast CLR types explicitly into one of the supported types in FOR JSON queries.
- 13605 — Column expressions and data sources without names or aliases cannot be formatted as JSON text using FOR JSON clause. Add alias to the unnamed column o…
- 13606 — JSON text that has more than 128 nesting levels cannot be parsed.
- 13607 — JSON path is not properly formatted. Unexpected character '%lc' is found at position %d.
- 13608 — Property cannot be found on the specified JSON path.
- 13609 — JSON text is not properly formatted. Unexpected character '%lc' is found at position %d.
- 13610 — The argument %d of the "%.*ls" must be a string literal.
- 13611 — Value referenced by JSON path is not an array or object and cannot be opened with OPENJSON.
- 13612 — Cannot convert a string value found in the JSON text to binary value because it is not Base64 encoded.
- 13613 — Base64 encoded string cannot be converted to binary value. Binary data would be truncated.
- 13614 — TEXT, NTEXT, SQL_VARIANT and IMAGE types cannot be used as column types in OPENJSON function with explicit schema. These types are not supported in WI…
- 13615 — OPENJSON function cannot convert value found in the JSON text to sql_variant data type. The value found in JSON text would be truncated.
- 13616 — CLR types cannot be used as column types in OPENJSON function with explicit schema. CLR types are not supported in WITH clause.
- 13617 — Table types cannot be used as column types in OPENJSON function with explicit schema. This type is not supported in WITH clause.
- 13618 — AS JSON option can be specified only for column of nvarchar(max) type in WITH clause.
- 13619 — Unsupported JSON path found in argument %d of JSON_MODIFY.
- 13620 — ROOT option and WITHOUT_ARRAY_WRAPPER option cannot be used together in FOR JSON. Remove one of these options.
- 13621 — Array cannot be found in the specified JSON path.
- 13622 — An invalid value was specified for argument %d.
- 13623 — Scalar value cannot be found in the specified JSON path.
- 13624 — Object or array cannot be found in the specified JSON path.
- 13625 — String value in the specified JSON path would be truncated.
- 13626 — Openjson cannot have more than %d columns in with clause.
- 13627 — Column type %ls cannot be used in the OPENJSON column that returns '$.sql:identity()' value.
- 13628 — System error.
- 13629 — System error.
- 13630 — System error.
- 13631 — System error.
- 13632 — System error.
- 13633 — System error: '%ls'.
- 13634 — System error: '%ls'.
- 13635 — System error.
- 13636 — System error.
- 13637 — System error.
- 13638 — User error : Name parameter value in '%ls' cannot be null
- 13639 — System error.
- 13640 — System error.
- 13641 — There is not enough resources to perform the operation. One or more JSON character strings in the query exceeds the supported limit for the JSON type.
- 13642 — Encountered an unsupported version of the JSON type. Please run DBCC CHECKTABLE with EXTENDED_LOGICAL_CHECKS to identify the rows. The remedy is to de…
- 13643 — Encountered corrupted JSON type. Please run DBCC CHECKTABLE with EXTENDED_LOGICAL_CHECKS to identify the rows. The remedy is to delete the rows and in…
- 13644 — String value length exceeds maximum %d bytes in JSON type.
- 13645 — Nested level of JSON document exceeds limit %d.
- 13646 — Key string length exceeds limit %d bytes in JSON type.
- 13647 — Number of items in one object/array exceeds limit %d in JSON type.
- 13648 — Length of numeric string around '%.*ls' exceeds limit %d characters in JSON type.
- 13649 — Number of unique keys exceeds limit %d in JSON type.
- 13650 — JSON path exceeds limit of %d bytes.
- 13654 — JSON column(s) cannot be natively imported through BULK INSERT or OPENROWSET(BULK) statement. Please use a format file to explicitly specify the type …
- 13655 — JSON data type is not supported in distributed queries. Remote object '%.*ls' has JSON column(s).
- 13656 — JSON data type cannot be used when its feature switch is off.
- 13657 — Cannot create alias types from a JSON data type.
- 13658 — JSON data type cannot be used in OpenJson function.
- 13659 — Index %d provided at position %d is not within the array of size %d.
- 13660 — %s not yet supported for advanced JSON array accessors.
- 13661 — JSON data type is not supported in CDC tracked table.
- 13662 — JSON data type is not supported in transactional replication.
- 13663 — JSON data type is not supported in generic replication features.
- 13664 — JSON path not valid for JSON index.
- 13665 — %s not yet supported for JSON native data type.
- 13666 — %s does not support CLR type as parameters
- 13667 — JSON aggregates do not support order-by within group when specified with grouping sets, cubes and rollups. Try your query without order-by within grou…
- 13668 — JSON_QUERY using WITH ARRAY WRAPPER will cause a buffer overflow. Please cast the document to a LOB.
- 13670 — Input JSON is not a valid Vector : '%ls'.
- 13671 — Given Vector size is not supported. Maximum allowed size '%ld'.
- 13672 — Table '%.*ls' needs to have a clustered primary key with less than %d columns in it in order to create a JSON index on it.
- 13674 — DROP JSON INDEX does not support any options.
- 13675 — Cannot create a JSON index on temp objects. '%.*ls' is identified as a temp object.
- 13676 — Internal error occurred while creating the JSON index. Please run DBCC CHECKCATALOG and retry if it does not report any error. Please contact support …
- 13677 — Failed to create internal table for the JSON index.
- 13678 — Could not create the JSON index on object '%.*ls' because that object is not a table. Create the index on the base table column.
- 13679 — '%.*ls' is not a valid JSON index name because it starts with '%c' character. JSON index name should not start with '#' or '@'
- 13680 — Column '%.*ls' on table '%.*ls' is not of JSON data type, which is required to create a JSON index on it.
- 13681 — A JSON index '%.*ls' already exists on column '%.*ls' on table '%.*ls', and multiple JSON indexes per column are not allowed.
- 13682 — Cannot create JSON index '%.*ls' on table '%.*ls', column '%.*ls', because the column is computed.
- 13683 — Invalid JSON paths in JSON index.
- 13684 — String conversion from UTF-8 to UTF-16 failed.
- 13685 — A JSON index '%.*ls' cannot be found on column '%.*ls' on table '%.*ls'.
- 13686 — Json_Contains matches pattern as LIKE. The pattern should be no longer than 4000 characters.
- 13687 — JSON data type is not supported in merge replication.
- 13688 — One or more of the specified ALTER INDEX options is invalid for a JSON index.
- 13689 — DATA_COMPRESSION is not compatible with JSON index '%.*ls'. Please drop it and recreate it.
- 13690 — JSON index '%.*ls' cannot be rebuilt. Drop and recreate it.
- 13691 — The JSON data type is not supported in a data mask.
- 13692 — The comparison_mode argument of JSON_CONTAINS must be 0 or 1.
- 13693 — ALTER INDEX SET OPTIONS for JSON index is disabled.
- 13694 — JSON Schema is not valid.
- 13695 — JSON Schema keyword is not supported. %.*ls
- 13696 — JSON numeric value '%.*ls' is out of range for the numeric(38,10) representation used by the JSON type.
- 13697 — JSON text is empty.
- 13698 — DBCC DBREINDEX cannot be used on JSON indexes. Use ALTER INDEX with the REBUILD option instead.
- 13699 — The search_value argument of JSON_CONTAINS cannot be NULL.
- 13701 — System-versioned table schema modification failed because history table '%.*ls' has custom unique keys defined. Consider dropping all unique keys and …
- 13702 — System-versioned table schema modification failed because history table '%.*ls' has foreign keys defined. Consider dropping all foreign keys and tryin…
- 13703 — System-versioned table schema modification failed because history table '%.*ls' has table or column constraints defined. Consider dropping all table a…
- 13704 — System-versioned table schema modification failed because history table '%.*ls' has IDENTITY column specification. Consider dropping all IDENTITY colu…
- 13705 — System-versioned table schema modification failed because history table '%.*ls' has computed column specification. Consider dropping all computed colu…
- 13706 — System-versioned table schema modification failed because history table '%.*ls' is not available or it is placed on a read-only file group.
- 13707 — System-versioned table schema modification failed because history table '%.*ls' is configured for change data capture. Consider dropping this configur…
- 13708 — System-versioned table schema modification failed because history table '%.*ls' has triggers defined. Consider dropping all triggers and trying again.
- 13709 — System-versioned table schema modification failed because table '%.*ls' has %d columns and table '%.*ls' has %d columns.
- 13710 — System-versioned table schema modification failed because column '%.*ls' at ordinal %d in history table '%.*ls' has a different name than the column '…
- 13711 — System-versioned table schema modification failed because column '%.*ls' has data type %s in history table '%.*ls' which is different from correspondi…
- 13712 — System-versioned table schema modification failed because column '%.*ls' does not have the same collation in tables '%.*ls' and '%.*ls'.
- 13713 — System-versioned table schema modification failed because column '%.*ls' does not have the same CLR type in tables '%.*ls' and '%.*ls'.
- 13714 — System-versioned table schema modification failed because column '%.*ls' does not have the same ANSI trimming semantics in tables '%.*ls' and '%.*ls'.
- 13715 — System-versioned table schema modification failed because column '%.*ls' does not have the same XML Schema Collection in tables '%.*ls' and '%.*ls'.
- 13716 — System-versioned table schema modification failed because system column '%.*ls' in history table '%.*ls' corresponds to a period column in table '%.*l…
- 13717 — System-versioned table schema modification failed because column '%.*ls' does not have the same nullability attribute in tables '%.*ls' and '%.*ls'.
- 13718 — System-versioned table schema modification failed because system-versioned tables cannot have FILESTREAM columns.
- 13719 — System-versioned table schema modification failed because column '%.*ls' does not have the same sparse storage attribute in tables '%.*ls' and '%.*ls'…
- 13720 — System-versioned table schema modification failed because column '%.*ls' does not have the same column set property in tables '%.*ls' and '%.*ls'.
- 13721 — System-versioned table schema modification failed because temporal history table '%.*ls' contains SYSTEM_TIME period.
- 13722 — Computed column is defined with a user-defined function which is not allowed with system-versioned table '%.*ls' because it performs user or system da…
- 13723 — System-versioned table schema modification failed because history table '%.*ls' has ROWGUID column specification. Consider dropping all ROWGUID column…
- 13724 — System-versioned table schema modification failed because adding computed column while system-versioning is ON is not supported.
- 13725 — System-versioned table schema modification failed because column '%.*ls' does not have the same masking functions in tables '%.*ls' and '%.*ls'.
- 13726 — Setting SYSTEM_VERSIONING to ON failed because history table '%.*ls' is referenced by one or more BLOCK security predicates. Consider removing the BLO…
- 13727 — Temporal 'GENERATED ALWAYS AS %ls' column '%.*ls' has invalid data type.
- 13728 — Temporal 'GENERATED ALWAYS AS %ls' column '%.*ls' cannot be nullable.
- 13729 — Temporal 'GENERATED ALWAYS' column '%.*ls' cannot be altered.
- 13730 — Setting SYSTEM_VERSIONING to ON failed because column '%.*ls' in history table '%.*ls' corresponds to a generated always column in table '%.*ls' and c…
- 13731 — System-versioned table schema modification failed because column '%.*ls' in history table '%.*ls' corresponds to a generated always column in table '%…
- 13732 — Temporal 'GENERATED ALWAYS AS %ls' column '%.*ls' has invalid data length.
- 13733 — Temporal table cannot have more than one 'GENERATED ALWAYS AS %ls' column.
- 13734 — System-versioned table schema modification failed because online alter is not supported on system-versioned memory optimized table '%.*ls'.
- 13735 — Cannot alter HIDDEN attribute on column '%.*ls' in table '%.*ls' because this column is not a generated always column.
- 13736 — ALTER TABLE SWITCH statement failed on table '%.*ls' because column '%.*ls' does not have the same GENERATED ALWAYS attribute in target and source tab…
- 13738 — History table '%.*ls' can not be memory optimized table.
- 13739 — Memory optimized temporal table '%.*ls' must be created with DURABILITY set to SCHEMA_AND_DATA.
- 13740 — The row size limit of %d bytes for memory optimized system versioned tables has been exceeded. Please simplify the table definition.
- 13741 — Cannot create UNIQUE index on temporal history table '%.*ls'.
- 13742 — Table '%.*ls' contains records where 'GENERATED ALWAYS AS %ls' is not equal to %ls.
- 13743 — %ld is not a valid value for system versioning history retention period.
- 13744 — '%.*ls' is not a valid history retention period unit for system versioning.
- 13745 — System-versioned table schema modification failed because column '%.*ls' does not use identical encryption in tables '%.*ls' and '%.*ls'.
- 13746 — '%.*ls' is not a system versioned temporal table.
- 13747 — Cannot apply history cleanup on table '%.*ls' because it has infinite retention period.
- 13748 — Setting SYSTEM_VERSIONING to ON failed because table '%.*ls' exceeds the maximum of 1023 columns.
- 13749 — The period of %ld %S_MSG is too big for system versioning history retention.
- 13750 — Temporal period column '%.*ls' does not exist.
- 13751 — Temporal application time column '%.*ls' has invalid data type. Allowed data types are datetime2, smalldatetime, datetimeoffset, date and datetime.
- 13752 — Column '%.*ls' must be defined as NOT NULL in order to be used in a temporal application time period.
- 13753 — Temporal period columns cannot have different data types.
- 13754 — Temporal period columns cannot have different data type precision.
- 13755 — Temporal period '%.*ls' has the same start and end time column.
- 13756 — Column '%.*ls' is used in the temporal period '%.*ls' and cannot be explicitly placed in the key list of a constraint where that same period without o…
- 13757 — Temporal table '%.*ls' already has history table defined. Consider dropping system_versioning first if you want to use different history table.
- 13758 — Cannot define foreign key constraint '%.*ls' with cascaded DELETE or UPDATE on table '%.*ls' because table is system-versioned.
- 13759 — Renaming a column failed on history table '%ls' because it is not a supported operation on system-versioned tables. Consider setting SYSTEM_VERSIONING…
- 13760 — Accessing history table for memory optimized temporal table using the SERIALIZABLE isolation level is not supported while SYSTEM_VERSIONING is ON.
- 13761 — The hint '%.*ls' is not supported with history table for memory optimized temporal table while SYSTEM_VERSIONING is ON.
- 13762 — Cannot alter temporal table '%.*ls' because this operation is currently not available.
- 13763 — Cannot query temporal table '%.*ls' because this operation is currently not available.
- 13764 — Online alter column is not supported for system-versioned temporal table '%.*ls'.
- 13765 — Setting finite retention period failed on system-versioned temporal table '%.*ls' because the history table '%.*ls' does not contain required clustere…
- 13766 — Cannot drop the clustered index '%.*ls' because it is being used for automatic cleanup of aged data. Consider setting HISTORY_RETENTION_PERIOD to INFI…
- 13767 — The clustered index '%.*ls' is being used for automatic cleanup of aged data, and can be converted to either a clustered columnstore or B-tree index s…
- 13768 — Retention cleanup of history table for a temporal table (database id %lu, table id %ld) has not been executed. Either the cleanup is disabled on the d…
- 13769 — Setting SYSTEM_VERSIONING to ON failed for table '%.*ls' because '%.*ls' with REMOTE_DATA_ARCHIVE enabled cannot be used as a history table when a fin…
- 13770 — Setting finite retention period failed on system-versioned temporal table '%.*ls' because REMOTE_DATA_ARCHIVE is enabled on the corresponding history …
- 13771 — Setting finite retention period failed on system-versioned temporal table '%.*ls' because corresponding history table '%.*ls' has both clustered colum…
- 13772 — Cannot create non-clustered index on temporal history table '%.*ls' since it has finite retention period and clustered columnstore index defined.
- 13773 — Clustered column store temporal retention cleanup attempted on non-clustered column store table '%.*ls'.
- 13774 — Setting SYSTEM_VERSIONING to ON failed because table '%.*ls' has INSTEAD OF triggers defined. Consider dropping INSTEAD OF triggers and trying again.
- 13775 — System-versioned table schema modification failed because table '%.*ls' has INSTEAD OF triggers defined. Consider dropping INSTEAD OF triggers and try…
- 13776 — Table '%.*ls' does not exist or you do not have the required permissions to complete the operation.
- 13777 — Stored procedure 'sp_cleanup_temporal_history' is temporarily disabled. Please contact customer support for more information.
- 13778 — The only allowed ALTER TABLE operations on temporal in-memory history table '%.*ls' are ADD INDEX, DROP INDEX and ALTER INDEX.
- 13779 — Defining a column store index on temporal in-memory history table '%.*ls' is not supported.
- 13780 — Setting finite retention period failed on system-versioned temporal table '%.*ls' beacause the history table '%.*ls' is clustered column store that co…
- 13781 — Wrong type for column '%.*ls': the system-versioned temporal table '%.*ls' cannot contain large object columns, because it has finite retention and th…
- 13782 — Cannot create clustered column store index '%.*ls' on table '%.*ls' because it contains large object columns and is the history table of temporal tabl…
- 13783 — Data modification failed on system-versioned table '%.*ls' because column '%.*ls' cannot be output into the history table '%.*ls'.
- 13784 — Setting SYSTEM_VERSIONING to ON failed because column '%.*ls' does not have the same sensitivity classification in tables '%.*ls' and '%.*ls'.
- 13785 — System-versioned table schema modification failed because column '%.*ls' does not have the same sensitivity classification in tables '%.*ls' and '%.*l…
- 13795 — '%.*ls' does not exist, or is not a temporal application time period.
- 13796 — Temporal application time period without overlaps can be defined only on a primary key or a unique constraint.
- 13797 — Temporal application time period is already defined on table '%.*ls'.
- 13798 — A table cannot have more than one application time period definition.
- 13799 — '%.*ls' is not allowed as application time period name.
- 13800 — INSERT BULK statement does not support recompile.
- 13801 — TEXT, NTEXT, SQL_VARIANT and IMAGE types cannot be used as column types in OPENROWSET function with inline schema. These types are not supported in WI…
- 13802 — CLR types cannot be used as column types in OPENROWSET function with inline schema. These types are not supported in WITH clause.
- 13803 — Table types cannot be used as column types in OPENROWSET function with inline schema. These types are not supported in WITH clause.
- 13804 — Invalid escape character specified for bulk load. Escape character can be one single byte or Unicode character.
- 13805 — An internal error has occurred during wildcard expansion.
- 13806 — It is not possible to expand wildcards in path to provided data source.
- 13807 — Content of directory on path '%ls' cannot be listed.
- 13808 — Starting offset cannot be larger than the file size.
- 13809 — Warning: No datasets were found that match the expression '%ls'.
- 13810 — Column '%ls' is of type '%ls' which is not supported with file format '%ls'.
- 13811 — Bulk load data conversion error (truncation) for row %d, column %d (%ls) in data file %ls.
- 13812 — Bulk load data conversion error (type mismatch or invalid character for the specified codepage) for row %d, column %d (%ls) in data file %ls.
- 13813 — Bulk load data conversion error (overflow) for row %d, column %d (%ls) in data file %ls.
- 13814 — Bulk load failed: Data file %ls does not have %ls encoding.
- 13815 — Consecutive wildcard characters present in path '%ls'.
- 13816 — File/directory path '%ls' is too long. Max length of the path is nvarchar(260).
- 13817 — The bulk load failed. Unexpected NULL value in data file row %ls%I64d, column %d in data file %ls. The destination column (%ls) is defined as NOT NULL…
- 13818 — Compression type '%1ls' is not supported.
- 13819 — Error occurred while reading '%1ls' for decoding with %2ls codec.
- 13820 — Error occurred while decoding '%1ls' using %2ls codec. Codec error code: %d. Codec error message: %3ls
- 13821 — File/directory path '%ls' is too long. Max length of the path is nvarchar(1024).
- 13822 — File '%ls' cannot be opened because it does not exist or it is used by another process.
- 13823 — Query failed because credential for specified path does not exist or you do not have permissions to reference the credential.
- 13824 — Wildcard expansion operation timed out after %lu seconds.
- 13825 — Provided URL format is incorrect.
- 13826 — Provided first row exceeds row count in first split of the data file %ls. Please retry after updating first row value or by disabling splitting.
- 13827 — %ls option cannot be used with %ls format.
- 13828 — Usage of filepath function with DATA_SOURCE '%.*ls' might result in unexpected results if number of wildcards in data source LOCATION changes.
- 13829 — XML type cannot be used as column type in OPENROWSET function with inline schema. This type is not supported in WITH clause.
- 13830 — Azure Active Directory authentication to Azure Storage is not allowed in BULK INSERT/OPENROWSET.
- 13831 — Cannot parse rowset options: %ls
- 13832 — Path '%ls' has URL suffix which is not allowed.
- 13833 — Multiple paths are only allowed from the same storage account and container.
- 13834 — Bulk load data conversion error (NULL in non-nullable column) for row %ls%I64d, column %d (%ls) in %ls.
- 13835 — ERRORFILE path '%ls' must be in the same storage account as the '%ls', that has to be in private container.
- 13836 — For onelake container paths, only files in '<Workspace>/<Artifact>/Files' directory are allowed.
- 13837 — ERRORFILE path '%ls' and data path '%ls' must have the same onelake endpoint, workspace, artifact and folder.
- 13838 — Accessing storage path '%ls' using '%ls' credential is not supported
- 13839 — For InsertBulk and onelake container paths, only files in '<Path>/WarehouseSystem/BcpTemporaryData' directory are allowed.
- 13840 — Access token couldn't be fetched for storage path '%ls' as it's an unsupported URL or cause of a transient error.
- 13841 — The code page %d specified for the SINGLE_CLOB option is not supported by this server. Code page 65001 (UTF-8) is used instead.
- 13842 — The ERRORFILE path '%.*ls' is not allowed because it contains a relative path traversal ('.' or '..') component.
- 13900 — Identifier '%.*ls' in a MATCH clause could not be bound.
- 13901 — Identifier '%.*ls' in a MATCH clause is not a node table or an alias for a node table.
- 13902 — Identifier '%.*ls' in a MATCH clause is not an edge table or an alias for an edge table.
- 13903 — Edge table '%.*ls' used in more than one MATCH pattern.
- 13904 — All node and edge tables within a single MATCH clause must reside in the same database.
- 13905 — A MATCH clause may not be directly combined with other expressions using OR or NOT.
- 13906 — A MATCH clause is only permitted in a WHERE clause or in the ON clause of a GRAPH JOIN.
- 13907 — Cannot modify permissions for graph column '%.*s'.
- 13908 — Cannot access internal graph column '%.*ls'.
- 13909 — The internal graph column '%.*ls' cannot be added to an index; use pseudocolumn '%.*ls' instead.
- 13910 — Cannot create a node or edge table as memory optimized.
- 13911 — Cannot create a node or edge table as a remote data archive.
- 13912 — A node or edge table cannot be created as or altered to a temporal table.
- 13913 — Internal graph columns cannot be altered.
- 13914 — Cannot create a node or edge table as a temporary table.
- 13915 — Cannot create a node or edge table as an external table.
- 13916 — The graph column '%.*ls' cannot be used as a non-key column in an index.
- 13917 — After expanding the computed graph column '%.*ls", the index '%.*ls' on table '%.*ls' exceeds the maximum number of columns in the key list. The maxim…
- 13918 — Adding constraint to column '%.*s' of a node or edge table is not allowed.
- 13919 — Identifier '%.*ls' in a MATCH clause corresponds to a derived table. Derived tables are not supported in MATCH clauses.
- 13920 — Identifier '%.*ls' in a MATCH clause is used with a JOIN clause or APPLY operator. JOIN and APPLY are not supported with MATCH clauses.
- 13921 — JSON data for INSERT/UPDATE of graph pseudocolumn '%.*ls' is malformed.
- 13922 — Remote tables are not supported in MATCH clauses.
- 13923 — Pseudocolumn '%.*s' is invalid because it references a node or edge table that is not in the current database.
- 13924 — Select * is not permitted because it refers to a node or edge table '%.*s' which is not in the current database.
- 13925 — Cannot drop or disable index or constraint '%.*s' because the last unique index or constraint on '%.*s' cannot be dropped or disabled.
- 13926 — The use of replication is not supported for node or edge table '%ls'.
- 13927 — Change Data Capture is not supported for node or edge table '%ls'.
- 13928 — Use pseudocolumn '%.*ls' to add a constraint on a node or edge table.
- 13929 — The pseudocolumn '%.*ls' cannot be part of an index unless the index is on a node or edge table that contains that pseudocolumn.
- 13930 — Edge constraint cannot be created on table '%.*ls'. The table is not an edge table.
- 13931 — Edge constraint '%.*ls' references invalid table '%.*ls'. Table could not be found.
- 13932 — Cross-database edge constraints are not supported.
- 13933 — Edge constraint must reference node tables.
- 13934 — Could not drop node table '%.*ls' because it is referenced by an edge constraint.
- 13935 — Cannot enable edge constraint '%.*ls' as there are no online, unique, unfiltered $node_id indexes on one or more target node tables.
- 13936 — Warning: Edge constraint '%.*ls' on table '%.*ls' was disabled as a result of disabling the index '%.*ls'.
- 13937 — Cannot disable clustered index '%.*ls' on table '%.*ls'. Permission denied to disable edge constraint '%.*ls' on table '%.*ls' that references this ta…
- 13938 — The target table '%.*ls' of the INSERT statement cannot be on either side of an edge constraint relationship when the FROM clause contains a nested IN…
- 13939 — The target table '%.*ls' of the OUTPUT INTO clause cannot be on either side of an edge constraint relationship. Found edge constraint '%.*ls'.
- 13940 — Cannot use a derived table '%.*ls' in a MATCH clause.
- 13941 — Cannot create an edge constraint that references a node table with a disabled $node_id index.
- 13942 — The initial recursive quantifier must be 1: {1, ... }.
- 13943 — The final recursive quantifier must be greater than the initial recursive quantifier.
- 13944 — Cannot truncate table '%.*ls' because it is being referenced by an EDGE constraint.
- 13945 — Cannot delete from a node table that is the target of both an edge constraint and a foreign key constraint on the $node_id column.
- 13946 — Cannot create a foreign key constraint referencing the $node_id or $edge_id column of a graph table.
- 13947 — Merge statements containing a MATCH clause do not support derived tables or views in the MATCH clause.
- 13948 — The table name or alias '%.*s' must be marked as FOR PATH to be used in the recursive section of a SHORTEST_PATH clause.
- 13949 — The table name or alias '%.*s' was marked as FOR PATH but was not used in the recursive section of a SHORTEST_PATH clause.
- 13950 — Node table name or alias '%.*ls' was used more than once in a SHORTEST_PATH recursive section.
- 13951 — Aggregate function '%ls' is not supported with WITHIN GROUP (GRAPH PATH).
- 13952 — No columns in the aggregate '%ls' WITHIN GROUP(GRAPH PATH) reference a recursive path.
- 13953 — Columns in the aggregate '%ls' WITHIN GROUP(GRAPH PATH) reference more than one recursive path.
- 13954 — Identifier '%.*ls' in aggregate '%ls' WITHIN GROUP(GRAPH PATH) is not referencing a recursive path and cannot be used.
- 13955 — Recursive MATCH queries cannot be used in a table-valued function.
- 13956 — Recursive MATCH queries cannot be used on the right side of APPLY.
- 13957 — Recursive MATCH queries cannot be used in subqueries.
- 13958 — Internal Error: Unable to compile MATCH query with derived table or view '%.*ls'.
- 13959 — Introducing edge constraint '%.*ls' on table '%.*ls' may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or modify other constrain…
- 13960 — Cannot define edge constraint '%.*ls' with cascaded DELETE on table '%.*ls' because the table has an INSTEAD OF DELETE TRIGGER defined on it.
- 13961 — The alias or identifier '%.*ls' cannot be used in the select list, order by, group by, or having context.
- 13962 — The alias or identifier '%.*ls' is not the last node in a shortest path pattern. Only the last node in the path can be used with LAST_NODE().
- 13963 — Node table name or alias '%.*s' refers to a derived table and cannot be used by the LAST_NODE function.
- 13964 — The two aliases '%.*s' and '%.*s' refer to different underlying objects in a LAST_NODE equality expression.
- 13965 — The table name or alias '%.*s' must use the LAST_NODE function to reference the last node in a shortest_path expression.
- 13966 — A recursive quantifier expression exceeds the limit of %d. Consider the '+' syntax instead.
- 13967 — Pseudocolumn '%.*ls' is not supported for use as a partitioning column on a table or index.
- 13968 — An explicit DROP INDEX is not allowed on index '%.*ls'. It is being used for edge constraint enforcement.
- 13969 — A node or edge table cannot be created as a ledger table.
- 13970 — Change Feed is not supported for node or edge table '%ls'.
- 13971 — The pseudo column used in the index key list does not match the underlying graph object type.
- 14002 — Could not find the 'Sync' subsystem with the task ID %ld.
- 14003 — You must supply a publication name.
- 14004 — %s must be in the current database.
- 14005 — Cannot drop the publication because at least one subscription exists for this publication. Drop all subscriptions to the publication before attempting…
- 14006 — Could not drop the publication.
- 14008 — There are no publications.
- 14009 — There are no articles for publication '%s'.
- 14010 — The remote server '%s' is not defined as a subscription server. Ensure you specify the server name rather than a network alias.
- 14011 — Unable to mark server '%s' as a non SQL Server subscriber.
- 14012 — The @status parameter value must be either 'active' or 'inactive'.
- 14013 — This database is not enabled for publication.
- 14014 — The synchronization method (@sync_method) must be '[bcp] native', '[bcp] character', 'concurrent', 'concurrent_c', 'database snapshot', or 'database s…
- 14015 — The replication frequency (@repl_freq) must be either 'continuous' or 'snapshot'.
- 14016 — The publication '%s' already exists.
- 14017 — Invalid @restricted parameter value. Valid options are 'true' or 'false'.
- 14018 — Could not create the publication.
- 14019 — The @operation parameter value must be either add, drop, or alter.
- 14020 — Could not obtain the column ID for the specified column. Schema replication failed.
- 14021 — The column was not added correctly to the article.
- 14022 — The @property parameter value must be either 'description', 'sync_object', 'type', 'ins_cmd', 'del_cmd', 'upd_cmd', 'filter', 'dest_table', 'dest_obje…
- 14023 — The type must be '[indexed view ]logbased[ (manualview|manualfilter|manualboth)]', '[serializable ]proc exec', or '(view|indexed view|proc|func|aggreg…
- 14024 — The value of property 'subscriber_provider' cannot be NULL.
- 14025 — Article update successful.
- 14026 — The value of property 'subscriber_type is not a supported heterogeneous subscriber type. The value must be 1 (ODBC subscriber), or 3 (OLEDB subscriber…
- 14027 — %s does not exist in the current database.
- 14028 — Only user tables, materialized views, and stored procedures can be published as 'logbased' articles.
- 14029 — The vertical partition switch must be either 'true' or 'false'.
- 14030 — The article '%s' exists in publication '%s'.
- 14031 — User tables and views are the only valid synchronization objects.
- 14032 — The value of parameter %s cannot be 'all'. It is reserved by replication stored procedures.
- 14033 — Could not change replication frequency because there are active subscriptions on the publication.
- 14034 — The publication name (@publication) cannot be the keyword 'all'.
- 14035 — The replication option '%s' of database '%s' has already been set to true.
- 14036 — Could not enable database for publishing.
- 14037 — The replication option '%s' of database '%s' has been set to false.
- 14038 — Could not disable database for publishing.
- 14039 — Could not construct column clause for article view. Reduce the number of columns or create the view manually.
- 14040 — The server '%s' is already a Subscriber.
- 14041 — The '%s' property can only be changed if the publication is enabled for heterogeneous subscriptions. The publication is not enabled.
- 14042 — Could not create Subscriber.
- 14043 — The parameter %s passed to stored procedure %s cannot be NULL.
- 14044 — Unable to clear subscriber status for the server.
- 14045 — Unable to update subscriber_type in MSdistribution_agents table.
- 14046 — Could not drop article. A subscription exists on it.
- 14047 — Could not drop %s.
- 14048 — The server '%s' is not a Subscriber.
- 14049 — Stored procedures for replication are the only objects that can be used as a filter.
- 14050 — No subscription is on this publication or article.
- 14051 — The parameter value must be 'sync_type' or 'dest_db'.
- 14052 — The @sync_type parameter value must be "automatic", "none", "replication support only", "initialize with backup", or "initialize from lsn".
- 14053 — The subscription could not be updated at this time.
- 14054 — The subscription was updated successfully.
- 14055 — The subscription does not exist.
- 14056 — The subscription could not be dropped at this time.
- 14057 — The subscription could not be created.
- 14058 — Cannot create the subscription because the subscription already exists in the subscription database. Only one subscription to the same publication is …
- 14059 — Materialized view articles cannot be created for publications with the properties allow_sync_tran, allow_queued_tran, or allow_dts.
- 14060 — Subscriber parameters specifying provider properties must be NULL for SQL Server subscribers.
- 14061 — The @pre_creation_cmd parameter value must be 'none', 'drop', 'delete', or 'truncate'.
- 14062 — The Subscriber was dropped.
- 14063 — The remote server does not exist or has not been designated as a valid Subscriber.
- 14064 — Found generation stuck at genstatus 4.
- 14065 — The @status parameter value must be 'initiated', 'active', 'inactive', or 'subscribed'.
- 14066 — The previous status must be 'active', 'inactive', or 'subscribed'.
- 14067 — The status value is the same as the previous status value.
- 14068 — The subscription status of the object could not be changed.
- 14069 — Could not update sysarticles. The subscription status could not be changed.
- 14070 — Could not update the distribution database subscription table. The subscription status could not be changed.
- 14071 — Could not find the Distributor or the distribution database for the local server. The Distributor may not be installed, or the local server may not be…
- 14074 — The server '%s' is already listed as a Publisher.
- 14075 — The Publisher could not be created at this time.
- 14076 — Could not grant replication login permission to '%s'.
- 14077 — The publication was updated successfully.
- 14078 — The parameter must be 'description', 'taskid', 'sync_method', 'status', 'repl_freq', 'restricted', 'retention', 'immediate_sync', 'enabled_for_interne…
- 14079 — Object '%ls' cannot be published because it was created by an internal SQL Server component.
- 14080 — The remote server "%s" does not exist, or has not been designated as a valid Publisher, or you may not have permission to see available Publishers.
- 14085 — The Subscriber information could not be obtained from the Distributor.
- 14088 — The table '%s' must have a primary key to be published using the transaction-based method.
- 14089 — The clustered index on materialized view '%s' may not contain nullable columns if it is to be published using the transaction-based method.
- 14090 — Error evaluating article synchronization object after column drop. The filter clause for article '%s' must not reference the dropped column.
- 14091 — The @type parameter passed to sp_helpreplicationdb must be either 'pub' or 'sub'.
- 14092 — Could not change article because there is an existing subscription to the article.
- 14093 — Cannot grant or revoke access directly on publication '%s' because it uses the default publication access list.
- 14094 — Could not subscribe to article '%s' because heterogeneous Subscriber '%s' does not support the @pre_creation_cmd parameter value 'truncate'.
- 14095 — The value for the @sync_method parameter is not valid. Could not subscribe to publication '%s' because non-SQL Server Subscriber '%s' only supports va…
- 14096 — The path and name of the table creation script must be specified if the @pre_creation_cmd parameter value is 'drop'.
- 14097 — The 'status' value must be 'no column names', 'include column names', 'string literals', 'parameters', 'DTS horizontal partitions' or 'no DTS horizont…
- 14098 — Cannot drop Distribution Publisher '%s'. The remote Publisher is using '%s' as Distributor. Disable publishing at the Publisher before attempting to d…
- 14099 — The server '%s' is already defined as a Distributor. To reconfigure the server as a Distributor, you must first uninstall the exisiting Distributor. U…
- 14100 — Specify all articles when subscribing to a publication using concurrent snapshot processing.
- 14101 — The publication '%s' already has a Snapshot Agent defined.
- 14102 — Specify all articles when unsubscribing from a publication using concurrent snapshot processing.
- 14103 — Invalid "%s" value. Valid values are "publisher", "subscriber", or "both".
- 14105 — You have updated the distribution database property '%s' successfully.
- 14106 — Distribution retention periods must be greater than or equal to 0.
- 14107 — The @max_distretention value must be larger than the @min_distretention value.
- 14108 — Removed %ld history records from %s.
- 14109 — The @security_mode parameter value must be 0 (SQL Server Authentication) or 1 (Integrated Authentication).
- 14110 — For stored procedure articles, the @property parameter value must be 'description', 'dest_table', 'dest_object', 'creation_script', 'pre_creation_cmd'…
- 14111 — The @pre_creation_cmd parameter value must be 'none' or 'drop'.
- 14112 — This procedure can be executed only against table-based articles.
- 14113 — Could not execute '%s'. Check '%s' in the install directory.
- 14114 — The server '%s' is not configured as a Distributor.
- 14115 — The property parameter value must be %s.
- 14117 — '%s' is not configured as a distribution database.
- 14118 — A stored procedure can be published only as a 'serializable proc exec' article, a 'proc exec' article, or a 'proc schema only' article.
- 14119 — Could not add the distribution database '%s'. This distribution database already exists.
- 14120 — Could not drop the distribution database '%s'. This distributor database is associated with a Publisher.
- 14121 — Could not drop the Distributor '%s'. This Distributor has associated distribution databases.
- 14122 — The @article parameter value must be 'all' for immediate_sync publications.
- 14123 — The subscription @sync_type parameter value 'manual' is no longer supported.
- 14124 — A publication must have at least one article before a subscription to it can be created.
- 14126 — You do not have the required permissions to complete the operation.
- 14128 — Invalid @subscription_type parameter value. Valid options are 'push' or 'pull'.
- 14129 — The @status parameter value must be NULL for 'automatic' sync_type when you add subscriptions to an immediate_sync publication.
- 14130 — WARNING: The database '%s' does not contain database master key. Create a database master key and then update all replication secrets in this database…
- 14131 — The database '%s' does not contain database master key. Create database master key and repeat the procedure. For more information, see https://aka.ms/…
- 14135 — There is no subscription on Publisher '%s', publisher database '%s', publication '%s'.
- 14136 — The keyword 'all' is reserved by replication stored procedures.
- 14137 — The @value parameter value must be either 'true' or 'false'.
- 14138 — Invalid option name '%s'.
- 14139 — The replication system table '%s' already exists.
- 14143 — Cannot drop Distributor Publisher '%s'. There are Subscribers associated with it in the distribution database '%s'.
- 14144 — Cannot drop Subscriber '%s'. There are subscriptions for it in the publication database '%s'.
- 14145 — Cannot drop Subscriber '%s'. There are active subscriptions for it in the distribution database.
- 14146 — The article parameter '@schema_option' cannot be NULL.
- 14147 — Restricted publications are no longer supported.
- 14148 — Invalid '%s' value. Valid values are 'true' or 'false'.
- 14149 — Removed %ld replication history records in %s seconds (%ld row/secs).
- 14150 — Replication-%s: agent %s succeeded. %s
- 14151 — Replication-%s: agent %s failed. %s
- 14152 — Replication-%s: agent %s scheduled for retry. %s
- 14153 — Replication-%s: agent %s warning. %s
- 14154 — The Distributor parameter must be '@heartbeat_interval'.
- 14155 — Invalid article ID specified for procedure script generation.
- 14156 — The custom stored procedure calling the format for the %s command specified in the article definition does not match the %s format.
- 14157 — The subscription created by Subscriber '%s' to publication '%s' has expired and has been dropped.
- 14158 — Replication-%s: agent %s: %s.
- 14159 — Could not change property '%s' for article '%s' because there is an existing subscription to the article.
- 14160 — One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and chang…
- 14161 — The threshold [%s:%s] for the publication [%s] has been set. Make sure that the logreader and distribution agents are running and can match the latenc…
- 14162 — One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and adjus…
- 14163 — One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and adjus…
- 14164 — One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and adjus…
- 14165 — One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and adjus…
- 14166 — Disable publishing ignored error msg %d, severity %d, state %d: %s.
- 14167 — Subscription expiration
- 14168 — Transactional replication latency
- 14169 — Long merge over dialup connection
- 14170 — Long merge over LAN connection
- 14171 — Slow merge over LAN connection
- 14172 — Slow merge over dialup connection
- 14173 — Replication-%s: agent initialization failed. %s
- 14196 — The agent has never been run.
- 14197 — Value of %s parameter should be in the set %s
- 14198 — The value of the %s parameter should be in the range %s. Verify that the specified parameter value is correct.
- 14199 — The specified job '%s' is not created for maintenance plans. Verify that the job has at least one step calling xp_sqlmaint.
- 14200 — The specified '%s' is invalid.
- 14201 — 0 (all steps) ..
- 14202 — before or after @active_start_time
- 14203 — sp_helplogins [excluding Windows NT groups]
- 14204 — 0 (non-idle), 1 (executing), 2 (waiting for thread), 3 (between retries), 4 (idle), 5 (suspended), 7 (performing completion actions)
- 14205 — (unknown)
- 14206 — 0..n seconds
- 14207 — -1 [no maximum], 0..n
- 14208 — 1..7 [1 = E-mail, 2 = Pager, 4 = NetSend]
- 14209 — 0..127 [1 = Sunday .. 64 = Saturday]
- 14210 — notification
- 14211 — server
- 14212 — (all jobs)
- 14213 — Core Job Details:
- 14214 — Job Steps:
- 14215 — Job Schedules:
- 14216 — Job Target Servers:
- 14217 — SQL Server Warning: '%s' has performed a forced defection of TSX server '%s'. Run sp_delete_targetserver at the MSX in order to complete the defection…
- 14218 — hour
- 14219 — minute
- 14220 — second
- 14221 — This job has one or more notifications to operators other than '%s'. The job cannot be targeted at remote servers as currently defined.
- 14222 — Cannot rename the '%s' operator.
- 14223 — Cannot modify or delete operator '%s' while this server is a %s.
- 14224 — Warning: The server name given is not the current MSX server ('%s').
- 14225 — Warning: Could not determine local machine name. This prevents MSX operations from being posted.
- 14226 — %ld history entries purged.
- 14227 — Server defected from MSX '%s'. %ld job(s) deleted.
- 14228 — Server MSX enlistment changed from '%s' to '%s'.
- 14229 — Server enlisted into MSX '%s'.
- 14230 — SP_POST_MSX_OPERATION: %ld %s download instruction(s) posted.
- 14231 — SP_POST_MSX_OPERATION Warning: The specified %s ('%s') is not involved in a multiserver job.
- 14232 — Specify either a job_name, job_id, or an originating_server.
- 14233 — Specify a valid job_id (or 0x00 for all jobs).
- 14234 — The specified '%s' is invalid (valid values are returned by %s).
- 14235 — The specified '%s' is invalid (valid values are greater than 0 but excluding %ld).
- 14236 — Warning: Non-existent step referenced by %s.
- 14237 — When an action of 'REASSIGN' is specified, the New Login parameter must also be supplied.
- 14238 — %ld jobs deleted.
- 14239 — %ld jobs reassigned to %s.
- 14240 — Job applied to %ld new servers.
- 14241 — Job removed from %ld servers.
- 14242 — Only a system administrator can reassign ownership of a job.
- 14243 — Job '%s' started successfully.
- 14245 — Specify either the @name , @id , or @loginname of the task(s) to be deleted.
- 14250 — The specified %s is too long. It must contain no more than %ld characters.
- 14251 — Cannot specify '%s' as the operator to be notified.
- 14252 — Cannot perform this action on a job you do not own.
- 14253 — %ld (of %ld) job(s) stopped successfully.
- 14254 — Job '%s' stopped successfully.
- 14255 — The owner ('%s') of this job is either an invalid login, or is not a valid user of database '%s'.
- 14256 — Cannot start the job "%s" (ID %s) because it does not have any job server or servers defined. Associate the job with a job server by calling sp_add_jo…
- 14257 — Cannot stop the job "%s" (ID %s) because it does not have any job server or servers defined. Associate the job with a job server by calling sp_add_job…
- 14258 — Cannot perform this operation while SQLServerAgent is starting. Try again later.
- 14260 — You do not have sufficient permission to run this command. Contact your system administrator.
- 14261 — The specified %s ('%s') already exists.
- 14262 — The specified %s ('%s') does not exist.
- 14263 — Target server '%s' is already a member of group '%s'.
- 14264 — Target server '%s' is not a member of group '%s'.
- 14265 — The MSSQLServer service terminated unexpectedly. Check the SQL Server error log and operating system error logs for possible causes.
- 14266 — The specified '%s' is invalid (valid values are: %s).
- 14267 — Cannot add a job to the '%s' job category.
- 14268 — There are no jobs at this server that originated from server '%s'.
- 14269 — Job '%s' is already targeted at server '%s'.
- 14270 — Job '%s' is not currently targeted at server '%s'.
- 14271 — A target server cannot be named '%s'.
- 14272 — Object-type and object-name must be supplied as a pair.
- 14273 — You must provide either @job_id or @job_name (and, optionally, @schedule_name) , or @schedule_id .
- 14274 — Cannot add, update, or delete a job (or its steps or schedules) that originated from an MSX server.
- 14275 — The originating server must be either local server or MSX server.
- 14276 — '%s' is a permanent %s category and cannot be deleted.
- 14277 — The command script does not destroy all the objects that it creates. Revise the command script.
- 14278 — The schedule for this job is invalid (reason: %s).
- 14279 — Supply either @job_name , @job_id or @originating_server .
- 14280 — Supply either a job name (and job aspect), or one or more job filter parameters.
- 14281 — Warning: The @new_owner_login_name parameter is not necessary when specifying a 'DELETE' action.
- 14282 — Supply either a date (created or last modified) and a data comparator, or no date parameters at all.
- 14283 — Supply @target_server_groups or @target_servers , or both.
- 14284 — Cannot specify a job ID for a new job. An ID will be assigned by the procedure.
- 14285 — Cannot add a local job to a multiserver job category.
- 14286 — Cannot add a multiserver job to a local job category.
- 14287 — The '%s' supplied has an invalid %s.
- 14288 — %s cannot be before %s.
- 14289 — %s cannot contain '%s' characters.
- 14290 — This job is currently targeted at the local server so cannot also be targeted at a remote server.
- 14291 — This job is currently targeted at a remote server so cannot also be targeted at the local server.
- 14292 — There are two or more tasks named '%s'. Specify %s instead of %s to uniquely identify the task.
- 14293 — There are two or more jobs named '%s'. Specify %s instead of %s to uniquely identify the job.
- 14294 — Supply either %s or %s to identify the job.
- 14295 — Frequency Type 0x2 (OnDemand) is no longer supported.
- 14296 — This server is already enlisted into MSX '%s'.
- 14297 — Cannot enlist into the local machine.
- 14298 — This server is not currently enlisted into an MSX.
- 14299 — Server '%s' is an MSX. Cannot enlist one MSX into another MSX.
- 14301 — Logins other than the current user can only be seen by members of the sysadmin role.
- 14305 — Column '%.*ls' does not exist in table '%.*ls'.
- 14306 — The target server (TSX) version is not compatible with the master server (MSX) version (%ld.%ld.%ld).
- 14307 — Access to Integration Services package '%s' is denied.
- 14350 — Cannot initialize COM library because CoInitialize failed.
- 14351 — Cannot complete this operation because an unexpected error occurred.
- 14353 — Cannot determine the service account for this SQL Server instance.
- 14357 — Cannot list '%s' in Active Directory because the name is too long. Active Directory common names cannot exceed 64 characters.
- 14360 — %s is already configured as TSX machine
- 14362 — The MSX server must be running the Standard or Enterprise edition of SQL Server
- 14363 — The MSX server is not prepared for enlistments [there must be an operator named 'MSXOperator' defined at the MSX]
- 14364 — The TSX server is not currently enlisted
- 14365 — Specify a valid schedule_uid.
- 14366 — Only members of sysadmin role can modify the owner of a schedule.
- 14367 — One or more schedules were not deleted because they are being used by at least one other job. Use "sp_detach_schedule" to remove schedules from a job.
- 14368 — Schedule "%s" was not deleted because it is being used by at least one other job. Use "sp_detach_schedule" to remove schedules from a job.
- 14369 — The schedule ID "%s" is used by more than one job. Specify the job_id.
- 14370 — The @originating_server must be either the local server name or the master server (MSX) name for MSX jobs on a target server (TSX).
- 14371 — There are two or more schedules named "%s". Specify %s instead of %s to uniquely identify the schedule.
- 14372 — The schedule was not deleted because it is being used by one or more jobs.
- 14373 — Supply either %s or %s to identify the schedule.
- 14374 — The specified schedule name "%s" is not associated with the job "%s".
- 14375 — More than one schedule named "%s" is attached to job "%s". Use "sp_update_schedule" to update schedules.
- 14376 — More than one schedule named "%s" is attached to job "%s". Use "sp_detach_schedule" to remove schedules from a job.
- 14377 — The schedule was not attached to the specified job. The caller must own the job or the operation must be performed by a sysadmin.
- 14378 — @sysadmin_only flag is no longer supported by SQLAgent and kept here only for backwards compatibility
- 14379 — Table '%s' foreign key 'originating_server_id' does not have a matching value in the referenced view 'dbo.sysoriginatingservers_view'.
- 14380 — Field 'originating_server_id' in table sysoriginatingservers is being referenced by either sysjobs or sysschedules.
- 14390 — Only members of role sysadmin can specify the %s parameter.
- 14391 — Only owner of a job or members of sysadmin role can detach a schedule.
- 14392 — Only owner of a job or members of role sysadmin or SQLAgentOperatorRole can purge history of the job.
- 14393 — Only owner of a job or members of role sysadmin or SQLAgentOperatorRole can start and stop the job.
- 14394 — Only owner of a job schedule or members of sysadmin role can modify or delete the job schedule.
- 14395 — '%s' is a member of sysadmin server role and cannot be granted to or revoked from the proxy. Members of sysadmin server role are allowed to use any pr…
- 14396 — Only members of sysadmin server role can modify multi-server jobs
- 14397 — Only members of sysadmin server role can start/stop multi-server jobs
- 14398 — Only members of sysadmin server role can create multi-server jobs
- 14399 — Current proxy_id %d and new proxy_id %d cannot be the same.
- 14400 — Proxy %d does not have access to subsystem %d. Please use sp_grant_proxy_to_subsystem to grant permissions to this proxy.
- 14410 — You must supply either a plan_name or a plan_id.
- 14411 — Cannot delete this plan. The plan contains enlisted databases.
- 14412 — The destination database is already part of a log shipping plan.
- 14413 — This database is already log shipping.
- 14414 — A log shipping monitor is already defined.
- 14415 — The user name cannot be null when using SQL Server authentication.
- 14416 — This stored procedure must be run in msdb.
- 14417 — Cannot delete the monitor server while databases are participating in log shipping.
- 14418 — The specified @backup_file_name was not created from database '%s'.
- 14419 — The specified @backup_file_name is not a database backup.
- 14420 — The log shipping primary database %s.%s has backup threshold of %d minutes and has not performed a backup log operation for %d minutes. Check agent lo…
- 14421 — The log shipping secondary database %s.%s has restore threshold of %d minutes and is out of sync. No restore was performed for %d minutes. Restored la…
- 14422 — Supply either @plan_id or @plan_name .
- 14423 — Other databases are enlisted on this plan and must be removed before the plan can be deleted.
- 14424 — The database '%s' is already involved in log shipping.
- 14425 — The database '%s' does not seem to be involved in log shipping.
- 14426 — A log shipping monitor is already defined. Call sp_define_log_shipping_monitor with @delete_existing = 1.
- 14427 — A user name is necessary for SQL Server security.
- 14428 — Could not remove the monitor as there are still databases involved in log shipping.
- 14429 — There are still secondary servers attached to this primary.
- 14430 — Destination path %s is not valid. Unable to list directory contents. Specify a valid destination path.
- 14440 — Could not set single user mode.
- 14441 — Role change succeeded.
- 14442 — Role change failed.
- 14450 — The specified @backup_file_name was not taken from database '%s'.
- 14451 — The specified @backup_file_name is not a database backup.
- 14500 — Supply either a non-zero message ID, non-zero severity, non-null performance condition, or non-null WMI namespace and query.
- 14501 — An alert ('%s') has already been defined on this condition.
- 14502 — The @target_name parameter must be supplied when specifying an @enum_type of 'TARGET'.
- 14503 — The @target_name parameter should not be supplied when specifying an @enum_type of 'ALL' or 'ACTUAL'.
- 14504 — '%s' is the fail-safe operator. You must make another operator the fail-safe operator before '%s' can be dropped.
- 14505 — Specify a null %s when supplying a performance condition.
- 14506 — Cannot set alerts on message ID %ld.
- 14507 — A performance condition must be formatted as: 'object_name|counter_name|instance_name|comparator(> or < or =)|numeric value'.
- 14508 — Specify both @wmi_namespace and @wmi_query .
- 14509 — Specify a valid %s when supplying a @wmi_namespace .
- 14510 — Specify a null %s when supplying a @wmi_namespace .
- 14511 — The @wmi_query could not be executed in the @wmi_namespace provided. Verify that an event class selected in the query exists in the namespace and that…
- 14512 — Specify a valid %s when supplying a @wmi_query .
- 14513 — Analysis query subsystem
- 14514 — Analysis command subsystem
- 14515 — Only a member of the sysadmin server role can add a job for a different owner with @owner_login_name .
- 14516 — Proxy (%d) is not allowed for subsystem "%s" and user "%s". Grant permission by calling sp_grant_proxy_to_subsystem or sp_grant_login_to_proxy.
- 14517 — A proxy account is not allowed for a Transact-SQL subsystem.
- 14518 — Cannot delete proxy (%d). It is used by at least one jobstep. Change this proxy for all jobsteps by calling sp_reassign_proxy.
- 14519 — Only one of @login_name , @fixed_server_role , or @msdb_role should be specified.
- 14520 — "%s" is not a valid SQL Server standard login, Windows NT user, Windows NT group, or msdb database role.
- 14521 — "%s" is not a valid SQL Server fixed server role, Windows NT user, or Windows NT group.
- 14522 — '"%s" is not a valid role of an msdb database, Windows NT user, or Windows NT group.
- 14523 — "%s" has not been granted permission to use proxy "%s".
- 14524 — Supply either %s or %s.
- 14525 — Only members of sysadmin role are allowed to update or delete jobs owned by a different login.
- 14526 — The specified category "%s" does not exist for category class "%s".
- 14527 — Job "%s" cannot be used by an alert. It should first be associated with a server by calling sp_add_jobserver.
- 14528 — Job "%s" has no steps defined.
- 14529 — Proxy "%s" is not a valid Windows user.
- 14530 — The Transact-SQL subsystem cannot be executed under the context of a proxy account.
- 14531 — Permission to access proxy already granted. Verify current permissions assignments.
- 14532 — Supply both %s and %s, or none of them.
- 14533 — Use either a proxy or user_domain, user_name, or user_password parameter.
- 14534 — All user_domain, user_name, and user_password parameters should be defined.
- 14535 — The user_domain, user_name, and user_password parameters can be specified only for replication subsystems.
- 14536 — Only members of the sysadmin role can specify a "%s" parameter.
- 14537 — Execution in the context of disabled proxy (proxy_id = %d) is not allowed. Contact your system administrator.
- 14538 — SSIS package execution subsystem
- 14539 — Only a Standard or Enterprise edition of SQL Server can be enlisted into an MSX.
- 14540 — Only a SQL Server running on Microsoft Windows NT can be enlisted into an MSX.
- 14541 — The version of the MSX (%s) is not recent enough to support this TSX. Version %s or later is required at the MSX.
- 14542 — It is invalid for any TSQL step of a multiserver job to have a non-null %s value.
- 14543 — Login '%s' owns one or more multiserver jobs. Ownership of these jobs can only be assigned to members of the %s role.
- 14544 — This job is owned by '%s'. Only a job owned by a member of the %s role can be a multiserver job.
- 14545 — The %s parameter is not valid for a job step of type '%s'.
- 14546 — The %s parameter is not supported on Windows 95/98 platforms.
- 14547 — Warning: This change will not be downloaded by the target server(s) until an %s for the job is posted using %s.
- 14548 — Target server '%s' does not have any jobs assigned to it.
- 14549 — (Description not requested.)
- 14550 — Command-Line Subsystem
- 14551 — Replication Snapshot Subsystem
- 14552 — Replication Transaction-Log Reader Subsystem
- 14553 — Replication Distribution Subsystem
- 14554 — Replication Merge Subsystem
- 14555 — Active Scripting Subsystem
- 14556 — Transact-SQL Subsystem
- 14557 — [Internal]
- 14558 — (encrypted command)
- 14559 — (append output file)
- 14560 — (include results in history)
- 14561 — (normal)
- 14562 — (quit with success)
- 14563 — (quit with failure)
- 14564 — (goto next step)
- 14565 — (goto step)
- 14566 — (idle)
- 14567 — (below normal)
- 14568 — (above normal)
- 14569 — (time critical)
- 14570 — (Job outcome)
- 14571 — No description available.
- 14572 — @freq_interval must be at least 1 for a daily job.
- 14573 — @freq_interval must be a valid day of the week bitmask [Sunday = 1 .. Saturday = 64] for a weekly job.
- 14574 — @freq_interval must be between 1 and 31 for a monthly job.
- 14575 — @freq_relative_interval must be one of 1st (0x1), 2nd (0x2), 3rd [0x4], 4th (0x8) or Last (0x10).
- 14576 — @freq_interval must be between 1 and 10 (1 = Sunday .. 7 = Saturday, 8 = Day, 9 = Weekday, 10 = Weekend-day) for a monthly-relative job.
- 14577 — @freq_recurrence_factor must be at least 1.
- 14578 — Starts whenever the CPU usage has remained below %ld percent for %ld seconds.
- 14579 — Automatically starts when SQLServerAgent starts.
- 14580 — job
- 14581 — Replication Transaction Queue Reader Subsystem
- 14582 — Only a sysadmin can specify '@output_file_name' parameter for a jobstep.
- 14583 — Only a sysadmin can specify '@database_user_name' parameter.
- 14585 — Only the owner of DTS Package '%s' or a member of the sysadmin role may reassign its ownership.
- 14586 — Only the owner of DTS Package '%s' or a member of the sysadmin role may create new versions of it.
- 14587 — Only the owner of DTS Package '%s' or a member of the sysadmin role may drop it or any of its versions.
- 14588 — ID.VersionID =
- 14589 — [not specified]
- 14590 — DTS Package '%s' already exists with a different ID in this category.
- 14591 — SSIS folder '%s' already exists in the specified parent folder.
- 14592 — DTS Category '%s' was found in multiple parent categories. You must uniquely specify the category to be dropped.
- 14593 — SSIS folder '%s' contains packages and/or other folders. You must drop these first.
- 14594 — DTS Package
- 14595 — DTS Package '%s' exists in different categories. You must uniquely specify the package.
- 14596 — DTS Package '%s' exists in another category.
- 14597 — DTS Package ID '%s' already exists with a different name.
- 14598 — Cannot drop the Local, Repository, or LocalDefault DTS categories.
- 14599 — Name
- 14600 — Proxy "%s" has not been granted permission to use subsystem "%s".
- 14601 — Operator "%s" is not enabled and therefore cannot receive notifications.
- 14602 — Operator "%s" does not have an e-mail address specified.
- 14603 — Database Mail is not properly configured.
- 14604 — Both %s parameters (id and name) cannot be NULL
- 14605 — Both %s parameters (id and name) do not point to the same object
- 14606 — %s id is not valid
- 14607 — %s name is not valid
- 14608 — Either %s or %s parameter needs to be supplied
- 14609 — Mail database to user database association does not exist and therefore cannot be updated
- 14610 — Either @profile_name or @description parameter needs to be specified for update
- 14611 — Account sequence number must be supplied for update
- 14612 — Each principal should have at least one default profile
- 14613 — The specified '%s' cannot use commas (,) to separate addresses: '%s'. To continue, use semicolons (;) to separate addresses.
- 14614 — %s is not a valid mailserver_type
- 14615 — The @username parameter needs to be supplied if the @password is supplied.
- 14616 — Unable to retrieve the newly created credential [%s] from the credential store.
- 14617 — Mail host database specified is invalid
- 14618 — Parameter '%s' must be specified. This parameter cannot be NULL.
- 14619 — Received an error on the Service Broker conversation with Database Mail. Database Mail may not be available, or may have encountered an error. Check t…
- 14620 — The Service Broker conversation to Database Mail ended without a response from Database Mail. Database Mail may not be available, or may have encounte…
- 14621 — Parameter @attachmentencoding does not support the value "%s". The attachment encoding must be "MIME".
- 14622 — Parameter @importance does not support the value "%s". Mail importance must be one of LOW, NORMAL, or HIGH.
- 14623 — Parameter @sensitivity does not support the value "%s". Mail sensitivity must be one of NORMAL, PERSONAL, PRIVATE, or CONFIDENTIAL.
- 14624 — At least one of the following parameters must be specified. "%s".
- 14625 — Parameter @attach_query_result_as_file cannot be 1 (true) when no value is specified for parameter @query . A query must be specified to attach the re…
- 14626 — Parameter @mailformat does not support the value "%s". The mail format must be TEXT or HTML.
- 14627 — Received error %d while sending a message as part of the %s operation. Database Mail may not be available, or may have encountered an error. Check the…
- 14628 — The format of the parameter @attachments is incorrect. The file names must be separated by a semicolon ";".
- 14629 — There is no configuration parameter named "%s", or the value provided is not of the correct data type.
- 14630 — Database Mail is not permitted to send files with the file extension %s.
- 14631 — The current user ('%s') either does not have permission to access the database specified in the parameter @execute_query_database or cannot impersonat…
- 14632 — The user name %s specified in @execute_query_as is invalid. There is no user by that name.
- 14633 — The database name "%s" specified in @execute_query_database is invalid. There is no database by that name.
- 14634 — Warning: %s'
- 14635 — Mail (Id: %d) queued.
- 14636 — No global profile is configured. Specify a profile name in the @profile_name parameter.
- 14637 — Activation failure.
- 14638 — Activation successful.
- 14639 — The mail queue was started by login "%s".
- 14640 — The mail queue stopped by login "%s".
- 14641 — Mail not queued. Database Mail is stopped. Use sysmail_start_sp to start Database Mail.
- 14642 — Default attachment encoding
- 14643 — Default dialog lifetime
- 14644 — Default maximum file size
- 14645 — Extensions not allowed in outgoing mails
- 14646 — Number of retry attempts for a mail server
- 14647 — Delay between each retry attempt to mail server
- 14648 — Minimum process lifetime in seconds
- 14649 — Unable to test profile. Database Mail is stopped. Use sysmail_start_sp to start Database Mail.
- 14650 — Service Broker message delivery is not enabled in this database. Use the ALTER DATABASE statement to enable Service Broker message delivery.
- 14651 — Unable to test profile. Service Broker message delivery is not enabled in this database. Use the ALTER DATABASE statement to enable Service Broker mes…
- 14652 — Invalid message received on the ExternalMailQueue. conversation_handle: %s. message_type_name: %s. message body: %s.
- 14653 — Invalid %s value received on the ExternalMailQueue. conversation_handle: %s. message_type_name: %s. message body: %s.
- 14654 — Unexpected message received on the ExternalMailQueue. conversation_handle: %s. message_type_name: %s. message body: %s.
- 14655 — Invalid XML message format received on the ExternalMailQueue. conversation_handle: %s. message_type_name: %s. message body: %s.
- 14657 — Mail not queued. Maximum number of mails per day (%ld) for login %s has been exceeded.
- 14658 — Failed to retrieve SQLPath for syssubsystems population.
- 14659 — Failed to retrieve VerSpecificRootDir for syssubsystems population.
- 14660 — Database Compatibility Level is too low. Compatibility Level must be Version80 or higher.
- 14661 — Query execution failed: %s
- 14662 — mailitem_id on conversation %s was not found in the sysmail_send_retries table. This mail item will not be sent.
- 14663 — Mail Id %d has exceeded the retry count. This mail item will not be sent.
- 14664 — Database Mail logging level: normal - 1, extended - 2 (default), verbose - 3
- 14665 — Mail items deletion is initiated by user "%s". %d items deleted.
- 14666 — User name cannot be supplied when using default credentials
- 14667 — Mail Id %d has been deleted from sysmail_mailitems table. This mail will not be sent.
- 14668 — Deleting profile %s failed because there are some unsent emails associated with this profile, use force_delete option to force the deletion of the pro…
- 14670 — Cannot delete the active collection set '%s'. Stop the collection set and then try to delete it again.
- 14671 — Cannot update the name or the parameters of the collection item '%s' in the active collection set '%s'. Stop the collection set and then try to update…
- 14672 — Cannot delete the collection item '%s' in the active collection set '%s'. Stop the collection set and then try to delete the collection item again.
- 14673 — Cannot delete the collector type '%s'. Delete all collection items associated with this collector type and then try to delete it again.
- 14674 — Cannot upload data for the inactive collection set '%s'. Start the collection set and then try to upload the data again.
- 14675 — Cannot update the name, target, proxy_id, logging_level, or collection_mode, or add collection item to the active collection set '%s'. Stop the collec…
- 14676 — The user does not have permission to change '%s'. The user must be a member of data collector role '%s'.
- 14677 — The user does not have permission to perform this operation. The user must be a member of data collector role '%s'.
- 14678 — SQL Server Trace with id %d has been stopped and closed by external user. SQL Server Trace collector will attempt to re-create the trace.
- 14679 — The specified %s (%s) is not valid in this data warehouse.
- 14680 — Management Data Warehouse database can only be installed on an instance of SQL Server 2008 or higher.
- 14681 — Cannot perform this procedure when the collector is disabled. Enable the collector and then try again.
- 14682 — The state of the collection set has changed, but it will not start or stop until the collector is enabled.
- 14683 — A collection set in cached mode requires a schedule.
- 14684 — Caught error#: %d, Level: %d, State: %d, in Procedure: %s, Line: %d, with Message: %s
- 14685 — Collection set: '%s' does not contain any collection items, so starting the collection set will have no effect.
- 14686 — The MDWInstance and MDWDatabase parameters of the configuration store cannot be null.
- 14687 — Invalid value (%d) of the @cache_window parameter. Allowable values are: -1 (cache all upload data from previous upload failures), 0 (cache no upload …
- 14688 — A collection set cannot start when SQL Server Agent is stopped. Start SQL Server Agent.
- 14689 — A collection set cannot start if the management data warehouse is not configured. Run the instmdw.sql script to create and configure the management da…
- 14690 — Cannot perform this procedure when the collector is enabled. Disable the collector and then try again.
- 14691 — The status of the collector cannot be null. This may indicate an internal corruption in the collector configuration data.
- 14692 — Insufficient priveleges to start collection set: '%s'. Only a member of the 'sysadmin' fixed server role can start a collection set without a SQL Serv…
- 14693 — A collection set cannot start without a schedule. Specify a schedule for the collection set.
- 14694 — Cannot upload data on-demand for the collection set '%s' in non-cached mode.
- 14695 — Cannot collect data on-demand for the collection set '%s' in cached mode.
- 14696 — Cannot update or delete a system collection set, or add new collection items to it.
- 14697 — Unable to convert showplan to XML. Error #%d on Line %d: %s
- 14698 — PowerShell Subsystem
- 14699 — Data Collector cannot be enabled when SQL Server Agent is stopped. Start SQL Server Agent.
- 14700 — Collects data about the disk and log usage for all databases.
- 14701 — Disk Usage
- 14702 — Disk Usage - Data Files
- 14703 — Disk Usage - Log Files
- 14704 — Collects top-level performance indicators for the computer and the Database Engine. Enables analysis of resource use, resource bottlenecks, and Databa…
- 14705 — Server Activity
- 14706 — Server Activity - DMV Snapshots
- 14707 — Server Activity - Performance Counters
- 14708 — Collects query statistics, T-SQL text, and query plans of most of the statements that affect performance. Enables analysis of poor performing queries …
- 14709 — Query Statistics
- 14710 — Query Statistics - Query Activity
- 14711 — Changes to SQL dumper configuration will take effect when the collection set is restarted. To perform an immediate dump, use the dtutil /dump option.
- 14712 — Only dbo or members of dc_admin can install or upgrade instmdw.sql. Contact an administrator with sufficient permissions to perform this operation.
- 14713 — A management data warehouse cannot be installed to SQL Server Express Edition.
- 14714 — Attempting to upgrade a Management Data Warehouse of newer version '%s' with an older version '%s'. Upgrade aborted.
- 14715 — Collects data about instances of SQL Server that are managed in the SQL Server Utility.
- 14716 — Utility Information
- 14718 — Utility Information - Managed Instance
- 14719 — "%s" has not been granted permission to use proxy.
- 14720 — The operation failed because credential '%s' identity is not a valid Windows account
- 14721 — AutoAdmin Subsystem
- 14801 — Multiple REMOTE_DATA_ARCHIVE definition.
- 14802 — Cannot disable REMOTE_DATA_ARCHIVE because the database contains at least one table having REMOTE_DATA_ARCHIVE enabled.
- 14803 — Cannot alter REMOTE_DATA_ARCHIVE option for table '%.*ls' because REMOTE_DATA_ARCHIVE is not enabled for the database.
- 14804 — The database credential '%s' cannot be found or the user doesn't have premission to access the credential.
- 14806 — The identity specified for the database credential '%s' is invalid. The identity must be a valid username for the remote stretch server administrator.
- 14807 — The secret specified for the database credential '%s' is invalid. The secret must be a valid password for the remote stretch server administrator.
- 14808 — Cannot disable REMOTE_DATA_ARCHIVE when migration is enabled.
- 14809 — Cannot enable REMOTE_DATA_ARCHIVE on database '%s'. The REMOTE_DATA_ARCHIVE option can only be set on user databases.
- 14810 — The database option REMOTE_DATA_ARCHIVE is already enabled on database '%s'.
- 14811 — Remote server '%s' is not an Azure SQL Database V12 (or higher) server. A database can only be stretched to an Azure SQL Database V12 (or higher) serv…
- 14812 — Cannot enable REMOTE_DATA_ARCHIVE for table '%.*ls' due to '%ls'. %ls
- 14813 — Cannot enable REMOTE_DATA_ARCHIVE for table '%.*ls' due to column '%.*ls' '%ls'. %ls
- 14814 — Code generation for REMOTE_DATA_ARCHIVE failed (%ls).
- 14815 — File error during REMOTE_DATA_ARCHIVE operation. GetLastError = %d (%ls).
- 14816 — The code generation directory cannot be created or set up correctly.
- 14817 — The server '%s' is not accessible. Ensure that the remote server exists and the Azure SQL DB Firewall Rules permit access to the server. If you believ…
- 14818 — The %ls on table '%ls' will not be enforced because of the use of REMOTE_DATA_ARCHIVE.
- 14819 — Stretch operation failed due to an internal error.
- 14820 — The stretch code generator output is corrupted. Stretch code generation and remote table provisioning will be re-tried.
- 14821 — Cannot execute in REMOTE_ONLY mode since remote part does not exist or is invalid for this operation.
- 14822 — '%s' is not a valid option for the @mode parameter. Enter 'ALL', 'LOCAL_ONLY' or 'REMOTE_ONLY'.
- 14823 — %ls failed on table '%.*ls' because it is not supported on tables with REMOTE_DATA_ARCHIVE option enabled.
- 14824 — Access to REMOTE_DATA_ARCHIVE has been disabled through server configuration option 'remote data archive'. Use "exec sp_configure 'remote data archive…
- 14825 — Cannot perform '%ls' on table '%.*ls' because REMOTE_DATA_ARCHIVE is enabled. %ls
- 14826 — Update and delete of rows eligible for migration in table '%.*ls' is not allowed because of the use of REMOTE_DATA_ARCHIVE.
- 14827 — Unable to access remote data archive: Error: %d, Severity: %d, State: %d, Line: %d '%s'
- 14828 — Cannot perform 'CREATE INDEX' on view '%.*ls' because it references table '%.*ls' with REMOTE_DATA_ARCHIVE enabled.
- 14829 — Table '%.*ls' cannot be used in READTEXT, WRITETEXT and UPDATETEXT statements because it has REMOTE_DATA_ARCHIVE option enabled.
- 14830 — Cannot query table '%.*ls' because this operation is currently disabled for this object.
- 14831 — Cannot set the Remote Data Archive query mode for database '%.*ls' because REMOTE_DATA_ARCHIVE is not enabled on the database.
- 14832 — Querying tables having REMOTE_DATA_ARCHIVE option enabled will not be possible in LOCAL_AND_REMOTE query mode in database '%.*ls' before Remote Data A…
- 14833 — Cannot set the Remote Data Archive query mode LOCAL_AND_REMOTE for database '%.*ls' because data on remote side is not consistent. See the SQL Server …
- 14834 — Cannot de-authorize database '%.*ls' because REMOTE_DATA_ARCHIVE is not enabled on the database.
- 14835 — Cannot de-authorize database '%.*ls' because it is already disconnected from the remote database.
- 14836 — Cannot reconcile stretched indexes for database '%.*ls' because REMOTE_DATA_ARCHIVE is not enabled on the database.
- 14837 — Cannot reconcile indexes for stretched table '%.*ls' because migration is not outbound on the table.
- 14838 — Table '%.*ls' cannot be accessed in SNAPSHOT transaction isolation level because it has REMOTE_DATA_ARCHIVE option enabled.
- 14839 — Only column identifiers are allowed as parameters passed to function '%.*ls'.
- 14840 — The filter predicate cannot be set for table '%.*ls' because all rows are already eligible for migration.
- 14841 — The filter predicate '%.*ls' for table '%.*ls' cannot be replaced with '%.*ls' because conditions necessary to perform the replacement are not satisfi…
- 14842 — The database '%.*ls' contains REMOTE_DATA_ARCHIVE tables, it will be marked as disconnected from the remote during the restore. If you would like to r…
- 14843 — Copying remote database '%.*ls' to remote database '%.*ls'.
- 14844 — Remote database '%.*ls' has completed copying, and is now online.
- 14845 — Waiting for remote database copy to complete.
- 14846 — Cannot re-authorize database '%.*ls' because REMOTE_DATA_ARCHIVE is not enabled on the database.
- 14847 — Cannot re-authorize database '%.*ls' because it is already authorized and connected to a remote database.
- 14848 — Attempted Migration failed. Remote insert failed. Error : %d.
- 14849 — Attempted Migration failed. Remote insert failed to insert all the rows. Expected rows : %d, Actual remote rows inserted: %d.
- 14850 — Attempted Migration failed. Incrementation of the batch ID failed. Expected batch ID : %I64d, Current batch ID : %I64d.
- 14851 — Attempted Reconciliation failed. The new max remote batch IDs is not less than the initial. Initial: %I64d, New: %I64d
- 14852 — Cannot query table '%.*ls' because data reconciliation is in progress. This is part of the automatic recovery process for a remote data archive enable…
- 14853 — Function '%.*ls' cannot be used as Stretch filter predicate because it does not meet necessary requirements.
- 14854 — The Remote Data Archive connection to the server '%ls' succeeded.
- 14855 — The Remote Data Archive connection to the server '%ls' failed.
- 14856 — The procedure %ls requires the %ls parameter if the database is not enabled for REMOTE_DATA_ARCHIVE.
- 14857 — The procedure %ls does not accept the %ls parameter if the database is enabled for REMOTE_DATA_ARCHIVE.
- 14858 — Cannot queue more stretch tasks. Please wait for remaining tasks to be finished and try again later.
- 14859 — The database '%.*ls' contains REMOTE_DATA_ARCHIVE tables, it will be marked as disconnected from the remote during the restore. If you would like to r…
- 14860 — '%.*ls' expects parameter '%.*ls', which was not supplied.
- 14861 — Modifying the collation is not allowed when REMOTE_DATA_ARCHIVE is already enabled on database '%.*ls'.
- 14862 — Cannot rename index '%ls'. Indexes on tables with REMOTE_DATA_ARCHIVE option enabled cannot be renamed.
- 14863 — Stretch was disabled after migration started. Please enable stretch and retry.
- 14864 — Attempted inbound migration failed. Local insert failed. Error : %d.
- 14865 — Attempted inbound migration failed. Decrementation of the batch ID failed. Expected batch ID : %I64d, Current batch ID : %I64d.
- 14866 — Attempted unlinking of the stretched table failed. If this table isn't dropped, please retry the operation of setting REMOTE_DATA_ARCHIVE to OFF on th…
- 14867 — User does not have permission to enable REMOTE_DATA_ARCHIVE with FEDERATED_SERVICE_ACCOUNT = ON.
- 14868 — Inbound migration is in progress or paused. Migration direction outbound cannot be set at this time. Please retry after inbound migration is complete.
- 14869 — Must be DB OWNER to use the REMOTA_DATA_ARCHIVE_OVERRIDE hint.
- 14870 — REMOTE_DATA_ARCHIVE_OVERRIDE hint is not allowed inside a user transaction.