错误码目录 / Microsoft SQL Server
Microsoft SQL Server 错误码目录 · 第 12 / 18 页
本页收录 Microsoft SQL Server 的 17,993 条错误码知识条目,每条均可打开独立详情页,包含错误说明、编号信息、官方文档与公开资料。
- 21658 — The data type mapping does not exist. Verify the list of mappings by querying msdb.dbo.sysdatatypemappings.
- 21659 — Cannot execute this procedure for a SQL Server Publisher. The Publisher must be a non-SQL Server Publisher.
- 21660 — The value specified for the parameter @full_or_fast for article '%s' must be 0, 1, or 2.
- 21661 — The value specified for the @shutdown_agent parameter for article '%s' must be 0 or 1.
- 21662 — The source object [%s].[%s] on the non-SQL Server Publisher was either not found or is not supported. If the object exists, verify that it meets the r…
- 21663 — Cannot find a valid primary key for the source table [%s].[%s]. A valid primary key is required to publish the table. Add or correct the primary key d…
- 21664 — Index [%s] contains unique nullable column.
- 21665 — Key [%s] contains unique nullable column.
- 21666 — Cannot specify more than %d column names for the index or primary key because this exceeds the maximum number of columns supported by SQL Server. %d c…
- 21667 — The index "%s" was not created. The index has a key length of at least %d bytes. The maximum key length supported by SQL Server is %d bytes.
- 21668 — The constraint "%s" was not created because one or more columns in the constraint is not published. Either include all columns in the published articl…
- 21669 — Column [%s] cannot be published because it uses an unsupported data type [%s]. View supported data types by querying msdb.dbo.sysdatatypemappings.
- 21670 — Connection to server [%s] failed.
- 21671 — Cannot execute the procedure. Administration of a non-SQL Server Publisher must be performed at the associated SQL Server Distributor. Execute the pro…
- 21672 — The login '%s' has insufficient authorization to execute this command.
- 21673 — Test connection to publisher [%s] failed. Verify authentication information.
- 21674 — Unable to update the linked server [%s] for the login [%s].
- 21675 — Cannot specify more than %d indexes for a single table. %d indexes specified. Excess indexes have been ignored.
- 21676 — Heterogeneous subscriber '%s' could not add a subscription for heterogeneous publication '%s' because publication sync method is not 'character', 'con…
- 21677 — Heterogeneous publisher '%s' cannot be defined as a subscriber.
- 21678 — The parameter "%s" can be set to "%s" only when "%s" is set to "%s".
- 21679 — Peer-to-peer publications only support a '%s' parameter value of %s.
- 21680 — The Distribution Agent was unable to update the cached log sequence numbers (LSNs) for Originator %s, OriginatorDB %s, OriginatorDBVersion %d, Origina…
- 21681 — The current user '%s' does not have a valid linked server login mapping for non-SQL Server Publisher [%s]. Replication connects to the Publisher throu…
- 21682 — Cannot publish table [%s].[%s]. The replication administraive user requires an explicit SELECT grant, or a SELECT grant through PUBLIC, in order to pu…
- 21683 — Cannot verify administrator login privileges for Oracle Publisher %s. Verify connection information and ensure that you can connect to the Publisher t…
- 21684 — The replication administrative user for Oracle Publisher "%s" has insufficient permissions. Refer to the script /MSSQL/Install/oracleadmin.sql for the…
- 21685 — Request '%s' for Oracle schema filter for Oracle publisher '%s' failed.
- 21686 — The operation "%s" is not valid. Valid operations are "add", "drop", and "help".
- 21687 — Schema filters are supported only for Oracle Publishers. The Publisher "%s" is a "%s" Publisher.
- 21688 — The current login '%s' is not in the publication access list (PAL) of any publication at Publisher '%s'. Use a login that is in the PAL, or add this l…
- 21689 — A NULL @schema value is invalid for add and drop schema filter operations.
- 21690 — The subscriber db cannot be the same as the publisher db when the subscriber is the same as the publisher
- 21691 — sp_mergesubscription_cleanup should be called on the subscription database
- 21692 — Failed to script the subscriber stored procedures for article '%s' in publication '%s'
- 21694 — %s cannot be null or empty when %s is set to 0 (SQL Server Authentication). Specify a login or set security mode to 1 (Integrated Authentication).
- 21695 — The replication agent job '%s' was not removed because it has a non-standard name; manually remove the job when it is no longer in use.
- 21696 — The stored procedure only applies to Oracle Publishers. The Publisher '%s' is a %s Publisher.
- 21698 — The parameter '%s' is no longer supported.
- 21699 — Unable to reuse view '%s' because it was not found. Re-creating all system table views. This is an informational message only. No user action is requi…
- 21701 — Microsoft SQL Server Additive Conflict Resolver
- 21702 — Microsoft SQL Server Averaging Conflict Resolver
- 21703 — Microsoft SQL Server DATETIME (Earlier Wins) Conflict Resolver
- 21704 — Microsoft SQL Server DATETIME (Later Wins) Conflict Resolver
- 21705 — Microsoft SQL Server Download Only Conflict Resolver
- 21706 — Microsoft SQL Server Maximum Conflict Resolver
- 21707 — Microsoft SQL Server Merge Text Columns Conflict Resolver
- 21708 — Microsoft SQL Server Minimum Conflict Resolver
- 21709 — Microsoft SQL Server Priority Column Resolver
- 21710 — Microsoft SQL Server Subscriber Always Wins Conflict Resolver
- 21711 — Microsoft SQL Server Upload Only Conflict Resolver
- 21712 — Microsoft SQLServer Stored Procedure Resolver
- 21715 — Cannot register the article resolver %s. This can occur if the account under which SQL Server is running does not have access to the distribution data…
- 21716 — The parameter %s contains invalid characters or patterns. For security reasons, parameters cannot contain command terminators, system procedure invoca…
- 21717 — The article resolver name cannot be an empty string or NULL. Specify a valid value for the @article_resolver parameter.
- 21718 — For a COM resolver, the @resolver_clsid cannot be an empty string or NULL. Specify a valid value for @resolver_clsid .
- 21719 — The Subscriber '%s':'%s' was not marked for reinitialization at the Publisher because the subscription is either anonymous or not valid. Verify that v…
- 21720 — Cannot find a job that matches the ID or name specified in the parameters @dynamic_snapshot_jobid or @dynamic_snapshot_jobname . Verify the values spe…
- 21721 — UserScripts
- 21722 — Failed to add an extended trigger for replicating the '%.*ls' event.
- 21723 — The value specified for the @pubid parameter of procedure '%s' is not valid or is NULL. Verify that the Merge Agent is running correctly. Reinitalize …
- 21724 — Cannot add the foreign key %s with the CASCADE option because table %s is published. Add the NOT FOR REPLICATION clause to the foreign key definition.
- 21725 — Cannot alter the view. An indexed view replicated as a table cannot be altered to a nonindexed view. Drop the view from the publication before attempt…
- 21727 — Cannot complete the replication operation. The security check for the current user is failing. Only members of the sysadmin fixed server role, or db_o…
- 21728 — The article can support logical record level conflict detection only if it uses logical record conflict resolution.
- 21729 — The @keep_partition_changes property cannot be set to "true." This is because the @publication_compatibility_level property is set to 90RTM or higher …
- 21730 — Table '%s' can not be replicated because it contains imprecise Primary Key column, please recreate table without 'persisted' clause and try again.
- 21731 — Cannot add a constraint or default without an explicit name, because the table is included in a publication that replicates DDL events. Specify a uniq…
- 21732 — Using Data Transformation Services (DTS) packages in replication requires a password that is not NULL or empty. Specify a valid value for parameter '%…
- 21733 — Cannot open database %s. The upgrade of replication %s could not be performed. Run %s again from the %s database when the %s is accessible.
- 21734 — Peer-to-peer publications do not support replicating timestamp columns as varbinary(8). You cannot add an article with this option, nor add or alter a…
- 21735 — Source object [%s].[%s] is a temporary object and cannot be published.
- 21736 — Unable to relocate the article log table to a different tablespace. Verify that the replication administrative user login can connect to the Oracle Pu…
- 21737 — The property '%s' is not valid for '%s' Publishers.
- 21738 — The property '%s' is not valid for %s publications.
- 21739 — Cannot alter property '%s'. You must first call the stored procedure sp_articleview to initialize the article; the property can then be altered.
- 21740 — Oracle subscriber '%s' not found. Loopback support cannot be checked.
- 21741 — Unable to retrieve distributor information from Oracle publisher '%s'. Bi-directional publishing requires Oracle publisher to exist before the Oracle …
- 21742 — The Oracle Publisher name is '%s' and the Oracle Subscriber name is '%s'. Bidirectional Oracle publishing requires the Oracle Publisher and Subscriber…
- 21743 — Unable to retrieve the originator information for the Oracle subscriber '%s'.
- 21744 — Oracle bidirectional publishing requires parameter '%s' to have a value of '%s'.
- 21745 — Cannot generate a filter view or procedure. Verify that the value specified for the @filter_clause parameter of sp_addarticle can be added to the WHER…
- 21746 — The '%s' character length must not exceed %d.
- 21747 — Cannot establish a connection to the Oracle Publisher '%s'. Verify connection information and ensure that you can connect to the Publisher through a t…
- 21748 — The article was dropped at the Distributor, but information at the Publisher '%s' was not dropped. No action is required; the information is cleaned u…
- 21749 — The Publisher was dropped at the Distributor, but information on the Publisher '%s' was not dropped. Connect to the Oracle Publisher with SQL*PLUS and…
- 21750 — The table %s does not have a primary key, which is required for transactional replication. Create a primary key on the table.
- 21751 — Cannot publish view %s as a table because it does not have a unique clustered index. Publish the view as a view, or add a unique clustered index.
- 21752 — The current user %s does not have SELECT permission on the table %s. The user must have SELECT permission to retrieve rows at the Subscriber that have…
- 21753 — The table %s, which is specified in the @tablename parameter of sp_getqueuedrows, is not part of any active initialized queued subscription. Ensure yo…
- 21754 — Processing has been terminated. The resultset for sp_getqueuedrows is larger than 16,000, the maximum size that the procedure can return. Run the Queu…
- 21755 — Failed to mark '%s' as a system object.
- 21756 — Based on article settings, table %s should have an identity column, but it does not have one. Verify article settings with sp_helparticle and change t…
- 21757 — The subscription is read-only. The publication that this subscription synchronizes with allows updates at the Subscriber, but a value of 'read-only' w…
- 21758 — Cannot find a valid Queue Reader Agent ID for the subscription to Publisher %s, database %s, publication %s. The specified subscription to an updating…
- 21759 — Cannot add the column '%s' to the table '%s'. The table already contains the maximum number of columns allowed for an article in a merge publication (…
- 21760 — Cannot execute the replication script in the 'master' database; the current session will be terminated. The script must be executed in the distributio…
- 21761 — Cannot execute the replication script; the current session will be terminated. Check for any errors returned by SQL Server during execution of the scr…
- 21762 — The distribution database '%s' has a compatibility level of %d, which is different from that of the master database. The two compatibility levels must…
- 21763 — Message Queuing Service is not running. Start this service and retry the operation.
- 21764 — Cannot create the publication. Specifying a value of 'msmq' for the parameter @queue_type is supported only on Microsoft Windows NT platforms. Specify…
- 21765 — The column msrepl_tran_version has been predefined and allows NULLs. This column will be dropped and recreated to not allow NULLs for updating subscri…
- 21766 — Table %s contains an identity column that is marked as Not For Replication, but the @identitymanagementoption parameter of sp_addarticle is set to 'no…
- 21767 — Warning: The parameter '%s' is obsolete and is available only for backwards compatibility. It will not be available in future releases. Instead of thi…
- 21768 — When executing sp_adddistributor for a remote Distributor, you must use a password. The password specified for the @password parameter must be the sam…
- 21769 — Custom data type mappings are not supported. You must validate the correctness of the mapping. If mappings are not compatible, errors will likely occu…
- 21770 — Data type mapping from '%s' to '%s' does not exist. Review source and destination data type, length, precision, scale, and nullability. Query the syst…
- 21771 — %s is not within the supported range of %d and %d.
- 21772 — Property "%s" requires the parameters @force_invalidate_snapshot and @force_reinit_subscription to be set to "true".
- 21773 — The distribution database '%s' cannot be opened due to inaccessible files. The database will be dropped, but distribution database cleanup tasks will …
- 21774 — This procedure is supported only for non-SQL Server Publishers. The Publisher '%s', on which you are executing the procedure, is a SQL Server Publishe…
- 21775 — Failed to generate column bitmap for article '%s'.
- 21776 — Failed to generate published column bitmap for article '%s'.
- 21777 — Failed to generate article view name for article '%s'.
- 21778 — Cannot add Publisher objects to the Oracle Publisher for article '%s'. Verify connection information and ensure that you can connect to the Publisher …
- 21779 — Cannot use the specified data type mapping. The matching destination data type for source type %s cannot be found. Query the system table msdb.dbo.sys…
- 21780 — The non-SQL Server Publisher is missing one or more %s objects. Drop and re-create the Publisher and the replication administrative user schema.
- 21781 — Unable to retrieve heterogeneous metadata. Verify connection information
- 21782 — Cannot add primary key column '%s' to article '%s'. If the Publisher is a non-SQL Server Publisher, the primary key could have violated SQL Server lim…
- 21783 — Cannot add the Publisher triggers and the article log table to the Oracle Publisher for the article '%s'. Verify connection information and ensure tha…
- 21784 — You must specify a non-NULL value for the @rowfilter parameter.
- 21785 — Failure to query Oracle XactSet Job attributes for publisher '%s'.
- 21786 — Failure to refresh Oracle XactSet Job for publisher '%s'.
- 21787 — Failure to query Oracle Xact batching enabled flag for publisher '%s'.
- 21788 — Invalid parameter passed to sp_IHSetXactBatching. The bit flag to enable/disable Xact batching must be 0 or 1.
- 21789 — Failure to set the Oracle Xact batching enabled flag for publisher '%s'.
- 21790 — Cannot publish the table '%s.%s' from the Publisher '%s'. Verify connection information and ensure that you can connect to the Publisher through a too…
- 21791 — The table '%s.%s' already appears in a transactional publication on Oracle Gateway Publisher '%s'. When using the Oracle Gateway option, a table publi…
- 21792 — The table '%s.%s' already appears in the transactional publication '%s' on Publisher '%s'. The Oracle Gateway publishing option (the default) allows a…
- 21793 — Non-SQL Server Publishers are supported only in the Enterprise and Developer editions of SQL Server. The edition of this instance is %s.
- 21794 — The value specified for the @propertyname parameter is not valid. Use one of the following values: %s.
- 21795 — The value specified for property %s is not valid. Use one of the following values: %s.
- 21796 — The property "xactsetjobinterval" must be assigned a value greater than or equal to 0.
- 21797 — Cannot create the agent job. '%s' must be a valid Windows login in the form : 'MACHINE\Login' or 'DOMAIN\Login'. See the documentation for '%s'.
- 21798 — Cannot execute the replication administrative procedure. The '%s' agent job must be added through '%s' before continuing. See the documentation for '%…
- 21799 — The %s agent for Publisher (%s), database (%s), publication (%s) cannnot be found. Create the agent with the appropriate procedure: sp_addpublication_…
- 21800 — The common generation watermark is invalid at this replica since it does not exist or metadata for changes not yet propagated may have been cleaned up…
- 21801 — The stored procedure sp_createagentparameter failed to add one or more parameters to the system table msdb.dbo.MSagentparameterlist. Check for any err…
- 21802 — The agent profile creation process cannot validate the specified agent parameter value. '%s' is not a valid value for the '%s' parameter. The value mu…
- 21803 — Cannot update agent parameter metadata. Replication could not insert parameter '%s' into table '%s'. Verify that replication is properly installed. Ch…
- 21804 — The value '%d' specified for the @agent_type parameter of sp_getagentparameterlist is not valid. Specify a valid value of 1, 2, 3, 4, or 9.
- 21805 — The agent profile creation process cannot validate the specified agent parameter value. '%s' is not a valid value for the '%s' parameter. The value mu…
- 21806 — The agent profile creation process cannot validate the specified agent parameter value: the profile_id %d does not exist or it does not support the pa…
- 21807 — For a .NET Assembly Business Logic Handler, the @resolver_clsid must be specified as NULL.
- 21808 — For a .NET Assembly Business Logic Handler, the @resolver_info must contain the class name in '%s' that implements the Microsoft.SqlServer.Replication…
- 21809 — DDL replication is not enabled for database '%ls' because its compatibility level is less than 80.
- 21810 — Identity column can only be added to a published table with 'Not For Replication' clause
- 21811 — Cannot drop the column '%s' because it is used by replication: it is referenced in a filter or view by article '%s'. To drop the column, you must firs…
- 21812 — Cannot perform "Disable Trigger All" on table %s because it belongs to a publication that supports updatable subscriptions (replication adds triggers …
- 21813 — Can not disable trigger %s on table %s because it is required by updatable publication.
- 21814 — DDL replication failed to refresh custom procedures, please run "exec sp_register_custom_scripting 'CUSTOM_SCRIPT', your_script, '%s', '%s' "and try a…
- 21815 — Can not alter replicated object '%s' to 'with encrypted'.
- 21816 — An invalid value was specified for parameter '%s'. The value must be '%s' when changing this property.
- 21817 — The property '%s' is only valid for push subscriptions.
- 21818 — The parameters for security, batch size, and scheduling have been deprecated and should no longer be used. For more information, see the "sp_addsubscr…
- 21819 — Cannot change the property '%s' . This property is only valid for subscriptions that allow updating at the Subscriber. The subscription against which …
- 21820 — Cannot write to the script file in the snapshot folder at the Distributor (%ls). Ensure that there is enough disk space available. Also ensure that th…
- 21821 — Specify one and only one of the parameters - %s or %s.
- 21822 — Cannot perform %s on %s as entry already exists.
- 21823 — Cannot perform %s on %s as entry does not exist.
- 21824 — Can not add constraints to multiple columns because table %s is published but column %s is not in all active partitions, please use separate DDL state…
- 21825 — Can not drop constraints in the same DDL statement which drops columns from table %s because the table is published, please use separate DDL statement…
- 21826 — The property '%s' is valid only for %s subscriptions. Use '%s' for %s subscriptions.
- 21827 — The %s parameters have been deprecated and should no longer be used. For more information, see the '%s' documentation.
- 21828 — The proxy account for jobstep_uid (%s) could not be found.
- 21830 — You cannot specify schema_option 0x4 (script identity as identity rather than the base data type) for article '%s'. The value specified for the parame…
- 21831 — The %s already exists. Use '%s' to change any settings/properties.
- 21832 — Only members of the sysadmin fixed server role can perform this operation without specifying %s.
- 21833 — An error occurred when creating a trace event at Oracle publisher '%s'. The trace event could not be posted.
- 21834 — The primary key for '%s.%s' has %d columns. SQL Server supports a maximum of %d columns. Redefine the primary key so that it has no more than the maxi…
- 21835 — The index for the primary key '%s.%s' is at least %d bytes. SQL Server supports a maximum key length of %d bytes. Reduce the number of columns in the …
- 21836 — The distribution agent must be run in single subscription stream mode prior to resetting the subscription xact_seqno.
- 21837 — A replication agent job (%s) for this subscription already exists.
- 21838 — The %s parameter(s) have been deprecated from this procedure. The value(s) should now be specified when calling '%s'.
- 21839 — Article '%s' can not support schema_option 0x20 or 0x2000000000 because it contains computed column, check/default constraint or primary key which is …
- 21840 — Can not add CLR type based computed column or check constraint to table '%s' because article '%s' supports schema_option 0x20.
- 21841 — DDL replication is forcing reinitialization because either publication'%s' uses character mode bcp, or timestamp/identity column is being replicated a…
- 21842 — %s can only be specified/changed for heterogeneous publications when %s is set to %s.
- 21843 — Article '%s' can not be added, an indexed view published as 'indexed view logbased' and a stored procedure in either form of 'proc exec' can not be pu…
- 21844 — Can not alter XML, CLR type or MAX type column because table is published and article '%s' supports the schema option to map this to a base column typ…
- 21845 — Can not alter procedure '%s' to depend on an indexed view published as 'indexed view logbased' or a base table because the indexed view depends on thi…
- 21846 — Cannot find a distribution agent job for the specified transactional or snapshot push subscription.
- 21847 — Cannot find a merge agent job for the specified merge push subscription.
- 21848 — The specified pull subscription is not configured with a synchronization agent job.
- 21850 — The property "%s" cannot be changed to "%s" after the value has already been set to "%s".
- 21851 — Peer-to-peer publications only support a "%s" value of %s. Article "%s" currently has a "%s" value of %s. This value must be changed to continue.
- 21852 — Peer-to-peer publications do not support %s. Article "%s" currently has %s. This must be changed to continue.
- 21853 — Warning: The "%s" property for %s "%s" has been changed to "%s" because it is required by %s.
- 21854 — Could not add new article to publication '%s' because of active schema change activities or a snapshot is being generated.
- 21855 — The login %s provided in sp_link_publication is not mapped to any user in publishing database %s.
- 21856 — For a .NET Assembly Business Logic Handler, the .NET Assembly name should be the name of a valid assembly in '%s' that contains the class that impleme…
- 21857 — Forcing re-initialization for article '%s' in publication '%s', the clustered index on indexed view '%s' may have been dropped by upgrade or restore p…
- 21858 — Snapshot can not process article '%s' in publication '%s', the clustered index on indexed view '%s' may have been dropped by upgrade or restore proces…
- 21859 — Cannot change subscription property '%s' because there is no entry for this subscription in the MSsubscription_properties table. Call sp_addmergepulls…
- 21860 — Table '%s' in database '%s' is subscribing to transactional queued publication and published for merge for uploading changes, this may cause non-conve…
- 21861 — The current operation was aborted because it would deactivate an article in a publication for which a snapshot was being generated.
- 21862 — FILESTREAM columns cannot be published in a publication by using a synchronization method of either 'database snapshot' or 'database snapshot characte…
- 21863 — Cannot add the SPARSE property to a column for the article '%s' because merge replication does not support sparse columns.
- 21864 — Cannot publish the article '%s' or add the COLUMN_SET attribute set to its base table '%s' because replication does not support column sets.
- 21865 — The '%s' publication property must be either 'true' or 'false'.
- 21866 — The publication property '%s' can only be set to '%s' when the publication property '%s' is set to '%s'.
- 21867 — ALTER TABLE SWITCH statement failed. The table '%s' belongs to a publication which does not allow switching of partitions
- 21868 — ALTER TABLE SWITCH statement failed. The statement is not allowed because one or more of the tables in this statement is an article with a different d…
- 21869 — Cannot add filter between proposed parent article '%s' and proposed child article '%s' since this would introduce a cycle in the filter relationships.…
- 21870 — Distribution agent encountered a deadlock while applying commands in SubscriptionStreams mode. Spid %u waiting on lock (type '%s', mode '%s') for inde…
- 21871 — Publisher %s of database %s has not been redirected.
- 21872 — The availability group associated with Virtual Network Name '%s' has no replicas.
- 21873 — You are not authorized to run the stored procedure %s.
- 21874 — The stored procedure %s must be run from a distirbution database. The current database %s is not a distribution database.
- 21875 — The parameters @original_publisher and @publisher_db to stored procedure '%s' may not be NULL.
- 21876 — The distributor '%s' is not the distributor for original publisher '%s' and publisher database '%s'.
- 21877 — The original publisher '%s' for database '%s' is not a remote server for the distributor.
- 21878 — Unable to create a linked server to use in contacting the remote publisher for original publisher '%s', publisher database '%s', and redirected publis…
- 21879 — Unable to query the redirected server '%s' for original publisher '%s' and publisher database '%s' to determine the name of the remote server; Error %…
- 21880 — The virtual network name '%s' has been used to identify the redirected publisher for original publisher '%s' and database '%s'. The availability group…
- 21881 — The database '%s' at the redirected publisher '%s' for original publisher '%s' and database '%s' is either not synchronized or is not active.
- 21882 — The database '%s' at the redirected publisher '%s' for original publisher '%s' and database '%s' belongs to a HADRon availability group and must be re…
- 21883 — The query at the redirected publisher '%s' to determine whether the publisher database '%s' belonged to an availability group failed with error '%d', …
- 21884 — The query at the redirected publisher '%s' to determine the health of the availability group associated with publisher database '%s' failed with error…
- 21885 — The return code of the failed call was '%d'.
- 21886 — The remote server name returned was null.
- 21887 — The query at the redirected publisher '%s' to determine whether the publisher database '%s' belonged to an availability group failed with error '%d', …
- 21888 — The SQL Server instance '%s' is not configured to support replication. To enable the SQL Server instance to serve as a replication publisher, configur…
- 21889 — The SQL Server instance '%s' is not a replication publisher. Run sp_adddistributor on SQL Server instance '%s' with distributor '%s' in order to enabl…
- 21890 — The SQL Server instance '%s' with distributor '%s' and distribution database '%s' cannot be used with publisher database '%s'. Reconfigure the publish…
- 21891 — The publisher '%s' with distributor '%s' is not known as a publisher at distributor '%s'. Run sp_adddistpublisher at distributor '%s' to enable the re…
- 21892 — Unable to query sys.availability_replicas at the availability group primary associated with virtual network name '%s' for the server names of the memb…
- 21893 — The subscribers ( %s ) of original publisher '%s' do not appear as remote servers at redirected publisher '%s'. Run sp_addlinkedserver at the redirect…
- 21894 — Unable to configure a linked server to query replica host server '%s': return code = %d.
- 21895 — One or more publisher validation errors were encountered for replica host '%s'.
- 21896 — The query at the redirected publisher '%s' to determine whether the SQL Server instance is a replication publisher failed with error '%d', error messa…
- 21897 — The query to determine whether the local distributor '%s' is the distributor for remote publisher '%s' failed with error '%d', error message '%s'.
- 21898 — The publisher '%s' uses distribution database '%s' and not '%s' which is required in order to host the publishing database '%s'. Run sp_changedistpubl…
- 21899 — The query at the redirected publisher '%s' to determine whether there were sysserver entries for the subscribers of the original publisher '%s' failed…
- 21900 — Unable to find listener name with the value provided for property redirected_publisher.
- 21901 — The publication property '%s' cannot be changed when publication is not enabled for peer-to-peer.
- 22001 — FreeStaleVersionSpace failed for page %S_PGID for database id '%d'. It will be retired in the next iteration of the version cleaner.
- 22002 — Internal Error: A expected large object wasn't found.
- 22003 — Stale/aborted version cleanup was aborted for database id '%d' due to database shutdown.
- 22004 — [%d]. System transaction with xdes id %S_XID was aborted due to failure injection while moving rows from one page to another.
- 22005 — ADR cleanup failed for database id '%d'.
- 22006 — Version cleanup was aborted for database id '%d' due to database exclusive waiter.
- 22007 — Version cleanup was aborted for database id '%d' due to planned failover.
- 22008 — Aborted versions belonging to this filegroup could not be cleaned up.
- 22010 — Cannot change the READONLY property of the filegroup containing Persistent Version Store which is required for Accelerated Database Recovery.
- 22011 — Invalid IAM chain encountered while dropping allocation unit.
- 22012 — Persistent version store is enabled on the database '%.*ls' but the version store manager could not be initialized.
- 22013 — [DbId: %d][FileId: %d] Could not obtain file add/remove latch to purge invalid file ranges before shrinking the file.
- 22014 — Lock ordinal population was aborted due to database exclusive waiter.
- 22015 — Forwarding of row [FileId: %d][PageInFile: %d][SlotId: %d] during logical revert failed due to insufficient space.
- 22016 — [DbId:%d] Sum of row sizes (%d) on page (%d:%d) exceeds maximum size of a page.
- 22017 — Could not find row version because it has been cleaned, this is due to transaction abort for some other reason on any node in the system where version…
- 22019 — Version cleanup was aborted for database id '%d' due to logical pause of db.
- 22020 — Internal Error: Tried to access an expired large object.
- 22021 — The EX Latch failure occurred on RefreshAllHoBts.
- 22022 — An internal error occurred while getting physical foreign file size.
- 22023 — Used by testshell test in failpoint simulation.
- 22024 — Version cleanup was aborted for database id '%d' due to SD transition.
- 22025 — DNS record '%.*ls' already exists.
- 22026 — Read replica '%.*ls' cannot be added under the reader endpoint '%.*ls' because it is not found on server '%.*ls'.
- 22027 — '%.*ls' operation for read replica '%.*ls' on reader endpoint '%.*ls' failed.
- 22028 — Reader endpoint '%.*ls' not found.
- 22029 — Reader endpoint '%.*ls' already exists.
- 22030 — The read replica '%.*ls' on server '%.*ls' is already under a different reader endpoint '%.*ls'.
- 22031 — Read replica '%.*ls' on server '%.*ls' has a different compute size than the existing read replicas under the reader endpoint '%.*ls'. All read replic…
- 22032 — Read replica '%.*ls' on server '%.*ls' is under reader endpoint '%.*ls'. Remove replica from the reader endpoint before changing its compute size. All…
- 22033 — Reader endpoint "%.*ls" cannot be empty or null. It can only be made up of lowercase letters 'a'-'z', the numbers 0-9 and the hyphen. The hyphen may n…
- 22034 — Read replica "%.*ls" is not a named replica of the primary database "%.*ls"
- 22035 — Reader endpoint '%.*ls' cannot be created because that would exceed the maximum number of reader endpoints for a primary database.
- 22036 — Read replicas cannot be added to the reader endpoint '%.*ls' because it would exceed the maximum allowed number of read replicas for that endpoint.
- 22037 — Reader endpoint '%.*ls' is currently being modified. Try again later.
- 22038 — A management operation on Reader endpoint '%.*ls' failed.
- 22039 — Database '%.*ls' is not a HyperScale database.
- 22040 — Primary HyperScale server '%.*ls' is busy.
- 22041 — Primary HyperScale database '%.*ls' is busy.
- 22042 — Reader endpoint server '%.*ls' is busy.
- 22043 — Read replica '%.*ls' is busy.
- 22044 — A create or update reader endpoint operation completed; however, some of the databases could not be added to or removed from the reader endpoint '%.*l…
- 22101 — The value supplied for the change_columns argument of CHANGE_TRACKING_IS_COLUMN_IN_MASK function is not valid. The value must be a bitmask returned by…
- 22102 — The arguments supplied are not valid for the CHANGES option of the CHANGETABLE function.
- 22103 — The arguments supplied are not valid for the VERSION option of the CHANGETABLE function.
- 22104 — A table returned by the CHANGETABLE function must be aliased.
- 22105 — Change tracking is not enabled on table '%.*ls'.
- 22106 — The CHANGETABLE function does not support remote data sources.
- 22107 — Object '%.*ls' is of a data type that is not supported by the CHANGETABLE function. The object must be a user-defined table.
- 22108 — The CHANGE_TRACKING_CONTEXT WITH clause cannot be used with a SELECT statement.
- 22109 — The "context" argument for the CHANGE_TRACKING_CONTEXT WITH clause must be of type varbinary data type with a maximum length of 128.
- 22110 — The number of columns specified in the CHANGETABLE(VERSION ...) function does not match the number of primary key columns for table '%.*ls'.
- 22111 — The column '%.*ls' specified in the CHANGETABLE(VERSION ...) function is not part of the primary key for table '%.*ls'.
- 22112 — Each primary key column must be specified once in the CHANGETABLE(VERSION ...) function. The column '%.*ls' is specified more than once.
- 22113 — %S_MSG is not allowed because the table is being tracked for change tracking.
- 22114 — Change tracking options for ALTER DATABASE cannot be combined with other ALTER DATABASE options.
- 22115 — Change tracking is enabled for one or more tables in database '%.*ls'. Disable change tracking on each table before disabling it for the database. Use…
- 22116 — Change tracking is not supported by this edition of SQL Server.
- 22117 — For databases that are members of a secondary availability replica, change tracking is not supported. Run change tracking queries on the databases in …
- 22118 — Cannot enable change tracking on table '%.*ls'. Change tracking is not supported when the primary key contains encrypted columns.
- 22119 — Cannot enable change tracking on table '%.*ls'. Change tracking requires a primary key constraint on the table to be enabled. Enable the primary key c…
- 22120 — Invalid value for cleanup batch size.
- 22121 — Deleted %ld row(s) per millisecond from %s
- 22122 — Change Tracking autocleanup failed on side table of "%s". If the failure persists, use sp_flush_CT_internal_table_on_demand to clean up expired record…
- 22123 — Change Tracking autocleanup is blocked on side table of "%s". If the failure persists, check if the table "%s" is blocked by any process .
- 22124 — Change Tracking manual cleanup is blocked on side table of "%s". If the failure persists, check if the table "%s" is blocked by any process .
- 22125 — Change tracking autocleanup is currently not able to maintain retention for database ID %d. Number of expired records: %d. If this warning persists, c…
- 22126 — Change tracking auto cleanup encountered an error when getting list of large side table IDs
- 22127 — Change tracking autocleanup encountered an invalid side table object id
- 22128 — Could not allocate memory for Change Tracking operation. Verify that SQL Server has sufficient memory for all operations. Check the memory settings on…
- 22129 — Change Tracking Adaptive Cleanup is disabled for all the databases on this instance.
- 22201 — Internal error. Unable to acquire the latch holding buffers for DW Tiered Storage ColumnStore Scan.
- 22202 — Internal error. Unable to run the remote cs garbage collector. Error Code 22202.
- 22203 — Internal error. Unable to update the blobs table in the catalogDB. Error Code 22203.
- 22204 — Internal error. Unable to refresh catalog db information for service uri [%ls].
- 22205 — Internal error. Unable to get catalog information via the catalog helper.
- 22206 — Internal error. Unable to get lock for protected shared buffer
- 22207 — Internal error. Unable to get a valid dbtable. Error Code 22207.
- 22208 — Access to DW Tiered Storage ColumnStore blob failed. See earlier errors for cause.
- 22209 — Internal error. Unable to populate instance member list.
- 22210 — Internal error. Unable to get instance member.
- 22211 — Internal error. Invalid instance member state.
- 22212 — An error occurred while reading remote column store segment HoBt 0x%I64X, Object %d, Column %d, Type %d in database %d. The segement could not be decr…
- 22213 — Internal error. Unable to get catalog information via the sp.
- 22214 — Internal error. Unable to initialise XODBC Connection Manager.
- 22215 — Internal error. Unable to get catalog information.
- 22216 — Internal error. Protected buffer failure.
- 22217 — Internal error. Persist lru cost info failure.
- 22218 — Internal error. Catalog Communication Failure.
- 22219 — Internal error. Internal table base failure.
- 22220 — Beginning database migration scan for database "%s".
- 22221 — Database migration scan for database "%s" is complete.
- 22222 — Database migration scan for database '%.*ls' was aborted. Internal error. Migration scan was aborted.
- 22223 — Internal error. Unable to refresh migration type from fabric property.
- 22224 — Internal error. ADW Optimized for Compute storage detected. Unable to retrieve blob.
- 22225 — An internal error (%d, %d) occurred. Please retry the operation. If the problem persists contact Microsoft Azure Customer Support.
- 22226 — An internal error (%d, %d) occurred. Please retry the operation. If the problem persists contact Microsoft Azure Customer Support.
- 22227 — TIERED Storage Scanner encountered an error message "%ls" in "%ls".
- 22228 — The columnstore remote lob header is invalid.
- 22229 — Remote storage columnstore data checksum mismatch. Expected checksum from blob is %lu, actual check sum from read buffers is %lu.
- 22230 — Failure to copy remote consolidated rowgroup blob HoBt id 0x%I64X, rowgroup id %d in database %d to Azure Block Blob Storage. Error code 0x%X.
- 22231 — : Encountered an unexpected error while trying to access a lob row (HRESULT = 0x%x).
- 22232 — An error occurred while writing remote column store segment HoBt 0x%I64X, Object %d, Column %d, Type %d in database %d. The segement could not be encr…
- 22233 — : Encountered an unexpected error while trying to access/update remote object (HRESULT = 0x%x).
- 22234 — An error occurred while writing remote rowgroup metadata HoBt 0x%I64X, Rowgroup %d,in database %d. The metadata could not be encrypted.
- 22235 — Could not process request due to internal error encountered during control node communication
- 22236 — : Encountered an unexpected error while trying to access/update fork entries (HRESULT = 0x%x).
- 22237 — Failure to copy manifest file block blobs during Table Clone operation. Error code 0x%X.
- 22301 — DW FIDO mode is not enabled.
- 22302 — DW FIDO transaction context not found.
- 22303 — Updates are not allowed from a FIDO Scan transaction.
- 22304 — Reading or Writing to database files is not supported in FIDO DBs.
- 22305 — A NULL or unexpected value was returned by an ODBC call.
- 22306 — Only CCI tables are allowed in Fido mode.
- 22307 — Alter statements are only allowed from a FIDO Alter transaction.
- 22308 — Fido thread failed to acquire a lock.
- 22309 — Fido Cache DB not found.
- 22310 — Failed to create Fido DB with key: [%.*ls].
- 22311 — Generic Fido out of bounds error.
- 22312 — Failed to remap rowset with Id '%I64d' on a Fido DB.
- 22313 — Failed to find Fido columns in rowset with Id '%I64d'.
- 22314 — Fido invalid ODBC connection.
- 22315 — Invalid Fido Transaction type %d.
- 22316 — Failed to acquire CSI Cache lock.
- 22317 — Fido invalid ODBC column.
- 22318 — Fido ODBC transaction failed a commit.
- 22319 — An invalid access to a Fido DB Rowset (DbId '%lu', RowsetId '%I64d') was performed.
- 22320 — Fido DB (DbId:'%lu', Name: '%.*ls') can only be used under a Fido session context.
- 22321 — Fido DB (DbId:'%lu', Name: '%.*ls') cannot be used in current session. Only DbId: '%lu' is allowed.
- 22322 — Fido session context invalid. Min cell Id cannot greater than Max cell Id
- 22323 — DW FIDO GLM server is not initialized.
- 22324 — DW FIDO GLM Client is not initialized.
- 22325 — The Key column Id (%d) for Rowset (%I64d) is out of range.
- 22326 — Updates are not allowed from a Scan only FIDO Rowset.
- 22327 — Invalid Rowset Id (%I64d) was provided to a Fido Rowset remapping sys RowsetId (%I64d).
- 22328 — Alters are only allowed on the GLMServer instance.
- 22329 — Open of Rowset (%I64d) in DB (%d) failed.
- 22330 — RowsetColumn Id (%d) missing in Rowset (%I64d).
- 22331 — Provided Accessor Mode is not supported in Fido GLM Rowset.
- 22332 — Data unsupported by Fido GLM Rowset.
- 22333 — Failed to retrieve Blob Container info.
- 22334 — This operation cannot be preformed in this version of Database.
- 22335 — Cannot obtain a LOCK resource at this time due to internal error. Rerun your statement when there are fewer active users.
- 22336 — The provided transaction was not found.
- 22337 — Invalid nesting level for lock manager table.
- 22338 — Invalid nested transaction value for requesting lock.
- 22339 — An error occurred while releasing a lock with error code: %d state: %d severity: %d
- 22340 — An error occurred while requesting a lock with error code: %d state: %d severity: %d
- 22341 — An error occurred while releasing all locks for transaction id %d with error code: %d state: %d severity: %d
- 22342 — Cannot release locks for transaction %d as it has active nested transactions
- 22343 — This DDL statement is not supported in this version of SQL Server.
- 22344 — This statement cannot be executed in this version of Database.
- 22345 — Transaction manager already exists.
- 22346 — Transaction manager not found.
- 22347 — Transaction manager lock acquisition failure
- 22348 — Transaction manager address not initialized
- 22350 — Found a fatal inconsistency in Delta files.
- 22351 — Encountered error %lu during parsing of RowGroup metadata. Contact Technical Support.
- 22352 — Encountered unexpected error during physical catalog maintenance. Contact Technical Support.
- 22353 — The SQL instances has not been correctly setup to allow this operation. Please retry the operation again. If the problem persists contact Microsoft Az…
- 22354 — Lock manager initialization failed.
- 22355 — Lock manager does not exist. Please retry the operation again. If the problem persists contact Microsoft Azure Customer Support.
- 22356 — Lock manager shutdown failed.
- 22357 — Point in time can only be specified for a Read transaction.
- 22358 — The Database Controller required for this operation was not found. Please retry the operation again. If the problem persists contact Microsoft Azure C…
- 22359 — Exceeded the resource limit on the number concurrent DDLs and active transactions. Please scale up to a higher SLO or reduce the workload on the SQL i…
- 22360 — Logical Database Name was not provided
- 22361 — The handler for the work item does not exists.
- 22362 — Timed out while waiting for internal task to complete.
- 22363 — Lock manager client does not exist.
- 22364 — Lock manager client initialization failed.
- 22365 — Client initialization failed with error %d.
- 22366 — Transaction context encode failed with error %d
- 22367 — Transaction context decode failed with error %d and size %d.
- 22368 — Database '%ls' configuration '%ls' not found.
- 22369 — Failed to start an async task to sync the physical catalog.
- 22370 — The statement failed due to an internal error while retrieving the query text.
- 22371 — Background task failed.
- 22372 — Lock release failed due to an internal error. Check the errorlog for more information.
- 22374 — DDL statements are not allowed in User transactions.
- 22375 — An operation that requires a feature to be enabled was started, but the feature is disabled. Aborting. Contact support for assistance.
- 22376 — Invalid Transaction context while requesting lock.
- 22377 — Transaction abort sequence number entry not found in cache
- 22378 — DW Temp Table Creation Fail
- 22379 — Failed to acquire the data update lock for DB Id '%ls'.
- 22380 — Updating the rowcount of a distributed table is not allowed unless trace flag 12127 is enabled. Rerun the statement by enabling the said trace flag.
- 22381 — Fido GLM remote execute command failed.
- 22382 — Transport DBM endpoint not available.
- 22383 — Transport not initialized.
- 22384 — DDL statements cannot cross DB boundaries.
- 22385 — The statement could not be serialized. Please try again.
- 22386 — Transport UCS connection string resolve failed.
- 22387 — Transport get response failed.
- 22388 — Failed to start the client sync thread during manager startup.
- 22389 — Transaction Action failed with error 0x%x.
- 22390 — Database name '%.*ls' is not allowed in this edition of SQL.
- 22391 — Background task queue failed.
- 22392 — Background task discovery failed.
- 22393 — Background task failed with error: %d, state: %d and message: '%ls'.
- 22394 — Failed to start the Server due to error %d. Check errorlog for more info.
- 22395 — Failed to start database '%ls' as it already exists.
- 22396 — Encountered exception when executing DBCC command.
- 22397 — Attempt to concurrently modify index [%ls].[%ls] row with Key %ls by multiple transactions '%I64d', '%I64d'.
- 22398 — Failed to set the drop time of object: '%I64d' as its create was not tracked. TxnId %I64d.
- 22399 — Failed Update TxnId of object: '%I64d' by TxnId %I64d. Old TxnId %I64d.
- 22401 — Failed to open internal table.
- 22402 — A NULL or unexpected value was returned by a remote call.
- 22403 — Unexpected operation performed on an internal table.
- 22404 — Failed to Register Database '%ls' in master.
- 22405 — Bulk insert bucketization failed.
- 22406 — Failed to Sync Database '%ls' to Server.
- 22407 — Failed to acquire DW transaction lock.
- 22408 — A severe error occurred. Error:%d, State:%d.
- 22409 — Table '%.*ls' does not exist.
- 22410 — Validations failed for the internal task handler.
- 22411 — Transaction got aborted due to unexpect situation.
- 22412 — Transaction Manager fail to create schema
- 22413 — Resource manager lock acquisition failure
- 22414 — Resource manager not found.
- 22415 — An error occurred while releasing all locks for transaction id 0x%016llx while commit of transaction, HRESULT = 0x%08X
- 22416 — An error occurred while releasing all locks for transaction id 0x%016llx while rollback of transaction, HRESULT = 0x%08X
- 22417 — An error occurred while commit transaction id 0x%016llx, HRESULT = 0x%08X
- 22418 — An error occurred while rollback transaction id 0x%016llx, nested id 0x%016llx, HRESULT = 0x%08X
- 22419 — An error occurred while begin transaction, transaction options = %d, HRESULT = 0x%08X
- 22420 — An error occurred while get list, transaction id 0x%016llx, list options = %d, HRESULT = 0x%08X
- 22421 — Changes in encryption are not allowed on this database type if tables are present. Please drop all tables and try again.
- 22422 — Failed to initialize a remote connection for an internal component.
- 22424 — %ls is not a supported statement type.
- 22425 — %ls is not a supported option in %ls statement.
- 22426 — Failed to get the client id from the Resource Manager.
- 22427 — Operation failed due to an error in a background task. Please retry the operation again. If the problem persists contact Microsoft Azure Customer Supp…
- 22428 — Failed to Begin a new transaction as a valid one already exists. Please Commit or Rollback the existing transaction before starting a new one.
- 22429 — Dropping multiple objects including Temp table is not supported in this version of SQL Server
- 22430 — Operation failed as the Database '%.*ls' is shutting down. Please retry the operation again. If the problem persists contact Microsoft Azure Customer …
- 22431 — You must have a compute pool provisioned in order to enable encryption. Create a compute pool and try again.
- 22432 — Failure in the compression engine. If the problem persists contact Microsoft Azure Customer Support.
- 22433 — An error occurred while set transaction token, HRESULT = 0x%08X
- 22434 — An inconsistency was detected while enumerating files for the database. If the problem persists contact Microsoft Azure Customer Support.
- 22435 — Catalog sync failed while updating system tables for [%I64d] database, rowset [%I64d], directory [%I64d], rowgroup [%I64d]. Used by failpoints.
- 22436 — This operation is not supported in this Database Version.
- 22437 — Failed to find a valid TxnId of object: '%ld'
- 22438 — Can't set retention policy on an invalid object id: '%ld'
- 22439 — Internal error. Unable to load database settings.
- 22440 — An error occurred during timestamp conversion. Please provide the correct format in the form yyyy-mm-ddThh:mm:ss.
- 22441 — An error occurred while begin transaction, requested point in time not found '%ls'
- 22442 — Point in time not supported for this statement type
- 22443 — ALTER TABLE RANGE statement failed. The specified table '%.*ls' is not partitioned.
- 22444 — ALTER TABLE RANGE statement failed. The specified range must not be 'NULL'.
- 22445 — This DML statement is not supported in this database version.
- 22446 — DeltaForce encountered an operational exception.
- 22447 — Internal table IQ_CATATLOG_OBJECTS_TABLE error.
- 22448 — An error occurred while updating the data encryption key.
- 22449 — The reencryption task encountered a blob that was already encrypted.
- 22450 — An error occurred with clone with message '%ls'.
- 22451 — An error occurred while initializing resource manager
- 22452 — Index quality DMV got invalid arguments.
- 22453 — Unable to get remote storage space usage: Error: %d, Severity: %d, State: %d, Line: %d '%s'
- 22454 — Internal error. Encryption scan was aborted.
- 22455 — A SERVICE_OBJECTIVE must be specified when creating a Synapse pool.
- 22456 — Pool '%.*ls' does not exist. Make sure that the name is entered correctly.
- 22457 — DBCC command failed with error : '%.*ls'.
- 22458 — Cannot specify a temporary object (i.e., View, Table or Stored Procedure) in a rename statement.
- 22459 — The metadata backup path was incorrectly formatted.
- 22460 — Index store client does not exist.
- 22461 — %ls is not supported for %ls.
- 22462 — Encountered exception during generation of script for clone.
- 22463 — Increase rowset blob directory generation id failed
- 22464 — Database collation name '%.*ls' is not valid.
- 22465 — Failed to clean up rows for object: '%d'. (HRESULT = 0x%x)
- 22466 — Connection to reserved databases are not allowed.
- 22467 — Failed complete data warehouse maintenance operation. See telemetry for more details.
- 22468 — The metadata backup failed.
- 22469 — Failed to update metadata of cloned table
- 22470 — Rowset info is not correct, please check the following info: %ls
- 22471 — Failed to serialize source table directory info
- 22472 — The supplied T-SQL statement is too long. The maximum allowed length is 4000 characters.
- 22473 — %ls is allowed only when connected to the logical master of a Synapse workspace.
- 22474 — DBCC CHECKIDENTITY with NORESEED is not supported in Azure Synapse Analytics
- 22475 — Failed to set the undrop time of object: '%I64d' as it was not found or drop was not tracked. TxnId %I64d.
- 22476 — Toad index tuning policy check failed. See other errors and telemetry for details.
- 22477 — The period of %ld %S_MSG is too big for data retention.
- 22478 — Retention Policy is not supported on temporary table
- 22479 — Failed to Alter Column as a concurrent Alter Column transaction has been detected.
- 22480 — Creating or altering table '%.*ls' failed because its maximum row size exceeds the allowed maximum of %d bytes including %d bytes of internal overhead…
- 22481 — Creating a Synapse SQL pool with name '%ls' is not allowed as it is a reserved system name. Please choose another name for your Synapse SQL pool.
- 22482 — %ls is an invalid name for a pool. Please make sure that it begins with a lowercase letter, consists only of lowercase letters, numbers, or hyphens ('…
- 22483 — MAX_SERVICE_OBJECTIVE '%ls' cannot be less than or equal to SERVICE_OBJECTIVE '%ls'.
- 22484 — MAX_SERVICE_OBJECTIVE '%ls' cannot be more than '%ld' times the value of SERVICE_OBJECTIVE '%ls'.
- 22485 — '%ls' is an invalid name for a pool as it contains profanity. Please choose a different name for your pool.
- 22486 — Get directory info failed
- 22487 — %ls is allowed only when connected to Synapse frontend.
- 22488 — A WORKLOAD_GROUP must be specified when creating a Synapse workload classifier.
- 22489 — START_TIME and END_TIME must be specified together when creating a Synapse workload classifier.
- 22490 — Invalid data requested from database completed requests table.
- 22491 — The DDL statement failed due to an internal error. Please retry the operation again. If the problem persists contact Microsoft Azure Customer Support.
- 22492 — Unable to perform operation as the data provided is invalid.
- 22493 — The database '%.*ls' failed to sync. Please retry the operation again. If the problem persists contact Microsoft Azure Customer Support.
- 22494 — There is already an object named '%.*ls' in the temp db.
- 22495 — %ls is allowed only when connected to Synapse frontend.
- 22496 — The client sync failed with a request to retry the operation again.
- 22497 — Redo of Block %I64d.%I64d on Database [%ls] failed with error '%.*ls'.
- 22498 — There is not enough resources to perform the operation. Please retry your operation later.
- 22499 — An error occurred when looking for clone container: '%ls'.
- 22500 — Unexpected
- 22501 — All articles in the publication passed data validation (rowcount and checksum).
- 22502 — Not All articles in the publication passed data validation (rowcount only)
- 22503 — Initializing.
- 22504 — Applying the snapshot to the Subscriber.
- 22505 — The merge completed with no data changes processed.
- 22506 — No data needed to be merged.
- 22507 — Uploading data changes to the Publisher.
- 22508 — Downloading data changes to the Subscriber.
- 22509 — Retrieving subscription information.
- 22510 — Retrieving publication information.
- 22511 — The merge completed successfully.
- 22512 — Cannot use partition groups with unfiltered publications. Set "use_partition_groups" to "false" using sp_changemergepublication.
- 22513 — Cannot use partition groups because the join filter between the following articles contains one or more functions: "%s" and "%s".
- 22514 — Cannot use partition groups because one or more filters reference the following view, which contains functions: "%s".
- 22515 — The publication cannot use precomputed partitions because there is at least one circular reference in the join filters specified for the articles in t…
- 22516 — The publication "%s" was defined as having dynamic filters, but it does not contain any dynamic filters.
- 22517 — The publication was defined as having no dynamic filters, but contains one or more dynamic filters.
- 22518 — Cannot use column of type image, ntext, xml, CLR type, varchar(max), nvarchar(max), or varbinary(max) in a subset or join filter for article: '%s'.
- 22519 — Cannot add a logical record relationship between tables "%s" and "%s" because a text, image, ntext, xml, varchar(max), nvarchar(max), or varbinary(max…
- 22520 — A filtering type changed for the article. Any pending or future changes made in this article by a Subscriber in a given partition will no longer be pr…
- 22521 — Unable to synchronize the row because the row was updated by a different process outside of replication.
- 22522 — Article '%s' cannot be published because it is published in another merge publication. An article that has a value of 3 for the @partition_options par…
- 22523 — An article cannot use @partition_options 2 or 3 (nonoverlapping partitions) and be a part of a logical record relationship at the same time. Check art…
- 22524 — Article '%s' is published in another merge publication, with a different value specified for the @partition_options parameter of sp_addmergearticle. T…
- 22525 — The publication "%s" cannot allow multiple subscriptions per partition if it contains articles using @partition_options = 3.
- 22526 — An invalid value was specified for %s. Valid values are 0 (none), 1 (enforced partitions), 2 (nonoverlapping partitions with multiple subscriptions pe…
- 22527 — Invalid value specified for %s. Valid values are 'day', 'days', 'dd', 'year', 'years', 'yy', 'yyyy', 'month', 'months', 'mm', 'week', 'weeks', 'wk', '…
- 22528 — Cannot use a retention period unit other than "days" for publication "%s" because the compatibility level of the publication is lower than 90. Use sp_…
- 22529 — Cannot change the retention period unit for publication "%s" because the compatibility level of the publication is lower than 90. Use sp_changemergepu…
- 22530 — Cannot update any column in article "%s" that is used in a logical record relationship clause.
- 22531 — Initialization.
- 22532 — Upload of Subscriber changes to the Publisher.
- 22533 — Download of Publisher changes to the Subscriber.
- 22534 — Character mode publication does not support partitioned tables.
- 22535 — For heterogeneous publications, the %s parameters should be specified when calling "%s".
- 22536 — The %s parameter value cannot be updated or changed for heterogeneous publications.
- 22537 — The job_login provided must match the Publisher login specified when adding the distribution Publisher (sp_adddistpublisher).
- 22538 — Only replication jobs or job schedules can be added, modified, dropped or viewed through replication stored procedures.
- 22539 — Use of parameters %s is invalid when parameter %s is set to %s.
- 22540 — Cannot change publication "%s" to use sync_mode of "character", because it contains one or more logical record relationships.
- 22541 — Cannot add a logical record relationship in publication "%s" because it uses sync_mode of "character" and could have SQL Server Compact Edition subscr…
- 22542 — Invalid value for property @subscriber_upload_options . Valid values are 0 (allow uploads), 1 (disable uploads), 2 (disable uploads prohibit subscribe…
- 22543 — When the publication property @allow_partition_realignment is set to "false", the article property @subscriber_upload_options for all articles in the …
- 22544 — Warning: The procedure sp_mergecleanupmetadata has been deprecated. In SQL Server 2000 SP1 and later, the merge agent calls sp_mergemetadataretentionc…
- 22545 — Cannot add a logical record relationship in publication "%s" because it allows Web synchronization.
- 22546 — Cannot change publication "%s" to allow Web synchronization because it contains one or more logical record relationships.
- 22547 — A concurrent snapshot is not allowed for snapshot publications.
- 22548 — Vertical partitioning is only allowed for log-based articles.
- 22549 — A shared distribution agent (%s) already exists for this subscription.
- 22550 — Cannot drop identity column "%s" from the vertical partition when identityrangemanagementoption is set to auto.
- 22551 — The type "%s" is invalid. Valid types are "merge", "tran", and "both".
- 22552 — A valid value for parameter "@resync_date_str" needs to be provided when "@resync_type" is set to 2.
- 22553 — The parameter "@resync_type" is set to "%d" but this subscription has never been successfully validated.
- 22554 — Cannot change publication "%s" to use the sync_mode of "character" because it uses a retention period unit other than "day". Use sp_changemergepublica…
- 22555 — Cannot set the retention period unit to a value other than "day" for publication "%s" because it uses the sync_mode of "character" and may have SQL Se…
- 22556 — Invalid value for the property "%s". Valid values are 1 and 0.
- 22557 — The status of the schema change could not be updated because the publication compatibility level is less than 90. Use sp_changemergepublication to set…
- 22558 — The status of the schema change could not be updated.
- 22559 — The status of the schema change must be "active" or "skipped".
- 22560 — Merge replication does not allow filters that reference dynamic functions that take one or more parameters. Check the function "%s".
- 22561 — The requested operation failed because the publication compatibility level is less than 90. Use sp_changemergepublication to set the publication_compa…
- 22562 — Cannot change the compatibility level of a publication to a value lower than the existing value.
- 22563 — contains one or more articles that do not upload changes
- 22564 — uses ddl replication
- 22565 — uses other than day as unit of retention period
- 22566 — uses logical records
- 22567 — contains one or more articles that use subscription-based or partition-based filtering
- 22568 — contains one or more articles which will not compensate for errors
- 22569 — contains one or more schema only articles
- 22570 — contains one or more articles that use automatic identity range management
- 22571 — contains one or more articles that use datatypes new in SQL Server 2000
- 22572 — contains one or more articles with a timestamp column
- 22573 — uses snapshot compression with snapshot_in_defaultfolder set to false
- 22574 — contains one or more articles that use vertical partitioning
- 22575 — When article property 'published_in_tran_pub' is set to 'true' then article property 'upload_options' has to be set to disable uploads.
- 22576 — Invalid failover_mode value of %d was specified for [%s].[%s].[%s], setting to 0 [immediate].
- 22578 — Cannot change publication "%s" to disallow use_partition_groups because it contains one or more logical record relationships. When using logical recor…
- 22579 — The subscription to publication '%s' was not found but a shared agent does exist. To specify a subscription to a publication that is replicated via a …
- 22580 — Cannot publish database '%s' because it is marked as published on a different server. Before attempting to publish this database, execute sp_replicati…
- 22581 — Article '%s' cannot be added or modified in publication '%s'. The replication of FILESTREAM columns is not supported for publications that have a 'syn…
- 22582 — Article '%s' cannot be added or modified in publication '%s'. The replication of FILESTREAM columns is not supported for publications that have a 'pub…
- 22583 — Article '%s' cannot be added or modified in publication '%s'. The replication of FILESTREAM columns is not supported for articles that have a 'schema_…
- 22584 — Warning: Values of some of the flags specified in the 'schema_option' property are not compatible with the publication's compatibility level. The modi…
- 22585 — The schema option to script out the FILESTREAM attribute on varbinary(max) columns has been enabled for article '%s'. Enabling this option after the a…
- 22586 — Column '%s' cannot be added or modified in article '%s' of publication '%s'. The DDL operatoin on hierarchyid and FILESTREAM columns is not supported …
- 22587 — Non-SQL Server Publishers and Subscribers are supported only on Windows. The platform detected is %s.
- 22588 — Publications on non-Windows platforms cannot support updateable subscriptions. The platform detected is %s. The values of @allow_sync_tran and @allow_…
- 22601 — This SQL Database can only be mirrored once across Fabric workspaces
- 22602 — This SQL Database is not supported for Fabric mirroring.
- 22603 — Fabric Mirroring feature is currently enabled only on Azure SQL DB.
- 22604 — Fabric Mirroring is not enabled on database '%s'.
- 22605 — Fabric Mirroring is not supported on Free, Basic or Standard tier Single Database (S0,S1,S2) and Database in Elastic pool with max eDTUs < 100 or max …
- 22606 — A Managed Identity is required to successfully enable Fabric Mirroring. Please configure either System Assigned Managed Identity or User Assigned Mana…
- 22607 — %ls not supported on the 'Microsoft Fabric' platform.
- 22608 — '%ls' statement is not supported on the 'Microsoft Fabric' platform.
- 22609 — Publishing the Database Reseed notification for the Fabric Mirrored Database to Fabric OneLake failed. Retry this operation later.
- 22610 — Cannot initiate the Database Reseed operation. This operation is currently not required for already reseeded Fabric Mirrored Database '%s'.
- 22611 — Parameter '%s' has an invalid value. Specify a valid value for the named parameter and retry the operation.
- 22612 — This Database Reseed operation can't be completed because Fabric Mirrored Database '%s' is no longer in Reseed state.
- 22613 — This Database Reseed operation can't be completed for Fabric Mirrored Database '%s' because Reseed operation is still in initializing phase. Please re…
- 22614 — Could not determine if the database is enabled for Fabric Mirroring, Synapse Link or Change Event Streaming.
- 22615 — Tables with '%ls' column type are not supported on the 'Microsoft Fabric' platform.
- 22616 — %ls are not supported on tables on the 'Microsoft Fabric' platform.
- 22617 — Tables with primary key that has '%ls' column type are not supported on the 'Microsoft Fabric' platform.
- 22618 — %ls cannot be used as primary key on the 'Microsoft Fabric' platform.
- 22619 — '%ls' collation is not supported on the 'Microsoft Fabric' platform.
- 22620 — Cannot perform this operation as the Fabric Mirrored database '%s' is in Reseeding state at Database level.
- 22621 — Table reseed operation on source table '%s.%s' with link table id '%s' corresponding to reseed_id '%s' is already completed. A table can only be resee…
- 22622 — Cannot re-enable mirroring for the table because table is not in Reseed state.
- 22623 — sp_rename on %ls is not supported on the 'Microsoft Fabric' platform.
- 22624 — SQL Database on the 'Microsoft Fabric' platform requires tables to have a primary key.
- 22625 — The Switch Partition Operation is currently blocked/not supported for table '%.*ls' that is Mirroring in Fabric.
- 22626 — Could not perform Database Reseed operation for Fabric Mirrored Database '%s' because mirroring is not enabled for any table groups of the Database.
- 22627 — Column name '%.*ls' contains one or more ',;={}()', space, tab or new line character(s), which are not supported on the 'Microsoft Fabric' platform.
- 22628 — Column name '%.*ls' contains one or more ',;={}()', space, tab or new line character(s), which are currently not supported for a table that is Mirrori…
- 22629 — Tables with a nonclustered primary key are not supported on Microsoft Fabric platform.
- 22630 — ALTER INDEX ALL ON table REBUILD statement is currently not supported on non-unique clustered tables on Microsoft Fabric platform.
- 22631 — ALTER PARTITION FUNCTION statement is currently not supported if function is used on heap tables on Microsoft Fabric platform.
- 22632 — ALTER TABLE REBUILD PARTITION statement is currently not supported on heap tables on Microsoft Fabric platform.
- 22633 — SHRINKDATABASE and SHRINKFILE statements are currently not supported on Microsoft Fabric platform.
- 22634 — Publishing MSSQL_System_Uniquifier column failed. Invalid uniquifier value detected. Please contact Microsoft Support for assistance.
- 22635 — Maxtrans cannot be changed for fabric mirrored database as it is managed and optimized automatically.
- 22636 — Repldone failed while performing the reseed db operation
- 22637 — Reseed db failed. The failure occurred when executing the command '%s'. The error/state returned was %d/%d: '%s'. Use the action and error to determin…
- 22638 — Publishing the create table notification to Fabric OneLake failed. Retry this operation later.
- 22639 — Aborting Fabric Link Commit Notification task for this database timed out. Retry this operation later.
- 22640 — The table could not be removed from the Change Feed. Please try the operation again shortly.
- 22641 — Disabling of mirroring for the table '%.*ls' failed. Please retry this operation later.
- 22642 — Can not enable Fabric Mirroring on a table where primary key (if there exists no primary key then applies to unique key) uses columns of the following…
- 22643 — Publishing a drop table notification to Fabric OneLake failed. Retry this operation later.
- 22644 — Unable to acquire a lock on the source table with object id '%d' because it is in use. If a user session is locking, consider terminating it or retry …
- 22645 — Fabric Mirroring cannot be enabled on a table where its primary key, or if no primary key exists, its clustered index, includes any of the following c…
- 22646 — Aborting Fabric Link Reseed Notification task for this database timed out. Retry this operation later.
- 22647 — Aborting Fabric Link Monitoring Notification task for this database timed out. Retry this operation later.
- 22648 — The stored procedure '%s' is not supported.
- 22649 — Publishing the heartbeat (KeepAlive) notification for the Fabric Mirrored Database to Fabric OneLake failed. Retry this operation later.
- 22651 — Public Network Access for logical server '%ls' is configured as SECURED_BY_PERIMETER but the destination FQDN '%ls' is not in the allowed outbound rul…
- 22652 — Public Network Access for logical server '%ls' is configured as SECURED_BY_PERIMETER, but no Network Security Perimeter (NSP) is associated. All outbo…
- 22653 — The following change feed settings aren't configurable via sp_change_feed_configure_parameters on SQL Server on Linux: %s. Configure these settings us…
- 22654 — Cannot enable Change Feed on database '%ls' because Data Recovery is enabled on this server. Combining Change Feed along with Data Recovery is current…
- 22655 — This Database Reseed operation can't be completed for Fabric Mirrored Database '%s' because Change Event Streaming is still enabled. Please disable Ch…
- 22656 — Change feed operations history becomes available only after change feed is enabled for the first time.
- 22657 — Adding a column_set column to table '%.*ls' that is enabled for Fabric Mirroring is not supported.
- 22658 — Fabric Mirroring could not find a current table version in the landing zone for table ID %d that is being actively mirrored. To resolve this, disable …
- 22659 — Change Data Store failed to truncate committed records.
- 22660 — Change Data Store failed to record a committed change.
- 22661 — Change Data Store cannot register a table because the database is not in the expected replication state.
- 22697 — Cannot enable fabric link on the database because the metadata tables are corrupted.
- 22698 — Cannot add encrypted column on table '%.*ls' in SQL Database on the 'Microsoft Fabric' platform
- 22699 — Cannot alter column '%.*ls' on table '%.*ls' in SQL Database on the 'Microsoft Fabric' platform
- 22701 — Cannot run this stored procedure as Change Feed feature is not enabled.
- 22702 — Caller is not authorized to initiate the requested action. only user with control database permission can perform this operation.
- 22703 — Could not enable Change Feed for database '%s'. Change Feed is not supported on system databases, or on a distribution database.
- 22704 — Could not enable Change Feed for database '%s'. Change Feed can not be enabled on a DB with Change Data Capture or transactional replication publishin…
- 22705 — Could not enable Change Feed for database '%s' as it is already enabled.
- 22706 — Change Feed is not enabled on database '%s'.
- 22707 — The specified database scoped credential name can't be found. It must have the identity of 'SHARED ACCESS SIGNATURE'
- 22708 — The specified database scoped credential name does not match the landing zone URL path
- 22709 — Parameter '%s' cannot be null or empty. Specify a value for the named parameter and retry the operation.
- 22710 — Could not update the metadata. The failure occurred when executing the command '%s'. The error/state returned was %d/%d: '%s'. Use the action and erro…
- 22711 — The specified table group can't be found in the current database.
- 22712 — The application lock request '%s' needed to modify Change Feed metadata was not granted. The value returned from the request was %d: -1 = timeout; -2 …
- 22713 — The value for parameter @maxtrans specified must be greater than 0.
- 22714 — Tables contained in the changefeed schema cannot be enabled for Change Feed.
- 22715 — Enabling Change Feed for a temporal history table '%ls' is not allowed.
- 22716 — Can not enable Change Feed on table '%s' or add ColumnSet column to it because Change Feed does not support ColumnSet.
- 22717 — A memory-optimized table cannot be enabled for Change Feed.
- 22718 — Change Feed is already enabled on source table '%s.%s' with link table id '%s'. A table can only be enabled once among all table groups.
- 22719 — Enabling Change Feed on a table with primary key on computed column is not allowed.
- 22720 — Enabling Change Feed on a table without primary key is not allowed.
- 22721 — Can not enable Change Feed on a table where primary key uses columns of the following types: user-defined types, geometry, geography, hierarchyid, sql…
- 22722 — Cannot enable Change Feed on a table with encrypted columns.
- 22723 — Cannot find an object ID for the Change Feed system table '%s'. Verify that the system table exists and is accessible by querying it directly. If it d…
- 22724 — Error occurred while exporting initial snapshot to landing zone.
- 22725 — Enabling Change Feed for a ledger history table '%ls' is not allowed.
- 22726 — Could not allocate memory for Change Feed operation. Verify that SQL Server has sufficient memory for all operations. Check the memory settings on the…
- 22727 — Failed to load landing zone library (%s) with error %d. Verify that SQL Server is installed properly.
- 22728 — Could not disable table because it is no longer enabled for table group.
- 22729 — Could not remove the metadata. The failure occurred when executing the command '%s'. The error/state returned was %d/%d: '%s'. Use the action and erro…
- 22730 — Could not disable Change Feed for database '%s' as it is already disabled.
- 22731 — Error occurred while publish incremental data to landing zone.
- 22732 — Invalid change feed table state.
- 22733 — Change Feed snapshot was cancelled.
- 22734 — Error occurred while process Change Feed on database %d.
- 22735 — Error occurred while update Change Feed table status for table %ld.
- 22736 — Error occurred while interacting with landing zone.
- 22737 — Can not enable Change Feed on a table where the column data type are user-defined types, geometry, geography, hierarchyid, sql_variant or timestamp
- 22738 — Can not enable Change Feed on a table with computed columns.
- 22739 — Error occurred while trying to retrieve storage info from Synapse Gateway Service with result code %d.
- 22740 — Parameter '%s' is invalid. Specify a valid value for the named parameter and retry the operation.
- 22741 — Landing Zone parameter is not valid on Azure Database.
- 22742 — Schema changes on table '%s' are not supported because it is enabled for change feed.
- 22743 — There is an issue with cleaning up metadata of some of the table groups of this database. Retry by dropping the table groups first and then disable Ch…
- 22744 — Cannot disable primary key index "%.*ls" on table "%.*ls" because the table has change feed enabled on it.
- 22745 — Cannot alter the table '%.*ls' because it has change feed enabled on it.
- 22746 — Change Feed
- 22747 — Another connection with session ID %I64d is already running 'sp_replcmds' for Change Feed in the current database.
- 22748 — Change Feed task is being aborted.
- 22749 — Cannot rename the table because it is being used for Change Feed
- 22750 — ALTER TABLE SWITCH statement failed because the partitioned destination table is enabled for Change Feed.
- 22751 — ALTER TABLE SWITCH statement failed because the partitioned source table is enabled for Change Feed.
- 22752 — Snapshot DATA_EXPORT query failed.
- 22753 — The number of tables enabled for a Change Feed table group can not exceed %d. Current number of table enabled: %d.
- 22754 — Aborting Synapse Link Capture task for this database timed out. Retry this operation later.
- 22755 — Change Feed is not supported on Free, Basic or Standard tier Single Database (S0,S1,S2) and Database in Elastic pool with max eDTUs < 100 or max vCore…
- 22756 — The elastic pool cannot lower its service tier with database max eDTUs < 100 or max vCore < 1 since one or more of its database(s) use Change Feed.
- 22757 — The database cannot lower its service tier to Standard(S0,S1,S2), Basic or Free, or move to elastic pool with database max eDTUs < 100 or max vCore < …
- 22758 — Aborting Synapse Link Commit task for table group '%s' timed out. Retry this operation later.
- 22759 — Aborting Synapse Link Snapshot task for table %ld timed out. Retry this operation later.
- 22760 — Aborting Synapse Link Publish task for partition %ld timed out. Retry this operation later.
- 22761 — Failed to cleanup previous change feed setup. Please try the operation again. If the problem persists contact Microsoft Azure Customer Support.
- 22762 — Cannot enable '%S_MSG' on '%s' because it is being used for '%S_MSG'.
- 22763 — Replication: Distribution
- 22764 — Replication: transactional or snapshot publication
- 22765 — Replication: merge publication
- 22766 — Could not enable Change Feed for database '%s'. Change Feed can not be enabled on a DB which is mirrored.
- 22767 — The value for parameter @pollinterval specified must be equal to or greater than 5.
- 22768 — Could not update change_feed_settings, the table has not been created yet.
- 22769 — Could not find table group or table with the provided table_group_id/table_id or source_schema/source_name
- 22770 — Could not return results, please provide table_group_id and table_id or source_schema and source_name
- 22771 — Error occurred while publishing data via CSVOutputter
- 22772 — environment
- 22773 — database
- 22774 — table group
- 22775 — Failed to get lock to complete in-memory objects cleanup with result: %d
- 22776 — %S_MSG (%s) can't be found in the current configuration.
- 22777 — Failure reported in %S_MSG processing
- 22778 — Failed to set database state to CLEANUP while trying to remove in-memory database objects
- 22779 — Failed to enqueue partition %d with result %d
- 22780 — Failed to enqueue work item with result %d
- 22781 — Change feed failed on processing transaction log
- 22782 — Failed to output batch data for table %d in partition %d
- 22783 — Failed to process commit work item
- 22784 — Change feed schema upgrade failed
- 22785 — Change batch was reset from unexpected state
- 22786 — Synapse workspace FQDN is not in the list of Outbound Firewall Rules on the server. Please add this to the list of Outbound Firewall Rules on your ser…
- 22787 — Change feed table group limit of %d groups exceeded
- 22788 — Could not enable Change Feed for database '%s'. Change Feed can not be enabled on a DB with delayed durability set.
- 22789 — Could not revoke changefeed user control db permission or alter changefeed user on changefeed enabled db.
- 22790 — A System Assigned Managed Identity is required to enable change feed or mirror SQL database in Fabric. Please configure System Assigned Managed Identi…
- 22791 — User cannot drop Change feed user for proper functioning of Change feed features.
- 22792 — Data masking is not supported for this column as this column is already enabled for Fabric Mirroring.
- 22793 — Fabric Mirroring is not supported on this table as the primary key column contains masking functions.
- 22794 — Failed to set table version during snapshot operation
- 22795 — Enabling Change Feed for an external table '%s' is not allowed.
- 22796 — Error %d occurred while interacting with the destination.
- 22797 — Cannot enable Synapse Link on the database as Synapse Link has been discontinued in this version of SQL Server. Use Mirroring in Fabric instead.
- 22798 — Synapse Link is now discontinued on this version of SQL Server. Disabling Synapse Link on the database.
- 22799 — Fabric Mirroring cannot be enabled on database '%s' due to the reason: %S_MSG
- 22801 — Starting the Change Data Capture Collection Agent job. To report on the progress of the operation, query the sys.dm_cdc_log_scan_sessions dynamic mana…
- 22802 — Starting the Change Data Capture Cleanup Agent job using low watermark %s.
- 22803 — Change Data Capture has scanned the log from LSN{%s} to LSN{%s}, %d transactions with %d commands have been extracted. To report on the progress of th…
- 22804 — Change Data Capture cannot proceed with the job-related action because transactional replication is enabled on database %s but Distributor information…
- 22805 — For more information, query the sys.dm_cdc_errors dynamic management view.
- 22806 — The originator ID '%s' is not valid. You must specify a non-zero ID that has never been used in the topology.
- 22807 — The publication property '%s' cannot be modified because the peer-to-peer publication '%s' is not enabled for conflict detection. To enable the public…
- 22808 — Cannot execute procedure '%s'. Publication '%s' must be enabled for peer-to-peer replication before you execute this procedure. To enable the publicat…
- 22809 — The existing conflict table '%s' was dropped.
- 22810 — The @action parameter value is not valid. Valid values are 'enable' and 'disable'.
- 22811 — The roundtrip time-out must be greater than 0.
- 22812 — The roundtrip '%s' finished with timeout: %d seconds.
- 22813 — The topology contains peer node versions that do not support conflict detection. To use conflict detection, ensure that all nodes in the topology are …
- 22814 — The topology contains a duplicate originator ID. To use conflict detection, the originator ID must be unique across the topology.
- 22815 — A conflict of type '%s' was detected at peer %d between peer %d (incoming), transaction id %s and peer %d (on disk), transaction id %s for Table '%s' …
- 22816 — The qualified table name '%s' is too long to be enabled for peer-to-peer conflict detection.
- 22817 — %s has %s.
- 22818 — A delete-delete conflict was detected and resolved. The row could not be deleted from the peer since the row does not exist. The incoming delete was s…
- 22819 — A delete-update conflict between peer %d (incoming) and peer %d (on disk) was detected and could not be resolved automatically. The incoming delete wa…
- 22820 — A delete-update conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming delete was applied to peer %d.
- 22821 — An update-update conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming update was skipped by peer %d.
- 22822 — An update-update conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming update was applied to peer %d.
- 22823 — An update-delete conflict was detected and unresolved. The row could not be updated since the row does not exist. The incoming update was skipped. Che…
- 22824 — An insert-insert conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming insert was skipped by peer %d.
- 22825 — An insert-insert conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming insert was applied to peer %d.
- 22827 — Peer-to-peer conflict detection alert
- 22828 — The publication '%s' was already %s for peer-to-peer conflict detection.
- 22829 — The command %s failed. The values specified for the @ins_cmd , @del_cmd or @upd_cmd cannot be appended with schema name %s within the size limit %d.
- 22830 — Could not update the metadata that indicates database %s is enabled for Change Data Capture. The failure occurred when executing the command '%s'. The…
- 22831 — Could not update the metadata that indicates database %s is not enabled for Change Data Capture. The failure occurred when executing the command '%s'.…
- 22832 — Could not update the metadata that indicates table %s is enabled for Change Data Capture. The failure occurred when executing the command '%s'. The er…
- 22833 — Could not update the metadata that indicates table %s is not enabled for Change Data Capture. The failure occurred when executing the command '%s'. Th…
- 22834 — Could not modify the the verbose logging status for table %s. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. U…
- 22835 — Could not update the metadata for database %s to indicate that a Change Data Capture job has been dropped. The failure occurred when executing the com…
- 22836 — Could not update the metadata for database %s to indicate that a Change Data Capture job has been added. The failure occurred when executing the comma…
- 22837 — Could not delete table entries or drop objects associated with capture instance '%s'. The failure occurred when executing the command '%s'. The error …
- 22838 — All columns of a CDC unique index must be defined as NOT NULL. Index '%s' selected as the CDC unique index for source table '%s.%s' does not meet this…
- 22840 — The application lock request '%s' needed to modify Change Data Capture metadata was not granted. The value returned from the request was %d: -1 = time…
- 22841 — Could not upgrade the metadata for database '%s' that is enabled for Change Data Capture. The failure occurred when executing the action '%s'. The err…
- 22842 — ALTER TABLE SWITCH statement failed because the partitioned destination table is enabled for Change Data Capture and does not have @allow_partition_sw…
- 22843 — ALTER TABLE SWITCH statement failed because the partitioned source table is enabled for Change Data Capture and does not have @allow_partition_switch …
- 22844 — The '%s' option must be either 1 or 0.
- 22845 — Cannot enable change data capture in this edition of SQL Server.
- 22850 — The threshold value specified for the Change Data Capture cleanup process must be greater than 0. When creating or modifying the cleanup job, specify …
- 22851 — Could not update cdc.change_tables to indicate a change in the low water mark for database %s.
- 22852 — Could not delete change table entries made obsolete by a change in one or more low water marks for capture instances of database %s. The failure occur…
- 22853 — Could not delete obsolete entries in the cdc.lsn_time_mapping table for database %s. The failure occurred when executing the command '%s'. The error r…
- 22854 — Can not enable Change Data Capture on table '%s' or add ColumnSet column to it because CDC does not support ColumnSet.
- 22855 — Warning: The @allow_partition_switch parameter is set to 1. Change data capture will not track changes introduced in the table resulting from a partit…
- 22856 — Warning: The @allow_partition_switch parameter is set to 0. ALTER TABLE ... SWITCH PARTITION statement will be disallowed on this partitioned table. R…
- 22857 — Warning: The @allow_partition_switch parameter must be 1 for tables that are not partitioned. The explicit setting of the parameter to 0 was ignored. …
- 22858 — Unable to add entries to the Change Data Capture LSN time mapping table to reflect dml changes applied to the tracked tables. Refer to previous errors…
- 22859 — Log Scan process failed in processing log records. Refer to previous errors in the current session to identify the cause and correct any associated pr…
- 22860 — Log scan process failed in processing a ddl log record. Refer to previous errors in the current session to identify the cause and correct any associat…
- 22861 — Unable to upgrade database '%s'. Error '%d' was raised: '%s'. Use the reported error to determine the cause of the failure and then execute sys.sp_cdc…
- 22862 — The database snapshot '%s' does not exist. Correct the parameter value and resubmit the request.
- 22863 — Failed to insert rows into Change Data Capture change tables. Refer to previous errors in the current session to identify the cause and correct any as…
- 22864 — The call to sp_MScdc_capture_job by the Capture Job for database '%s' failed. Look at previous errors for the cause of the failure.
- 22865 — The number of columns in the index '%s', used as the unique row identifier to support net changes for table '%s'.'%s', exceeds the limit of 14 columns…
- 22866 — The value returned by %S_MSG is %I64d.
- 22867 — Total rows deleted: %I64u.
- 22868 — Cleanup Watermark = %I64u
- 22869 — Internal Change Tracking table name : %s
- 22870 — Deleted %I64u rows from %s
- 22871 — Change Data Capture is not supported on Free, Basic or Standard tier Single Database (S0,S1,S2) and Database in Elastic pool with max eDTUs < 100 or m…
- 22872 — The elastic pool cannot lower its service tier with database max eDTUs < 100 or max vCore < 1 since one or more of its database(s) use Change Data Cap…
- 22873 — The database cannot lower its service tier to Standard(S0,S1,S2), Basic or Free, or move to elastic pool with database max eDTUs < 100 or max vCore < …
- 22874 — Cannot set @enable_extended_ddl_handling parameter to 1 as this feature is not enabled.
- 22875 — Capture instance name '%s' exceeds the length limit of 78 characters when @enable_extended_ddl_handling is enabled. Specify a name that satisfies the …
- 22876 — One capture instance already exist with DDL handling enabled for source table '%s.%s'. A table can have only one capture instance with DDL handling en…
- 22877 — All columns are not captured for source table '%s.%s' when using DDL handling feature. DDL handling feature is only supported when all columns are cap…
- 22878 — The @p2p_conflictdetection_policy parameter value is not valid. Valid values are 'originatorid' and 'lastwriter'.
- 22879 — Peer-to-peer publications with last writer conflict detection policy only supports CALL or SCALL command type for @upd_cmd . Change the value for para…
- 22880 — An insert-insert conflict between peer %d (incoming) with commit datetime value of '%s' and peer %d (on disk) with commit datetime value of '%s' was d…
- 22881 — A conflict of type '%s' was detected at peer %d between peer %d (incoming), transaction id %s, commit datetime '%s' and peer %d (on disk), transaction…
- 22882 — An update-update conflict between peer %d (incoming) with commit dateime value of '%s' and peer %d (on disk) with commit datetime value of '%s' was de…
- 22883 — An update-update conflict between peer %d (incoming) with commit datetime value of '%s' and peer %d (on disk) with commit datetime value of '%s' was d…
- 22884 — An delete-update conflict between peer %d (incoming) with commit datetime value of '%s' and peer %d (on disk) with commit datetime value of '%s'was de…
- 22885 — An insert-insert conflict between peer %d (incoming) with commit datetime value of '%s' and peer %d (on disk) with commit datetime value of '%s' was d…
- 22886 — An update-delete conflict was detected. The row could not be updated since the row does not exist. The incoming update was skipped.
- 22887 — Could not enable Change Data Capture for database '%s'. Change Data Capture cannot be enabled on a DB with Change Feed enabled.
- 22888 — Could not alter captured column of a CDC tracked table with character/binary/unicode as target data type with ansi warnings turned off.
- 22889 — Warning: Unable to get database version for the subscription database '%s'. The sp_replmonitorsubscriptionpendingcmds may report incorrect number of p…
- 22890 — Could not remove cdc user from db_owner role or alter cdc user on cdc enabled db.
- 22891 — Could not enable '%S_MSG' for database '%s'. '%S_MSG' cannot be enabled on a DB with delayed durability set.
- 22892 — Could not enable delayed durability on DB. Delayed durability cannot be enabled on a DB while '%S_MSG' is enabled.
- 22893 — Change data capture scan failed on processing transaction log
- 22894 — sp_cdc_disable_db_internal caught an exception in try block when executing command : '%s'. The error returned was %d: '%s'
- 22895 — Could not drop cdc user. CDC user is required for proper working of CDC.
- 22896 — sp_cdc_disable_db caught an exception in try block when executing command : '%s'. The error returned was %d: '%s'
- 22897 — Enabling Change Data Capture for an external table '%s' is not allowed.
- 22898 — Could not enable Change Data Capture for database '%ls'. Change Data Capture cannot be enabled on a database configured for Change Event Streaming.
- 22899 — Could not run Change Data Capture sprocs on database '%ls' because Data Recovery is enabled. To configure Change Data Capture, disable Data Recovery, …
- 22901 — The database '%s' is not enabled for Change Data Capture. Ensure that the correct database context is set and retry the operation. To report on the da…
- 22902 — Caller is not authorized to initiate the requested action. Sysadmin privileges are required.
- 22903 — Another connection with session ID %I64d is already running 'sp_replcmds' for Change Data Capture in the current database.
- 22904 — Caller is not authorized to initiate the requested action. DBO privileges are required.
- 22905 — Database '%s' is already enabled for Change Data Capture. Ensure that the correct database context is set, and retry the operation. To report on the d…
- 22906 — The database '%s' cannot be enabled for Change Data Capture because a database user named 'cdc' or a schema named 'cdc' already exists in the current …
- 22907 — Parameter @role_name cannot be empty. Specify a value for @role_name and retry the operation. Supply null as the value if no role is to be used to gat…
- 22908 — Could not create the Change Data Capture objects in database '%s'. Refer to previous errors in the current session to identify the cause and correct a…
- 22909 — Failed to cleanup the cdc.lsn_time_mapping table in database '%s' when the last database table enabled for Change Data Capture was disabled. Refer to …
- 22910 — The cleanup request for database '%s' failed. The database is not enabled for Change Data Capture.
- 22911 — The capture job cannot be used by Change Data Capture to extract changes from the log when transactional replication is also enabled on the same datab…
- 22912 — sp_repldone failed
- 22913 — Could not drop the Change Data Capture objects in database '%s'. Refer to previous errors in the current session to identify the cause and correct any…
- 22914 — Only members of the sysadmin or db_owner or db_ddladmin roles can perform this operation when Change Data Capture is enabled for a database.
- 22915 — sp_replflush failed
- 22916 — Could not grant SELECT permission for the change enumeration functions for capture instance '%s' and source table '%s.%s' for the specified role. Refe…
- 22917 — sp_replhelp failed
- 22918 — One or more columns in the list of included columns was not a captured column of the change table %s.
- 22919 — One or more columns in the list of columns needing update flags was not a captured column of the change table %s.
- 22920 — The named capture instance %s does not exist for database %s.
- 22921 — Unable to generate scripts for all capture instances that the caller is authorized to access. To generate all such scripts, the parameters @column_lis…
- 22923 — Could not compute the new low endpoint for database '%s' from retention %d. Refer to previous errors in the current session to identify the cause and …
- 22924 — Could not clean up change tables for database '%s'. A failure occurred when attempting to clean up the database change tables based upon the current r…
- 22925 — The number of columns captured by capture instance '%s' exceeds the maximum allowed number: %d. Use the @captured_columns_list parameter to specify a …
- 22926 — Could not create a capture instance because the capture instance name '%s' already exists in the current database. Specify an explicit unique name for…
- 22927 — Capture instance name '%s' exceeds the length limit of 100 characters. Specify a name that satisfies the length constraint.
- 22928 — Index name '%s' is not an index for table '%s.%s'. Specify a valid index name for the table.
- 22929 — Index '%s' must be either a primary key or a unique index for table '%s.%s'. Specify an index that meets at least one of these requirements.
- 22930 — Could not locate '%s' as a column of source table '%s.%s'. Specify a valid column name.
- 22931 — Source table '%s.%s' does not exist in the current database. Ensure that the correct database context is set. Specify a valid schema and table name fo…
- 22932 — Capture instance name '%s' is invalid. Specify a valid name. See the topic 'Identifiers' in SQL Server Books Online for object name rules.
- 22933 — Could not drop change table objects for capture instance '%s'. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. …
- 22938 — Role name '%s' is invalid. Specify a valid name. See the topic 'Identifiers' in SQL Server Books Online for object name rules.
- 22939 — The parameter @supports_net_changes is set to 1, but the source table does not have a primary key defined and no alternate unique index has been speci…
- 22940 — Could not remove DDL history entries in the Change Data Capture metadata for capture instance '%s' and source table '%s.%s'. Refer to previous errors …
- 22941 — Could not retrieve column information for index '%s' of source table '%s.%s'. Refer to previous errors in the current session to identify the cause an…
- 22942 — Columns specified in the captured column list could not be mapped to columns in source table '%s.%s'. Verify that the columns specified in the paramet…
- 22943 — Columns used to uniquely identify a row for net change tracking must be included in the list of captured columns. Add either the primary key columns o…
- 22944 — Could not create the specified database role '%s' for gating access to change table '%s.%s'. Refer to previous errors in the current session to identi…
- 22945 — Could not add column information to the cdc.index_columns system table for the specified index for source table '%s.%s. Refer to previous errors in th…
- 22946 — Could not add column information to the cdc.captured_columns system table for source table '%s.%s'. Refer to previous errors in the current session to…
- 22947 — Could not create the change table for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session to identify the …
- 22948 — Could not create the change enumeration functions for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session …
- 22949 — Could not update the Change Data Capture metadata for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session …
- 22950 — Could not remove index column entries in the Change Data Capture metadata for capture instance '%s' and source table '%s.%s'. Refer to previous errors…
- 22951 — Could not remove captured column entries in the Change Data Capture metadata for capture instance '%s' and source table '%s.%s'. Refer to previous err…
- 22952 — Could not drop Change Data Capture objects created for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session…
- 22953 — Could not remove Change Data Capture metadata for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session to i…
- 22954 — Could not cleanup change tables for capture instance '%s' using low end point %s. Refer to previous errors in the current session to identify the caus…
- 22955 — Could not obtain the maximum LSN for the database from function 'sys.fn_cdc_get_max_lsn'. Refer to previous errors in the current session to identify …
- 22956 — Could not obtain the minimum LSN of the change table associated with capture instance '%s' from function 'sys.fn_cdc_get_min_lsn'. Refer to previous e…
- 22957 — LSN %s, specified as the new low end point for the change table associated with capture instance '%s', is not within the Change Data Capture timeline …
- 22958 — Could not create the function to query for all changes for capture instance '%s'. Refer to previous errors in the current session to identify the caus…
- 22959 — Could not create the function to query for net changes for capture instance '%s'. Refer to previous errors in the current session to identify the caus…
- 22960 — Change data capture instance '%s' has not been enabled for the source table '%s.%s'. Use sys.sp_cdc_help_change_data_capture to verify the capture ins…
- 22961 — Could not create a nonclustered index to support net change tracking for capture instance '%s' and source table '%s.%s'. Refer to previous errors in t…
- 22962 — Two capture instances already exist for source table '%s.%s'. A table can have at most two capture instances. If the current tracking options are not …
- 22963 — Parameter '%s' cannot be null or empty. Specify a value for the named parameter and retry the operation.
- 22964 — LSN %s, specified as the new low end point for change table cleanup must represent the start_lsn value of a current entry in the cdc.lsn_time_mapping …
- 22965 — A quoted column in the column list is not properly terminated. Verify that columns are correctly delimited and retry the operation. For more informati…
- 22966 — Could not create table dbo.systranschemas in database '%s'. Refer to previous errors in the current session to identify the cause and correct any asso…
- 22967 — Could not create a clustered index for table dbo.systranschemas in database '%s'. Refer to previous errors in the current session to identify the caus…
- 22968 — Could not create DDL trigger '%s' when enabling Change Data Capture for database '%s'. Additional messages in the SQL Server error log and operating s…
- 22969 — Update mask evaluation will be disabled in net_changes_function because the CLR configuration option is disabled.
- 22970 — The value for parameter @maxscans specified for the Change Data Capture job must be greater than 0.
- 22971 — Could not allocate memory for the log reader history cache. Verify that SQL Server has sufficient memory for all operations. Check the physical and vi…
- 22972 — When calling stored procedure [sys].sp_cdc_help_change_data capture, if either @source_schema or @source_name is non-null and non-empty, the other par…
- 22973 — The specified filegroup '%s' is not a valid filegroup for database '%s'. Specify a valid existing filegroup or create the named filegroup, and retry t…
- 22974 — Tables contained in the cdc schema cannot be enabled for Change Data Capture.
- 22975 — Source table '%s' contains one of the following reserved column names: __$start_lsn, __$end_lsn, __$seqval, __$operation, and __$update_mask. To enabl…
- 22976 — Could not alter column '%s' of change table '%s' in response to a data type change in the corresponding column of the source table '%s'. The Change Da…
- 22977 — Unable to update DDL history information to reflect columns changes applied to the tracked table associated with change table '%s'. Refer to previous …
- 22978 — Could not update the cdc.captured_columns entry for column '%s' of change table '%s' to reflect a data type change in the corresponding column of the …
- 22979 — The unique index '%s' on table '%s' is used by Change Data Capture. The constraint using this index cannot be dropped or disabled.
- 22980 — The unique index '%s' on table '%s.%s' is disabled and cannot be used as a unique index by Change Data Capture. Enable the index.
- 22981 — Object does not exist or access is denied.
- 22982 — Could not create internal stored procedures used to populate the change table for capture instance '%s' and source table '%s.%s'. Refer to previous er…
- 22983 — The unique index '%s' on source table '%s' is used by Change Data Capture. To alter or drop the index, you must first disable Change Data Capture on t…
- 22984 — An error occurred while waiting on the log reader history cache event. This error is reported by the internal task scheduling and might be transient. …
- 22985 — Change data capture has not been enabled for source table '%s.%s'. Specify the name of a table enabled for Change Data Capture. To report on the table…
- 22986 — Could not allocate memory for Change Data Capture population. Verify that SQL Server has sufficient memory for all operations. Check the physical and …
- 22987 — Change Data Capture population failed writing blob data for one or more large object columns. Verify that SQL Server has sufficient memory for all ope…
- 22988 — This instance of SQL Server is the %s. Change data capture is only available in the Enterprise, Developer, Enterprise Evaluation, and Standard edition…
- 22989 — Could not enable Change Data Capture for database '%s'. Change data capture is not supported on system databases, or on a distribution database.
- 22990 — The value specified for the parameter @pollinginterval cannot exceed 24 hours or be less than 0. Specify a polling interval (in seconds) that is less …
- 22991 — The value specified for the parameter @maxtrans must be greater than 0.
- 22992 — The specified @job_type , %s, is not supported. The value specified for the parameter @job_type must be N'capture' to indicate a capture job, or N'cle…
- 22993 — The Change Data Capture job table containing job information for database '%s' cannot be found in the msdb system database. Run the stored procedure '…
- 22994 — The retention value specified for the Change Data Capture cleanup process must be greater than 0 and less than or equal to 52594800. When creating or …
- 22995 — A value for the parameter @retention cannot be specified when the job type is 'capture'. Specify NULL for the parameter, or omit the parameter from th…
- 22996 — When adding or modifying the CDC cleanup job, @pollinginterval , @maxtrans , @maxscans , and @continuous may not be assigned non-null values.
- 22997 — The Change Data Capture '%s' job does not exist in the system table 'msdb.dbo.cdc_jobs'. Use the stored procedure 'sys.sp_cdc_add_job' to add the Chan…
- 22998 — The value specified for the parameter @continuous must be 0 or 1.
- 22999 — The value specified for the parameter @pollinginterval must be null or 0 when the stored procedure 'sys.sp_cdc_scan' is not being run in continuous mo…
- 23003 — The WinFS share permissions have become corrupted {Error: %ld}. Please try setting the share permissions again.
- 23100 — Invalid input parameter(s).
- 23101 — Access is denied.
- 23102 — Item does not exist {ItemId: %ls}.
- 23103 — Folder already exists {ItemId: %ls}.
- 23104 — Folder does not exist {ItemId: %ls}.
- 23105 — Operation violates hierarchical namespace uniqueness.
- 23106 — Container is not empty {ItemId: %ls}.
- 23107 — Item cannot be copied onto itself.
- 23108 — Scoping path does not exist or is invalid.
- 23109 — Container does not exist.
- 23110 — No more items to enumerate.
- 23111 — Item does not exist in the given scope {ItemId: %ls, Scope: %ls}.
- 23112 — Transaction not in active state.
- 23113 — Item either does not exist or it is not a file-backed one.
- 23114 — Sharing violation.
- 23115 — Transaction bindtoken must be null when called within the context of a transaction.
- 23116 — Inconsistent StreamSize and/or AllocationSize data {ItemId: %ls}.
- 23117 — File-backed item does not exist {ItemId: %ls}.
- 23118 — Either %ls, or %ls, or both must have a value. These parameters cannot be both set to NULL.
- 23119 — The index specified by the @index_id is an XML Index. Omit the @data_compression parameter or set it to NULL, XML Indexes do not support data compress…
- 23200 — ItemId of folder '%ls' not found.
- 23201 — Share '%ls' does not exist in Catalog.
- 23202 — Could not delete Share '%ls' in Catalog.