HomeSQL ServerSQL Server Error Messages 14001 to 15000

SQL Server Error Messages 14001 to 15000

In this post, we’ll list out the SQL Server Error Messages from the error codes 14001 to 15000 and references to the detailed post to know more about the errors and how to fix them when using SQL Server as database in your application.

SQL Server Error Messages 14001 to 15000

ErrorCodeSeverityErrorMessage
1400216Could not find the ‘Sync’ subsystem with the task ID %ld.
1400316You must supply a publication name.
1400416%s must be in the current database.
1400516Cannot drop the publication because at least one subscription exists for this publication. Drop all subscriptions to the publication before attempting to drop the publication. If the problem persists, replication metadata might be incorrect; consult Books Online for troubleshooting information.
1400616Could not drop the publication.
1400811There are no publications.
1400911There are no articles for publication ‘%s’.
1401016The remote server ‘%s’ is not defined as a subscription server. Ensure you specify the server name rather than a network alias.
1401116Unable to mark server ‘%s’ as a non SQL Server subscriber.
1401216The @status parameter value must be either ‘active’ or ‘inactive’.
1401316This database is not enabled for publication.
1401416The synchronization method (@sync_method) must be ‘[bcp] native’, ‘[bcp] character’, ‘concurrent’, ‘concurrent_c’, ‘database snapshot’, or ‘database snapshot character’.
1401516The replication frequency (@repl_freq) must be either ‘continuous’ or ‘snapshot’.
1401616The publication ‘%s’ already exists.
1401716Invalid @restricted parameter value. Valid options are ‘true’ or ‘false’.
1401816Could not create the publication.
1401916The @operation parameter value must be either add, drop, or alter.
1402016Could not obtain the column ID for the specified column. Schema replication failed.
1402116The column was not added correctly to the article.
1402216The @property parameter value must be either  ‘description’, ‘sync_object’, ‘type’, ‘ins_cmd’, ‘del_cmd’, ‘upd_cmd’, ‘filter’, ‘dest_table’, ‘dest_object’, ‘creation_script’, ‘pre_creation_cmd’, ‘status’, ‘schema_option’, or ‘destination_owner’.
1402316The type must be ‘[indexed view ]logbased[ (manualview|manualfilter|manualboth)]’, ‘[serializable ]proc exec’,  or ‘(view|indexed view|proc|func|aggregate|synonym) schema only’.
1402416The value of property ‘subscriber_provider’ cannot be NULL.
1402510Article update successful.
1402616The value of property ‘subscriber_type is not a supported heterogeneous subscriber type.  The value must be 1 (ODBC subscriber), or 3 (OLEDB subscriber).
1402711%s does not exist in the current database.
1402816Only user tables, materialized views, and stored procedures can be published as ‘logbased’ articles.
1402916The vertical partition switch must be either ‘true’ or ‘false’.
1403016The article ‘%s’ exists in publication ‘%s’.
1403116User tables and views are the only valid synchronization objects.
1403216The value of parameter %s cannot be ‘all’. It is reserved by replication stored procedures.
1403316Could not change replication frequency because there are active subscriptions on the publication.
1403416The publication name (@publication) cannot be the keyword ‘all’.
1403516The replication option ‘%s’ of database ‘%s’ has already been set to true.
1403616Could not enable database for publishing.
1403716The replication option ‘%s’ of database ‘%s’ has been set to false.
1403816Could not disable database for publishing.
1403916Could not construct column clause for article view. Reduce the number of columns or create the view manually.
1404016The server ‘%s’ is already a Subscriber.
1404116The ‘%s’ property can only be changed if the publication is enabled for heterogeneous subscriptions.  The publication is not enabled.
1404216Could not create Subscriber.
1404316The parameter %s passed to stored procedure %s cannot be NULL.
1404416Unable to clear subscriber status for the server.
1404516Unable to update subscriber_type in MSdistribution_agents table.
1404616Could not drop article. A subscription exists on it.
1404716Could not drop %s.
1404816The server ‘%s’ is not a Subscriber.
1404916Stored procedures for replication are the only objects that can be used as a filter.
1405011No subscription is on this publication or article.
1405116The parameter value must be ‘sync_type’ or ‘dest_db’.
1405216The @sync_type parameter value must be “automatic”, “none”, “replication support only”, “initialize with backup”, or “initialize from lsn”.
1405316The subscription could not be updated at this time.
1405410The subscription was updated successfully.
1405510The subscription does not exist.
1405616The subscription could not be dropped at this time.
1405716The subscription could not be created.
1405816Cannot create the subscription because the subscription already exists in the subscription database. Only one subscription to the same publication is allowed in each subscription database. Drop the subscription and add it again if necessary. If the problem persists, replication metadata might be incorrect; see Books Online for troubleshooting information.
1405916Materialized view articles cannot be created for publications with the properties allow_sync_tran, allow_queued_tran, or allow_dts.
1406016Subscriber parameters specifying provider properties must be NULL for SQL Server subscribers.
1406116The @pre_creation_cmd parameter value must be ‘none’, ‘drop’, ‘delete’, or ‘truncate’.
1406210The Subscriber was dropped.
1406311The remote server does not exist or has not been designated as a valid Subscriber.
1406410Found generation stuck at genstatus 4.
1406516The @status parameter value must be ‘initiated’, ‘active’, ‘inactive’, or ‘subscribed’.
1406616The previous status must be ‘active’, ‘inactive’, or ‘subscribed’.
1406716The status value is the same as the previous status value.
1406816The subscription status of the object could not be changed.
1406916Could not update sysarticles. The subscription status could not be changed.
1407016Could not update the distribution database subscription table. The subscription status could not be changed.
1407116Could not find the Distributor or the distribution database for the local server. The Distributor may not be installed, or the local server may not be configured as a Publisher at the Distributor.
1407416The server ‘%s’ is already listed as a Publisher.
1407516The Publisher could not be created at this time.
1407616Could not grant replication login permission to ‘%s’.
1407710The publication was updated successfully.
1407816The parameter must be ‘description’, ‘taskid’, ‘sync_method’, ‘status’, ‘repl_freq’, ‘restricted’, ‘retention’, ‘immediate_sync’, ‘enabled_for_internet’, ‘allow_push’, ‘allow_pull’, ‘allow_anonymous’, or ‘retention’.
1408016The remote server “%s” does not exist, or has not been designated as a valid Publisher, or you may not have permission to see available Publishers.
1408516The Subscriber information could not be obtained from the Distributor.
1408816The table ‘%s’ must have a primary key to be published using the transaction-based method.
1408916The clustered index on materialized view ‘%s’ may not contain nullable columns if it is to be published using the transaction-based method.
1409016Error evaluating article synchronization object after column drop. The filter clause for article ‘%s’ must not reference the dropped column.
1409116The @type parameter passed to sp_helpreplicationdb must be either ‘pub’ or ‘sub’.
1409216Could not change article because there is an existing subscription to the article.
1409316Cannot grant or revoke access directly on publication ‘%s’ because it uses the default publication access list.
1409416Could not subscribe to article ‘%s’ because heterogeneous Subscriber ‘%s’ does not support the @pre_creation_cmd parameter value ‘truncate’.
1409516The value for the @sync_method parameter is not valid. Could not subscribe to publication ‘%s’ because non-SQL Server Subscriber ‘%s’ only supports values of  ‘character’, ‘bcp character’, ‘concurrent_c’, and ‘database snapshot character’ for the @sync_method parameter.
1409616The path and name of the table creation script must be specified if the @pre_creation_cmd parameter value is ‘drop’.
1409716The ‘status’ value must be ‘no column names’, ‘include column names’, ‘string literals’, ‘parameters’, ‘DTS horizontal partitions’ or ‘no DTS horizontal partitions’.
1409816Cannot drop Distribution Publisher ‘%s’. The remote Publisher is using ‘%s’ as Distributor. Disable publishing at the Publisher before attempting to drop this relationship.
1409916The server ‘%s’ is already defined as a Distributor. To reconfigure the server as a Distributor, you must first uninstall the exisiting Distributor. Use the stored procedure sp_dropdistributor, or use the Disable Publishing and Distribution Wizard.
1410016Specify all articles when subscribing to a publication using concurrent snapshot processing.
1410116The publication ‘%s’ already has a Snapshot Agent defined.
1410216Specify all articles when unsubscribing from a publication using concurrent snapshot processing.
1410316Invalid “%s” value. Valid values are “publisher”, “subscriber”, or “both”.
1410510You have updated the distribution database property ‘%s’ successfully.
1410616Distribution retention periods must be greater than or equal to 0.
1410710The @max_distretention value must be larger than the @min_distretention value.
1410810Removed %ld history records from %s.
1410910The @security_mode parameter value must be 0 (SQL Server Authentication) or 1 (Integrated Authentication).
1411016For stored procedure articles, the @property parameter value must be ‘description’, ‘dest_table’, ‘dest_object’, ‘creation_script’, ‘pre_creation_cmd’, ‘schema_option’, or ‘destination_owner’.
1411116The @pre_creation_cmd parameter value must be ‘none’ or ‘drop’.
1411216This procedure can be executed only against table-based articles.
1411316Could not execute ‘%s’. Check ‘%s’ in the install directory.
1411416The server ‘%s’ is not configured as a Distributor.
1411516The property parameter value must be %s.
1411716‘%s’ is not configured as a distribution database.
1411816A stored procedure can be published only as a ‘serializable proc exec’ article, a ‘proc exec’ article, or a ‘proc schema only’ article.
1411916Could not add the distribution database ‘%s’. This distribution database already exists.
1412016Could not drop the distribution database ‘%s’. This distributor database is associated with a Publisher.
1412116Could not drop the Distributor ‘%s’. This Distributor has associated distribution databases.
1412216The @article parameter value must be ‘all’ for immediate_sync publications.
1412316The subscription @sync_type parameter value ‘manual’ is no longer supported.
1412416A publication must have at least one article before a subscription to it can be created.
1412616You do not have the required permissions to complete the operation.
1412816Invalid @subscription_type parameter value. Valid options are ‘push’ or ‘pull’.
1412916The @status parameter value must be NULL for ‘automatic’ sync_type when you add subscriptions to an immediate_sync publication.
1413516There is no subscription on Publisher ‘%s’, publisher database ‘%s’, publication ‘%s’.
1413616The keyword ‘all’ is reserved by replication stored procedures.
1413716The @value parameter value must be either ‘true’ or ‘false’.
1413816Invalid option name ‘%s’.
1413916The replication system table ‘%s’ already exists.
1414316Cannot drop Distributor Publisher ‘%s’. There are Subscribers associated with it in the distribution database ‘%s’.
1414416Cannot drop Subscriber ‘%s’. There are subscriptions for it in the publication database ‘%s’.
1414616The article parameter ‘@schema_option’ cannot be NULL.
1414716Restricted publications are no longer supported.
1414816Invalid ‘%s’ value. Valid values are ‘true’ or ‘false’.
1414910Removed %ld replication history records in %s seconds (%ld row/secs).
1415010Replication-%s: agent %s succeeded. %s
1415118Replication-%s: agent %s failed. %s
1415210Replication-%s: agent %s scheduled for retry. %s
1415310Replication-%s: agent %s warning. %s
1415416The Distributor parameter must be ‘@heartbeat_interval’.
1415516Invalid article ID specified for procedure script generation.
1415616The custom stored procedure calling the format for the %s command specified in the article definition does not match the %s format.
1415710The subscription created by Subscriber ‘%s’ to publication ‘%s’ has expired and has been dropped.
1415810Replication-%s: agent %s: %s.
1415916Could not change property ‘%s’ for article ‘%s’ because there is an existing subscription to the article.
1416010One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and change the expiration threshold value if necessary.
1416110The threshold [%s:%s] for the publication [%s] has been set. Make sure that the logreader and distribution agents are running and can match the latency requirement.
1416210One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and adjust the threshold value if necessary.
1416310One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and adjust the threshold value if necessary.
1416410One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and adjust the threshold value if necessary.
1416510One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and adjust the threshold value if necessary.
1416610Disable publishing ignored error msg %d, severity %d, state %d: %s.
1416710Subscription expiration
1416810Transactional replication latency
1416910Long merge over dialup connection
1417010Long merge over LAN connection
1417110Slow merge over LAN connection
1417210Slow merge over dialup connection
1417318Replication-%s: agent initialization failed. %s
1419610The agent has never been run.
1419710Value of %s parameter should be in the set %s
1419810The value of the %s parameter should be in the range %s. Verify that the specified parameter value is correct.
1419910The specified job ‘%s’ is not created for maintenance plans. Verify that the job has at least one step calling xp_sqlmaint.
1420016The specified ‘%s’ is invalid.
14201100 (all steps) ..
1420210before or after @active_start_time
1420310sp_helplogins [excluding Windows NT groups]
14204100 (non-idle), 1 (executing), 2 (waiting for thread), 3 (between retries), 4 (idle),  5 (suspended), 7 (performing completion actions)
1420510(unknown)
14206100..n seconds
1420710-1 [no maximum], 0..n
14208101..7 [1 = E-mail, 2 = Pager, 4 = NetSend]
14209100..127 [1 = Sunday .. 64 = Saturday]
1421010notification
1421110server
1421210(all jobs)
1421310Core Job Details:
1421410Job Steps:
1421510Job Schedules:
1421610Job Target Servers:
1421710SQL Server Warning: ‘%s’ has performed a forced defection of TSX server ‘%s’. Run sp_delete_targetserver at the MSX in order to complete the defection.
1421810hour
1421910minute
1422010second
1422116This job has one or more notifications to operators other than ‘%s’. The job cannot be targeted at remote servers as currently defined.
1422216Cannot rename the ‘%s’ operator.
1422316Cannot modify or delete operator ‘%s’ while this server is a %s.
1422410Warning: The server name given is not the current MSX server (‘%s’).
1422516Warning: Could not determine local machine name. This prevents MSX operations from being posted.
1422610%ld history entries purged.
1422710Server defected from MSX ‘%s’. %ld job(s) deleted.
1422810Server MSX enlistment changed from ‘%s’ to ‘%s’.
1422910Server enlisted into MSX ‘%s’.
1423010SP_POST_MSX_OPERATION: %ld %s download instruction(s) posted.
1423110SP_POST_MSX_OPERATION Warning: The specified %s (‘%s’) is not involved in a multiserver job.
1423216Specify either a job_name, job_id, or an originating_server.
1423316Specify a valid job_id (or 0x00 for all jobs).
1423416The specified ‘%s’ is invalid (valid values are returned by %s).
1423516The specified ‘%s’ is invalid (valid values are greater than 0 but excluding %ld).
1423610Warning: Non-existent step referenced by %s.
1423716When an action of ‘REASSIGN’ is specified, the New Login parameter must also be supplied.
1423810%ld jobs deleted.
1423910%ld jobs reassigned to %s.
1424010Job applied to %ld new servers.
1424110Job removed from %ld servers.
1424216Only a system administrator can reassign ownership of a job.
1424310Job ‘%s’ started successfully.
1424516Specify either the @name, @id, or @loginname of the task(s) to be deleted.
1425016The specified %s is too long. It must contain no more than %ld characters.
1425116Cannot specify ‘%s’ as the operator to be notified.
1425216Cannot perform this action on a job you do not own.
1425310%ld (of %ld) job(s) stopped successfully.
1425410Job ‘%s’ stopped successfully.
1425516The owner (‘%s’) of this job is either an invalid login, or is not a valid user of database ‘%s’.
1425616Cannot start the job “%s” (ID %s) because it does not have any job server or servers defined. Associate the job with a job server by calling sp_add_jobserver.
1425716Cannot stop the job “%s” (ID %s) because it does not have any job server or servers defined. Associate the job with a job server by calling sp_add_jobserver.
1425816Cannot perform this operation while SQLServerAgent is starting. Try again later.
1426016You do not have sufficient permission to run this command. Contact your system administrator.
1426116The specified %s (‘%s’) already exists.
1426216The specified %s (‘%s’) does not exist.
1426316Target server ‘%s’ is already a member of group ‘%s’.
1426416Target server ‘%s’ is not a member of group ‘%s’.
1426524The MSSQLServer service terminated unexpectedly. Check the SQL Server error log and operating system error logs for possible causes.
1426616The specified ‘%s’ is invalid (valid values are: %s).
1426716Cannot add a job to the ‘%s’ job category.
1426816There are no jobs at this server that originated from server ‘%s’.
1426916Job ‘%s’ is already targeted at server ‘%s’.
1427016Job ‘%s’ is not currently targeted at server ‘%s’.
1427116A target server cannot be named ‘%s’.
1427216Object-type and object-name must be supplied as a pair.
1427316You must provide either @job_id or @job_name (and, optionally, @schedule_name), or @schedule_id.
1427416Cannot add, update, or delete a job (or its steps or schedules) that originated from an MSX server.
1427516The originating server must be either local server or MSX server.
1427616‘%s’ is a permanent %s category and cannot be deleted.
1427716The command script does not destroy all the objects that it creates. Revise the command script.
1427816The schedule for this job is invalid (reason: %s).
1427916Supply either @job_name, @job_id or @originating_server.
1428016Supply either a job name (and job aspect), or one or more job filter parameters.
1428110Warning: The @new_owner_login_name parameter is not necessary when specifying a ‘DELETE’ action.
1428216Supply either a date (created or last modified) and a data comparator, or no date parameters at all.
1428316Supply @target_server_groups or @target_servers, or both.
1428416Cannot specify a job ID for a new job. An ID will be assigned by the procedure.
1428516Cannot add a local job to a multiserver job category.
1428616Cannot add a multiserver job to a local job category.
1428716The ‘%s’ supplied has an invalid %s.
1428816%s cannot be before %s.
1428916%s cannot contain ‘%s’ characters.
1429016This job is currently targeted at the local server so cannot also be targeted at a remote server.
1429116This job is currently targeted at a remote server so cannot also be targeted at the local server.
1429216There are two or more tasks named ‘%s’. Specify %s instead of %s to uniquely identify the task.
1429316There are two or more jobs named ‘%s’. Specify %s instead of %s to uniquely identify the job.
1429416Supply either %s or %s to identify the job.
1429516Frequency Type 0x2 (OnDemand) is no longer supported.
1429616This server is already enlisted into MSX ‘%s’.
1429716Cannot enlist into the local machine.
1429816This server is not currently enlisted into an MSX.
1429916Server ‘%s’ is an MSX. Cannot enlist one MSX into another MSX.
1430116Logins other than the current user can only be seen by members of the sysadmin role.
1430516Column ‘%.*ls’ does not exist in table ‘%.*ls’.
1430616The target server (TSX) version is not compatible with the master server (MSX) version (%ld.%ld.%ld).
1430716Access to Integration Services package ‘%s’ is denied.
1435016Cannot initialize COM library because CoInitialize failed.
1435116Cannot complete this operation because an unexpected error occurred.
1435316Cannot determine the service account for this SQL Server instance.
1435716Cannot list ‘%s’ in Active Directory because the name is too long. Active Directory common names cannot exceed 64 characters.
1436016%s is already configured as TSX machine
1436216The MSX server must be running the Standard or Enterprise edition of SQL Server
1436316The MSX server is not prepared for enlistments [there must be an operator named ‘MSXOperator’ defined at the MSX]
1436416The TSX server is not currently enlisted
1436516Specify a valid schedule_uid.
1436616Only members of sysadmin role can modify the owner of a schedule.
1436716One or more schedules were not deleted because they are being used by at least one other job. Use “sp_detach_schedule” to remove schedules from a job.
1436816Schedule “%s” was not deleted because it is being used by at least one other job. Use “sp_detach_schedule” to remove schedules from a job.
1436916The schedule ID “%s” is used by more than one job. Specify the job_id.
1437016The @originating_server must be either the local server name or the master server (MSX) name for MSX jobs on a target server (TSX).
1437116There are two or more schedules named “%s”. Specify %s instead of %s to uniquely identify the schedule.
1437216The schedule was not deleted because it is being used by one or more jobs.
1437316Supply either %s or %s to identify the schedule.
1437416The specified schedule name “%s” is not associated with the job “%s”.
1437516More than one schedule named “%s” is attached to job “%s”. Use “sp_update_schedule” to update schedules.
1437616More than one schedule named “%s” is attached to job “%s”. Use “sp_detach_schedule” to remove schedules from a job.
1437716The schedule was not attached to the specified job. The caller must own the job or the operation must be performed by a sysadmin.
1437816@sysadmin_only flag is no longer supported by SQLAgent and kept here only for backwards compatibility
1437916Table ‘%s’ foreign key ‘originating_server_id’ does not have a matching value in the referenced view ‘dbo.sysoriginatingservers_view’.
1438016Field ‘originating_server_id’ in table sysoriginatingservers is being referenced by either sysjobs or sysschedules.
1439016Only members of role sysadmin can specify the %s parameter.
1439116Only owner of a job or members of sysadmin role can detach a schedule.
1439216Only owner of a job or members of role sysadmin or SQLAgentOperatorRole can purge history of the job.
1439316Only owner of a job or members of role sysadmin or SQLAgentOperatorRole can start and stop the job.
1439416Only owner of a job schedule or members of sysadmin role can modify or delete the job schedule.
1439516‘%s’ is a member of sysadmin server role and cannot be granted to or revoked from the proxy. Members of sysadmin server role are allowed to use any proxy.
1439616Only members of sysadmin server role can modify multi-server jobs
1439716Only members of sysadmin server role can start/stop multi-server jobs
1439816Only members of sysadmin server role can create multi-server jobs
1439916Current proxy_id %d and new proxy_id %d cannot be the same.
1440016Proxy %d does not have access to subsystem %d. Please use sp_grant_proxy_to_subsystem to grant permissions to this proxy.
1441016You must supply either a plan_name or a plan_id.
1441116Cannot delete this plan. The plan contains enlisted databases.
1441216The destination database is already part of a log shipping plan.
1441316This database is already log shipping.
1441416A log shipping monitor is already defined.
1441516The user name cannot be null when using SQL Server authentication.
1441616This stored procedure must be run in msdb.
1441716Cannot delete the monitor server while databases are participating in log shipping.
1441816The specified @backup_file_name was not created from database ‘%s’.
1441916The specified @backup_file_name is not a database backup.
1442016The log shipping primary database %s.%s has backup threshold of %d minutes and has not performed a backup log operation for %d minutes. Check agent log and logshipping monitor information.
1442116The log shipping secondary database %s.%s has restore threshold of %d minutes and is out of sync. No restore was performed for %d minutes. Restored latency is %d minutes. Check agent log and logshipping monitor information.
1442216Supply either @plan_id or @plan_name.
1442316Other databases are enlisted on this plan and must be removed before the plan can be deleted.
1442416The database ‘%s’ is already involved in log shipping.
1442516The database ‘%s’ does not seem to be involved in log shipping.
1442616A log shipping monitor is already defined. Call sp_define_log_shipping_monitor with @delete_existing = 1.
1442716A user name is necessary for SQL Server security.
1442816Could not remove the monitor as there are still databases involved in log shipping.
1442916There are still secondary servers attached to this primary.
1443016Destination path %s is not valid. Unable to list directory contents. Specify a valid destination path.
1444016Could not set single user mode.
1444116Role change succeeded.
1444216Role change failed.
1445016The specified @backup_file_name was not taken from database ‘%s’.
1445116The specified @backup_file_name is not a database backup.
1450016Supply either a non-zero message ID, non-zero severity, non-null performance condition, or non-null WMI namespace and query.
1450116An alert (‘%s’) has already been defined on this condition.
1450216The @target_name parameter must be supplied when specifying an @enum_type of ‘TARGET’.
1450316The @target_name parameter should not be supplied when specifying an @enum_type of ‘ALL’ or ‘ACTUAL’.
1450416‘%s’ is the fail-safe operator. You must make another operator the fail-safe operator before ‘%s’ can be dropped.
1450516Specify a null %s when supplying a performance condition.
1450616Cannot set alerts on message ID %ld.
1450716A performance condition must be formatted as: ‘object_name|counter_name|instance_name|comparator(> or < or =)|numeric value’.
1450816Specify both @wmi_namespace and @wmi_query.
1450916Specify a valid %s when supplying a @wmi_namespace.
1451016Specify a null %s when supplying a @wmi_namespace.
1451116The @wmi_query could not be executed in the @wmi_namespace provided. Verify that an event class selected in the query exists in the namespace and that the query has the correct syntax.
1451216Specify a valid %s when supplying a @wmi_query.
1451310Analysis query subsystem
1451410Analysis command subsystem
1451516Only a member of the sysadmin server role can add a job for a different owner with @owner_login_name.
1451616Proxy (%d) is not allowed for subsystem “%s” and user “%s”. Grant permission by calling sp_grant_proxy_to_subsystem or sp_grant_login_to_proxy.
1451716A proxy account is not allowed for a Transact-SQL subsystem.
1451816Cannot delete proxy (%d). It is used by at least one jobstep. Change this proxy for all jobsteps by calling sp_reassign_proxy.
1451916Only one of @login_name, @fixed_server_role, or @msdb_role should be specified.
1452016%s is not a valid SQL Server standard login, Windows NT user, Windows NT group, or msdb database role.
1452116%s is not a valid SQL Server fixed server role, Windows NT user, or Windows NT group.
1452216‘”%s” is not a valid role of an msdb database, Windows NT user, or Windows NT group.
1452316%s has not been granted permission to use proxy “%s”.
1452416Supply either %s or %s.
1452516Only members of sysadmin role are allowed to update or delete jobs owned by a different login.
1452616The specified category “%s” does not exist for category class “%s”.
1452716Job “%s” cannot be used by an alert. It should first be associated with a server by calling sp_add_jobserver.
1452816Job “%s” has no steps defined.
1452916Proxy “%s” is not a valid Windows user.
1453016The Transact-SQL subsystem cannot be executed under the context of a proxy account.
1453116Permission to access proxy already granted. Verify current permissions assignments.
1453216Supply both %s and %s, or none of them.
1453316Use either a proxy or user_domain, user_name, or user_password parameter.
1453416All user_domain, user_name, and user_password parameters should be defined.
1453516The user_domain, user_name, and user_password parameters can be specified only for replication subsystems.
1453616Only members of the sysadmin role can specify a “%s” parameter.
1453716Execution in the context of disabled proxy (proxy_id = %d) is not allowed. Contact your system administrator.
1453810SSIS package execution subsystem
1453916Only a Standard or Enterprise edition of SQL Server can be enlisted into an MSX.
1454016Only a SQL Server running on Microsoft Windows NT can be enlisted into an MSX.
1454116The version of the MSX (%s) is not recent enough to support this TSX.  Version %s or later is required at the MSX.
1454216It is invalid for any TSQL step of a multiserver job to have a non-null %s value.
1454316Login ‘%s’ owns one or more multiserver jobs. Ownership of these jobs can only be assigned to members of the %s role.
1454416This job is owned by ‘%s’. Only a job owned by a member of the %s role can be a multiserver job.
1454516The %s parameter is not valid for a job step of type ‘%s’.
1454616The %s parameter is not supported on Windows 95/98 platforms.
1454710Warning: This change will not be downloaded by the target server(s) until an %s for the job is posted using %s.
1454810Target server ‘%s’ does not have any jobs assigned to it.
1454910(Description not requested.)
1455010Command-Line Subsystem
1455110Replication Snapshot Subsystem
1455210Replication Transaction-Log Reader Subsystem
1455310Replication Distribution Subsystem
1455410Replication Merge Subsystem
1455510Active Scripting Subsystem
1455610Transact-SQL Subsystem
1455710[Internal]
1455810(encrypted command)
1455910(append output file)
1456010(include results in history)
1456110(normal)
1456210(quit with success)
1456310(quit with failure)
1456410(goto next step)
1456510(goto step)
1456610(idle)
1456710(below normal)
1456810(above normal)
1456910(time critical)
1457010(Job outcome)
1457110No description available.
1457210@freq_interval must be at least 1 for a daily job.
1457310@freq_interval must be a valid day of the week bitmask [Sunday = 1 .. Saturday = 64] for a weekly job.
1457410@freq_interval must be between 1 and 31 for a monthly job.
1457510@freq_relative_interval must be one of 1st (0x1), 2nd (0x2), 3rd [0x4], 4th (0x8) or Last (0x10).
1457610@freq_interval must be between 1 and 10 (1 = Sunday .. 7 = Saturday, 8 = Day, 9 = Weekday, 10 = Weekend-day) for a monthly-relative job.
1457710@freq_recurrence_factor must be at least 1.
1457810Starts whenever the CPU usage has remained below %ld percent for %ld seconds.
1457910Automatically starts when SQLServerAgent starts.
1458010job
1458110Replication Transaction Queue Reader Subsystem
1458216Only a sysadmin can specify ‘@output_file_name’ parameter for a jobstep.
1458316Only a sysadmin can specify ‘@database_user_name’ parameter.
1458516Only the owner of DTS Package ‘%s’ or a member of the sysadmin role may reassign its ownership.
1458616Only the owner of DTS Package ‘%s’ or a member of the sysadmin role may create new versions of it.
1458716Only the owner of DTS Package ‘%s’ or a member of the sysadmin role may drop it or any of its versions.
1458810ID.VersionID =
1458910[not specified]
1459016DTS Package ‘%s’ already exists with a different ID in this category.
1459116SSIS folder ‘%s’ already exists in the specified parent folder.
1459216DTS Category ‘%s’ was found in multiple parent categories. You must uniquely specify the category to be dropped.
1459316SSIS folder ‘%s’ contains packages and/or other folders. You must drop these first.
1459410DTS Package
1459516DTS Package ‘%s’ exists in different categories. You must uniquely specify the package.
1459616DTS Package ‘%s’ exists in another category.
1459716DTS Package ID ‘%s’ already exists with a different name.
1459816Cannot drop the Local, Repository, or LocalDefault DTS categories.
1459910Name
1460016Proxy “%s” has not been granted permission to use subsystem “%s”.
1460116Operator “%s” is not enabled and therefore cannot receive notifications.
1460216Operator “%s” does not have an e-mail address specified.
1460316Database Mail is not properly configured.
1460416Both %s parameters (id and name) cannot be NULL
1460516Both %s parameters (id and name) do not point to the same object
1460616%s id is not valid
1460716%s name is not valid
1460816Either %s or %s parameter needs to be supplied
1460916Mail database to user database association does not exist and therefore cannot be updated
1461016Either @profile_name or @description parameter needs to be specified for update
1461116Account sequence number must be supplied for update
1461216Each principal should have at least one default profile
1461316The specified ‘%s’ cannot use commas (,) to separate addresses: ‘%s’. To continue, use semicolons (;) to separate addresses.
1461416%s is not a valid mailserver_type
1461516The @username parameter needs to be supplied if the @password is supplied.
1461616Unable to retrieve the newly created credential [%s] from the credential store.
1461716Mail host database specified is invalid
1461816Parameter ‘%s’ must be specified. This parameter cannot be NULL.
1461916Received an error on the Service Broker conversation with Database Mail. Database Mail may not be available, or may have encountered an error. Check the Database Mail error log for information.
1462016The Service Broker conversation to Database Mail ended without a response from Database Mail. Database Mail may not be available, or may have encountered an error. Check the Database Mail error log for more information.
1462116Parameter @attachmentencoding does not support the value “%s”. The attachment encoding must be “MIME”.
1462216Parameter @importance does not support the value “%s”. Mail importance must be one of LOW, NORMAL, or HIGH.
1462316Parameter @sensitivity does not support the value “%s”. Mail sensitivity must be one of NORMAL, PERSONAL, PRIVATE, or CONFIDENTIAL.
1462416At least one of the following parameters must be specified. “%s”.
1462516Parameter @attach_query_result_as_file cannot be 1 (true) when no value is specified for parameter @query. A query must be specified to attach the results of the query.
1462616Parameter @mailformat does not support the value “%s”. The mail format must be TEXT or HTML.
1462716Received error %d while sending a message as part of the %s operation. Database Mail may not be available, or may have encountered an error. Check the Database Mail error log for more information.
1462816The format of the parameter @attachments is incorrect. The file names must be separated by a semicolon “;”.
1462916There is no configuration parameter named “%s”, or the value provided is not of the correct data type.
1463016Database Mail is not permitted to send files with the file extension %s.
1463116The current user (‘%s’) either does not have permission to access the database specified in the parameter @execute_query_database or cannot impersonate the user specified in the parameter @execute_query_as. Only members of the sysadmin fixed server role and members of the db_owner fixed database role can impersonate another user.
1463216The user name %s specified in @execute_query_as is invalid. There is no user by that name.
1463316The database name “%s” specified in @execute_query_database is invalid. There is no database by that name.
1463410Warning: %s’
1463510Mail (Id: %d) queued.
1463616No global profile is configured. Specify a profile name in the @profile_name parameter.
1463710Activation failure.
1463810Activation successful.
1463910The mail queue was started by login “%s”.
1464010The mail queue stopped by login “%s”.
1464116Mail not queued. Database Mail is stopped. Use sysmail_start_sp to start Database Mail.
1464210Default attachment encoding
1464310Default dialog lifetime
1464410Default maximum file size
1464510Extensions not allowed in outgoing mails
1464610Number of retry attempts for a mail server
1464710Delay between each retry attempt to mail server
1464810Minimum process lifetime in seconds
1464916Unable to test profile. Database Mail is stopped. Use sysmail_start_sp to start Database Mail.
1465016Service Broker message delivery is not enabled in this database. Use the ALTER DATABASE statement to enable Service Broker message delivery.
1465116Unable to test profile. Service Broker message delivery is not enabled in this database. Use the ALTER DATABASE statement to enable Service Broker message delivery.
1465216Invalid message received on the ExternalMailQueue. conversation_handle: %s.  message_type_name: %s.  message body: %s.
1465316Invalid %s value received on the ExternalMailQueue. conversation_handle: %s.  message_type_name: %s.  message body: %s.
1465410Unexpected message received on the ExternalMailQueue. conversation_handle: %s.  message_type_name: %s.  message body: %s.
1465516Invalid XML message format received on the ExternalMailQueue. conversation_handle: %s.  message_type_name: %s.  message body: %s.
1465716Mail not queued. Maximum number of mails per day (%ld) for login %s has been exceeded.
1465816Failed to retrieve SQLPath for syssubsystems population.
1465916Failed to retrieve VerSpecificRootDir for syssubsystems population.
1466016Database Compatibility Level is too low. Compatibility Level must be Version80 or higher.
1466116Query execution failed: %s
1466210mailitem_id on conversation %s was not found in the sysmail_send_retries table. This mail item will not be sent.
1466310Mail Id %d has exceeded the retry count. This mail item will not be sent.
1466416Database Mail logging level: normal – 1, extended – 2 (default), verbose – 3
1466510Mail items deletion is initiated by user “%s”. %d items deleted.
1466616User name cannot be supplied when using default credentials
1466716Mail Id %d has been deleted from sysmail_mailitems table. This mail will not be sent.
1466816Deleting profile %s failed because there are some unsent emails associated with this profile, use force_delete option to force the deletion of the profile.
1467016Cannot delete the active collection set ‘%s’. Stop the collection set and then try to delete it again.
1467116Cannot update the name or the parameters of the collection item ‘%s’ in the active collection set ‘%s’. Stop the collection set and then try to update the collection item again.
1467216Cannot delete the collection item ‘%s’ in the active collection set ‘%s’. Stop the collection set and then try to delete the collection item again.
1467316Cannot delete the collector type ‘%s’. Delete all collection items associated with this collector type and then try to delete it again.
1467416Cannot upload data for the inactive collection set ‘%s’. Start the collection set and then try to upload the data again.
1467516Cannot update the name, target, proxy_id, logging_level, or collection_mode, or add collection item to the active collection set ‘%s’. Stop the collection set and then try to update it again.
1467616The user does not have permission to change ‘%s’. The user must be a member of data collector role ‘%s’.
1467716The user does not have permission to perform this operation. The user must be a member of data collector role ‘%s’.
1467816SQL Server Trace with id %d has been stopped and closed by external user. SQL Server Trace collector will attempt to re-create the trace.
1467916The specified %s (%s) is not valid in this data warehouse.
1468016Management Data Warehouse database can only be installed on an instance of SQL Server 2008 or higher.
1468116Cannot perform this procedure when the collector is disabled. Enable the collector and then try again.
1468216The state of the collection set has changed, but it will not start or stop until the collector is enabled.
1468316A collection set in cached mode requires a schedule.
1468416Caught error#: %d, Level: %d, State: %d, in Procedure: %s, Line: %d, with Message: %s
1468516Collection set: ‘%s’ does not contain any collection items, so starting the collection set will have no effect.
1468616The MDWInstance and MDWDatabase parameters of the configuration store cannot be null.
1468716Invalid value (%d) of the @cache_window parameter. Allowable values are: -1 (cache all upload data from previous upload failures), 0 (cache no upload data), N (cache data from N previous upload failures, where N >= 1)
1468816A collection set cannot start when SQL Server Agent is stopped. Start SQL Server Agent.
1468916A collection set cannot start if the management data warehouse is not configured. Run the instmdw.sql script to create and configure the management data warehouse.
1469016Cannot perform this procedure when the collector is enabled. Disable the collector and then try again.
1469116The status of the collector cannot be null. This may indicate an internal corruption in the collector configuration data.
1469216Insufficient priveleges to start collection set: ‘%s’. Only a member of the ‘sysadmin’ fixed server role can start a collection set without a SQL Server Agent proxy. Attach a SQL Server Agent proxy to the collection set before retrying.
1469316A collection set cannot start without a schedule. Specify a schedule for the collection set.
1469416Cannot upload data on-demand for the collection set ‘%s’ in non-cached mode.
1469516Cannot collect data on-demand for the collection set ‘%s’ in cached mode.
1469616 Cannot update or delete a system collection set, or add new collection items to it.
1469716Unable to convert showplan to XML.  Error #%d on Line %d: %s
1469810PowerShell Subsystem
1469916Data Collector cannot be enabled when SQL Server Agent is stopped. Start SQL Server Agent.
1470010Collects data about the disk and log usage for all databases.
1470110Disk Usage
1470210Disk Usage – Data Files
1470310Disk Usage – Log Files
1470410Collects top-level performance indicators for the computer and the Database Engine. Enables analysis of resource use, resource bottlenecks, and Database Engine activity.
1470510Server Activity
1470610Server Activity – DMV Snapshots
1470710Server Activity – Performance Counters
1470810Collects query statistics, T-SQL text, and query plans of most of the statements that affect performance. Enables analysis of poor performing queries in relation to overall SQL Server Database Engine activity.
1470910Query Statistics
1471010Query Statistics – Query Activity
1471110Changes to SQL dumper configuration will take effect when the collection set is restarted. To perform an immediate dump, use the dtutil /dump option.
1471216Only dbo or members of dc_admin can install or upgrade instmdw.sql. Contact an administrator with sufficient permissions to perform this operation.
1471321A management data warehouse cannot be installed to SQL Server Express Edition.
1471416Attempting to upgrade a Management Data Warehouse of newer version ‘%s’ with an older version ‘%s’. Upgrade aborted.
1471510Collects data about instances of SQL Server that are managed in the SQL Server Utility.
1471610Utility Information
1471810Utility Information – Managed Instance
1471916%s has not been granted permission to use proxy.
1472016The operation failed because credential ‘%s’ identity is not a valid Windows account
1472110AutoAdmin Subsystem
1480116Multiple REMOTE_DATA_ARCHIVE definition.
1480216Cannot disable REMOTE_DATA_ARCHIVE because the database contains at least one table having REMOTE_DATA_ARCHIVE enabled.
1480316Cannot alter REMOTE_DATA_ARCHIVE option for table ‘%.*ls’ because REMOTE_DATA_ARCHIVE is not enabled for the database.
1480416The database credential ‘%s’ cannot be found or the user doesn’t have premission to access the credential.
1480616The identity specified for the database credential ‘%s’ is invalid. The identity must be a valid username for the remote stretch server administrator.
1480716The secret specified for the database credential ‘%s’ is invalid. The secret must be a valid password for the remote stretch server administrator.
1480816Cannot disable REMOTE_DATA_ARCHIVE when migration is enabled.
1480916Cannot enable REMOTE_DATA_ARCHIVE on database ‘%s’. The REMOTE_DATA_ARCHIVE option can only be set on user databases.
1481016The database option REMOTE_DATA_ARCHIVE is already enabled on database ‘%s’.
1481116Remote server ‘%s’ is not an Azure SQL Database V12 (or higher) server. A database can only be stretched to an Azure SQL Database V12 (or higher) server.
1481216Cannot enable REMOTE_DATA_ARCHIVE for table ‘%.*ls’ due to ‘%ls’. %ls
1481316Cannot enable REMOTE_DATA_ARCHIVE for table ‘%.*ls’ due to column ‘%.*ls’ ‘%ls’. %ls
1481416Code generation for REMOTE_DATA_ARCHIVE failed (%ls).
1481516File error during REMOTE_DATA_ARCHIVE operation. GetLastError = %d (%ls).
1481616The code generation directory cannot be created or set up correctly.
1481716The server ‘%s’ is not accessible. Ensure that the remote server exists and the Azure SQL DB Firewall Rules permit access to the server. If you believe that your server should be accessible please retry the command.
1481810The %ls on table ‘%ls’ will not be enforced because of the use of REMOTE_DATA_ARCHIVE.
1481920Stretch operation failed due to an internal error.
1482020The stretch code generator output is corrupted.  Stretch code generation and remote table provisioning will be re-tried.
1482116Cannot execute in REMOTE_ONLY mode since remote part does not exist or is invalid for this operation.
1482216‘%s’ is not a valid option for the @mode parameter. Enter  ‘ALL’, ‘LOCAL_ONLY’ or ‘REMOTE_ONLY’.
1482316%ls failed on table ‘%.*ls’ because it is not supported on tables with REMOTE_DATA_ARCHIVE option enabled.
1482416Access to REMOTE_DATA_ARCHIVE has been disabled through server configuration option ‘remote data archive’. Use “exec sp_configure ‘remote data archive’, 1” to enable access to the server.
1482516Cannot perform ‘%ls’ on table ‘%.*ls’ because REMOTE_DATA_ARCHIVE is enabled. %ls
1482614Update and delete of rows eligible for migration in table ‘%.*ls’ is not allowed because of the use of REMOTE_DATA_ARCHIVE.
1482716Unable to access remote data archive: Error: %d, Severity: %d, State: %d, Line: %d ‘%s’
1482816Cannot perform ‘CREATE INDEX’ on view ‘%.*ls’ because it references table ‘%.*ls’ with REMOTE_DATA_ARCHIVE enabled.
1482916Table ‘%.*ls’ cannot be used in READTEXT, WRITETEXT and UPDATETEXT statements because it has REMOTE_DATA_ARCHIVE option enabled.
1483016Cannot query table ‘%.*ls’ because this operation is currently disabled for this object.
1483116Cannot set the Remote Data Archive query mode for database ‘%.*ls’ because REMOTE_DATA_ARCHIVE is not enabled on the database.
1483210Querying tables having REMOTE_DATA_ARCHIVE option enabled will not be possible in LOCAL_AND_REMOTE query mode in database ‘%.*ls’ before Remote Data Archive re-authorization is performed.
1483316Cannot set the Remote Data Archive query mode LOCAL_AND_REMOTE for database ‘%.*ls’ because data on remote side is not consistent. See the SQL Server errorlog for more information on the inconsistent objects.
1483416Cannot de-authorize database ‘%.*ls’ because REMOTE_DATA_ARCHIVE is not enabled on the database.
1483516Cannot de-authorize database ‘%.*ls’ because it is already disconnected from the remote database.
1483616Cannot reconcile stretched indexes for database ‘%.*ls’ because REMOTE_DATA_ARCHIVE is not enabled on the database.
1483716Cannot reconcile indexes for stretched table ‘%.*ls’ because migration is not outbound on the table.
1483816Table ‘%.*ls’ cannot be accessed in SNAPSHOT transaction isolation level because it has REMOTE_DATA_ARCHIVE option enabled.
1483916Only column identifiers are allowed as parameters passed to function ‘%.*ls’.
1484016The filter predicate cannot be set for table ‘%.*ls’ because all rows are already eligible for migration.
1484116The filter predicate ‘%.*ls’ for table ‘%.*ls’ cannot be replaced with ‘%.*ls’ because conditions necessary to perform the replacement are not satisfied.
1484210The database ‘%.*ls’ contains REMOTE_DATA_ARCHIVE tables, it will be marked as disconnected from the remote during the restore. If you would like to reconnect to the same archive or make a copy, refer to the sp_rda_reauthorize_db spec proc once the restore is complete.
1484310Copying remote database ‘%.*ls’ to remote database ‘%.*ls’.
1484410Remote database ‘%.*ls’ has completed copying, and is now online.
1484510Waiting for remote database copy to complete.
1484616Cannot re-authorize database ‘%.*ls’ because REMOTE_DATA_ARCHIVE is not enabled on the database.
1484716Cannot re-authorize database ‘%.*ls’ because it is already authorized and connected to a remote database.
1484816Attempted Migration failed. Remote insert failed. Error : %d.
1484916Attempted Migration failed. Remote insert failed to insert all the rows. Expected rows : %d, Actual remote rows inserted: %d.
1485016Attempted Migration failed. Incrementation of the batch ID failed. Expected batch ID : %I64d, Current batch ID : %I64d.
1485116Attempted Reconciliation failed. The new max remote batch IDs is not less than the initial. Initial: %I64d, New: %I64d
1485216Cannot query table ‘%.*ls’ because data reconciliation is in progress. This is part of the automatic recovery process for a remote data archive enabled table. You may check the status of this operation in sys.remote_data_archive_tables.
1485316Function ‘%.*ls’ cannot be used as Stretch filter predicate because it does not meet necessary requirements.
1485410The Remote Data Archive connection to the server ‘%ls’ succeeded.
1485516The Remote Data Archive connection to the server ‘%ls’ failed.
1485616The procedure %ls requires the %ls parameter if the database is not enabled for REMOTE_DATA_ARCHIVE.
1485716The procedure %ls does not accept the %ls parameter if the database is enabled for REMOTE_DATA_ARCHIVE.
1485816Cannot queue more stretch tasks. Please wait for remaining tasks to be finished and try again later.
1485910The database ‘%.*ls’ contains REMOTE_DATA_ARCHIVE tables, it will be marked as disconnected from the remote during the restore. If you would like to reconnect to the same archive or make a copy, refer to the sp_rda_reauthorize_db spec proc once the restore is complete.
1486016‘%.*ls’ expects parameter ‘%.*ls’, which was not supplied.
1486116Modifying the collation is not allowed when REMOTE_DATA_ARCHIVE is already enabled on database ‘%.*ls’.
1486216Cannot rename index ‘%ls’. Indexes on tables with REMOTE_DATA_ARCHIVE option enabled cannot be renamed.
1486316Stretch was disabled after migration started. Please enable stretch and retry.
1486416Attempted inbound migration failed. Local insert failed. Error : %d.
1486516Attempted inbound migration failed. Decrementation of the batch ID failed. Expected batch ID : %I64d, Current batch ID : %I64d.
1486616Attempted unlinking of the stretched table failed. If this table isn’t dropped, please retry the operation of setting REMOTE_DATA_ARCHIVE to OFF on the table.
1486716User does not have permission to enable REMOTE_DATA_ARCHIVE with FEDERATED_SERVICE_ACCOUNT = ON.
1486816Inbound migration is in progress or paused. Migration direction outbound cannot be set at this time. Please retry after inbound migration is complete.
1486916Must be DB OWNER to use the REMOTA_DATA_ARCHIVE_OVERRIDE hint.
1487016REMOTE_DATA_ARCHIVE_OVERRIDE hint is not allowed inside a user transaction.
1487116REMOTE_DATA_ARCHIVE_OVERRIDE hint is not allowed inside an implicit transaction.
1487216REMOTE_DATA_ARCHIVE_OVERRIDE hint not permitted on INSERT statements.
1487316REMOTE_DATA_ARCHIVE_OVERRIDE hint not permitted within a view definition.
1487416Table ‘%.*ls’ cannot be a target of an update or delete statement with a FROM clause because it has the REMOTE_DATA_ARCHIVE option enabled.
1487516DML operation failed because it would have affected one or more migrated (or migration-eligible) rows.
1487616Table ‘%.*ls’ cannot be the target of an update or delete statement through a view because it has the REMOTE_DATA_ARCHIVE option enabled.
1487716Not all rows needed to reconcile with the remote data are available locally for table ‘%ls’. Needed batch ID : %I64d, Available batch ID : %I64d.
1487816The filter predicate cannot be set for table ‘%ls’ together with inbound migration.
1487916Cannot perform update or delete using hint %.*ls over table ‘%.*ls’ if migration is not paused. Please set MIGRATION_STATE to PAUSED and retry the operation.
1488016Unexpected exception occurred during remote column update.
1488116Unable to update remote data archive: Error: %d, Severity: %d, State: %d.
1488216Cannot use STAGE_ONLY hint since the staging environment for the table ‘%.*ls’ has not been provisioned yet.
1488316Stretch remote table creation failed without specific exception.
1488416Unable to load the stretch filter predicate for table “%.*ls”.
1488516Cannot reconcile columns for %S_MSG ‘%.*ls’ because REMOTE_DATA_ARCHIVE is not enabled on the %S_MSG.
1488616Cannot set the rpo duration for database ‘%.*ls’ because REMOTE_DATA_ARCHIVE is not enabled on the database.
1488716Cannot run the procedure %.*ls for table ‘%.*ls’ if migration is not paused. Please set MIGRATION_STATE to PAUSED and retry the operation.
1488816Attempted inbound migration failed. Insert failed to insert all the rows. Expected rows : %d, Actual remote rows: %d.
1488916Unable to process DML statement due to an unexpected operator in the migration predicate for table “%.*ls”.
1489016The maximum batch ID in the staging table cannot be greater than %I64d. Please perform the necessary delete/update operation using STAGE_ONLY hint to correct it.
1489116Table ‘%.*ls’ cannot be a target of an update or delete statement with an OUTPUT clause because it has the REMOTE_DATA_ARCHIVE option enabled.
1489216Table ‘%.*ls’ cannot be a target of an update or delete statement through a CURSOR because it has the REMOTE_DATA_ARCHIVE option enabled.
1489316Table ‘%.*ls’ cannot be a target of an update or delete statement because it has the REMOTE_DATA_ARCHIVE option enabled without a migration predicate.
1489416Table ‘%.*ls’ cannot be a target of an update or delete statement because it has both the REMOTE_DATA_ARCHIVE option enabled and a BLOCK PREDICATE enabled.
1489516Cannot run the procedure %.*ls for table ‘%.*ls’ since the max batch ID found in the stage table is different than the max batch ID found in the remote table. Please make sure that you run the same hinted admin query on both tables to bring them in sync.
1489610Reconciliation proc %.*ls brought down the local batch ID for the stretch table ‘%.*ls’ of database ‘%.*ls’ from %I64d to %I64d.
1489716Cannot run the procedure %.*ls for table ‘%.*ls’ since it is not stretched.
1489816Cannot run the procedure %.*ls in database ‘%.*ls’ since it is not connected to a remote database.
1489916Specified RPO Duration cannot be less than the minimum duration of %d
1490110Running an admin %ls operation on stretched table with ID %d using %ls hint.
1490316Cannot rename column ‘%ls’. Columns on tables with REMOTE_DATA_ARCHIVE option enabled cannot be renamed.
1490410Reauthorizing stretched database ‘%.*ls’ with the remote database has completed successfully. Now reconciling remote tables and/or remote columns…
1490510Reconciliation of remote tables and/or remote columns for stretched database ‘%.*ls’ has completed successfully.
1490616The database ‘%s’ is not accessible. Ensure that the remote database exists. If you believe that your database should be accessible please retry the command.
1490816Cannot set REMOTE_DATA_ARCHIVE to OFF from ON. To retrieve remote data and turn off remote data archive, set REMOTE_DATA_ARCHIVE (MIGRATION_STATE = INBOUND). To turn off REMOTE_DATA_ARCHIVE without retrieving remote data, set REMOTE_DATA_ARCHIVE = OFF_WITHOUT_DATA_RECOVERY.
1490916Cannot currently use the REMOTE_DATA_ARCHIVE_OVERRIDE hint with table ‘%.*ls’ because the remote table has not yet been created.
1491016Cannot currently perform the requested operation against table ‘%.*ls’ because it has the REMOTE_DATA_ARCHIVE option enabled but the remote table has not yet been created.
1491110%.*ls is set to ‘%.*ls’ on table ‘%.*ls’.
1491210REMOTE_DATA_ARCHIVE with value set to OFF_WITHOUT_DATA_RECOVERY is not supported at table creation. Please retry using a valid option’.
1491310Failure was injected by ‘%ls’ transaction/function.
1491416The edition for database ‘%ls’ is invalid. Only the Azure SQL Stretch edition is supported as a target for Stretch database.
1491516The use of replication is not supported for table ‘%ls’ with REMOTE_DATA_ARCHIVE enabled.
1491616Change Data Capture is not supported for table ‘%ls’ with REMOTE_DATA_ARCHIVE enabled.
1491716The REMOTE_DATA_ARCHIVE option cannot be enabled on table ‘%ls’ because it will exceed the maximum allowable size of %d bytes on the remote table due to an additional required system column.

Leave a Reply

You May Also Like

When dealing with a relational database management system (RDBMS) like SQL Server, compatibility level is an important concept to understand....
In this blog post, let’s learn about the error message “49975 – Unable to load controller client certificate due to...
In this blog post, let’s learn about the error message “49973 – Cannot remove tempdb remote file to local tempdb...