错误码目录 / Microsoft SQL Server
Microsoft SQL Server 错误码目录 · 第 18 / 18 页
本页收录 Microsoft SQL Server 的 17,993 条错误码知识条目,每条均可打开独立详情页,包含错误说明、编号信息、官方文档与公开资料。
- 45580 — The elastic pool has reached its storage limit. The storage allocated for the elastic pool cannot exceed (%d) MB. (%d) MB storage has been allocated a…
- 45581 — Native restore backup contains files in forbidden states.
- 45582 — Subnet currently used by managed instance and provided destination subnet are part of the virtual networks that are not connected with virtual network…
- 45583 — Subnet provided for managed instance deployment is located on subscription different than the one submitted for managed instance. Managed instance and…
- 45584 — Parameter '%s' cannot be null or empty. Specify a value for the named parameter and retry the operation.
- 45585 — The parameter '%ls' is invalid. '%ls'
- 45586 — The restored database is too large for the requested service level objective '%s'. Submit a new restore request to a target service level objective wh…
- 45587 — The attempted CRUD operation of Start/Stop schedule on the Azure SQL Managed Instance '%ls' cannot be executed. The schedule does not exist for a give…
- 45588 — Cannot create Managed Instance in the subnet '%ls' because subnet is too small. Minimal allowed size of a subnet is %d IP addresses. For more informat…
- 45589 — The subnet selected for managed instance migration has an address range that overlaps with the address range of the subnet that holds the geo replicat…
- 45590 — The subnet selected for managed instance migration is not configured to enable communication with the geo replicated secondary instance. Check if all …
- 45591 — The database can't be restored into the resource pool due to the remaining storage capacity in the pool. The database required {0} bytes, while the po…
- 45592 — The largest database file size of database '{0}' exceeds data file size limit {1} for General Purpose SQL Managed Instance service tier. See: https://…
- 45593 — Storage account limit {0} for General Purpose SQL Managed Instance '{1}' exceeded. See: https://learn.microsoft.com/azure/azure-sql/managed-instance/r…
- 45594 — Unable to add keys to the Azure SQL Server due to CryptographicException. Error details: Exponent: '%ls', Modulus: %ls'. For additional support, conta…
- 45595 — The key vault provided '%ls' on server '%ls' uses unsupported RSA Key Exponent. Exponent value: '%ls'. For additional support, contact your system adm…
- 45596 — Database restore is not supported when Database-level CMK is configured in preview.
- 45597 — Database-level CMK in preview is not supported for Hyperscale edition..
- 45598 — Geo Replication and Database Copy is not supported when Database-level CMK is configured in preview.
- 45599 — Standby replicas are not supported in DTU based purchasing models. Neither source nor target for standby replicas may be DTU based.
- 45600 — AKV endpoint '%ls' is not reachable from SQL, on server '%ls'.
- 45601 — DTC cannot be configured because it is not supported on the virtual cluster version hosting Azure SQL Managed Instance '%ls'.
- 45602 — Database recovery requests are invalid when issued against a database that is not configured to use geo-redundant backup storage.
- 45603 — Restoring a Hyperscale database backup to a non-Hyperscale service tier or vice versa is not supported.
- 45604 — The subscription '%ls' does not have access to the specified server(s) '%ls'
- 45605 — The specified recovery point '%ls' either does not exist or is not valid.
- 45606 — The specified long term retention backup '%ls' does not exist.
- 45607 — The specified point in time, '%ls', is not valid for database '%ls'. Valid points in time are between '%ls' and '%ls' inclusive.
- 45608 — Cannot resolve target cluster for server '%ls'
- 45609 — Specifying the target service level objective or edition is not supported when restoring to an elastic pool.
- 45610 — Point-in-time restore and database recovery operations are not supported on databases that are currently configured as geo-secondaries.
- 45611 — Configuration of backup retention policy is not supported on Named Replica.
- 45612 — It is not possible to stop the instance that has Managed Instance link configured. Refer to the following article for limits of managed instance start…
- 45613 — The ImportExport operation failed because of invalid storage credentials.
- 45614 — The ImportExport operation failed because of invalid storage auth type.
- 45615 — The ImportExport operation failed because of invalid storage key format.
- 45616 — The ImportExport operation failed because the storage URI is too long.
- 45617 — The Export operation failed because database is larger than max supported size.
- 45618 — The ImportExport operation failed because it is targeting a '%ls' edition.
- 45619 — The ImportExport operation failed because the storage URI is invalid.
- 45620 — Invalid storage IOps limit: %ls IOps. Storage IOps limit must be specified between %ls IOps and %ls IOps, in increments of %ls IOps.
- 45621 — Invalid storage throughput limit: %ls MBps. Storage throughput limit must be specified between %ls MBps and %ls MBps, in increments of %ls MBps.
- 45622 — Geo-redundant backup storage is not permitted for databases under subscription '%s'.
- 45623 — Managed Instance start/stop feature is available only for instances that are running with Feature Wave November 2022. Refer to the following article f…
- 45624 — TR-CMS geo-secondary server/database does not exist.
- 45625 — The ImportExport operation failed because the SQL authentication type is invalid. Please use either SQL Server or Active Directory.
- 45626 — The ImportExport operation failed because the storage blob already exists.
- 45627 — Restoring a Hyperscale database to an elastic pool which is not Hyperscale or restoring a database which is not Hyperscale to a Hyperscale elastic poo…
- 45628 — The specified target database name, '%ls', is reserved and cannot be used in a restore operation.
- 45629 — Restore and database recovery are not supported for system databases.
- 45630 — The source database, '%ls', dropped on '%ls', has not existed long enough to support restores.
- 45631 — The source database, '%ls', has not yet accomplished its first backup in order to support restore operations. Please wait until at least the indicated…
- 45632 — For point-in-time restores, the target logical server must be the same as the source logical server. Consider restoring to the source database's serve…
- 45633 — Same-server recovery is currently not supported. Consider using point-in-time restore or recovering to a different server.
- 45634 — Restore from long-term retention backup to '%ls' edition not supported.
- 45635 — Restore from external backup to '%ls' edition not supported.
- 45636 — Enabling long-term backup retention for a serverless database is not supported if auto-pause is enabled.
- 45637 — Enabling long-term backup retention for a database during migration to the Hyperscale service tier is not supported.
- 45638 — Enabling long-term backup retention for a database during a reverse migration from Hyperscale is not supported.
- 45639 — Enabling auto-pause for a serverless database is not supported if long-term backup retention is enabled.
- 45640 — The subscription ID is required to delete a long-term retention backup.
- 45641 — The server name is required to delete a long-term retention backup.
- 45642 — The database name is required to delete a long-term retention backup.
- 45643 — The provided long-term retention backup resource ID or backup name is incorrect.
- 45644 — A restore request with the same target database name '%ls' on server '%ls' already exists.
- 45645 — The external backup storage container URI is malformed.
- 45646 — The host name for the external backup storage container URI is not allowed.
- 45647 — The external backup storage container URI uses an invalid scheme or port. Please use https and port 443.
- 45648 — Hyperscale does not support external backup restore requests.
- 45649 — For database '%ls', specified point-in-time '%ls' is prior to the Hyperscale migration time of '%ls'. Please specify a target edition or service level…
- 45650 — Storage IOps parameter is not allowed in the instance create/update operation.
- 45651 — Storage throughput MBps parameter is not allowed in the instance create/update operation.
- 45652 — Storage IOps parameter is not allowed in the instance create/update operation for the specified edition.
- 45653 — Storage throughput MBps parameter is not allowed in the instance create/update operation for the specified edition.
- 45654 — Azure Key Vault key URI '%s' is required to successfully restore the database '%s' under server '%s'.
- 45655 — Restore of Hyperscale database where source database is geo-secondary is not allowed.
- 45656 — The operation could not be completed because the Azure Key Vault Key name '%ls' is currently set as encryption protector on geo-primary.
- 45657 — DTC for Azure SQL Managed Instance not ready at the moment.
- 45658 — This operation cannot start because specified target managed instance '%ls' already has maximum number of user databases.
- 45659 — No backups were found to restore the database to the point in time %s (UTC). Please contact support to restore the database.
- 45660 — Target server '%ls' does not have access to all AKV Uris created between %s (UTC) and %s (UTC). Please retry operation after restoring all AKV Uris.
- 45661 — Unable to connect to the instance in order to perform restore operation.
- 45662 — Backup set in %ld is broken. Sql error code is %d. Error message: %ls
- 45663 — A timeout was encountered while trying to connect to the restore target. Please retry or retry with a higher service objective for higher reliability.…
- 45664 — The restore plan is broken because firstLsn (%ls) of log backup '%ls' is not equal to lastLsn (%ls) of prev log backup %ls. Restore to point in time: …
- 45665 — Full backup '%ls' is missing checksum. Please provide full backup with checksum.
- 45666 — Migration cannot be completed because provided backup file name '%ls' should be the last restore backup file '%ls'.
- 45667 — The database backup contains incompatible physical layout. Non-online data files exist.
- 45668 — The database backup contains incompatible physical layout. Multiple log files are not supported.
- 45669 — Database '%ls' operation failed because there is no network connectivity between source instance '%ls' and target instance '%ls'.
- 45670 — Database '%ls' operation failed because there is no connectivity between source and target Azure SQL Managed Instance. This is because the target inst…
- 45671 — Microsoft Distributed Transaction Coordinator (MS DTC) cannot be enabled because required outbound traffic on port 445 to the MS DTC log on a remote s…
- 45672 — Cross subscription '%ls' operation, from subscription id '%ls' to subscription id '%ls' is not allowed because these two subscriptions don't belong to…
- 45673 — Cannot perform delete operation because of the following resource lock: '%ls'. Please remove the lock and try again.
- 45674 — Cannot drop database because a database '%ls' operation is completing.
- 45675 — Combination of unspecified target edition (sku.name/sku.tier parameters) and the value TRUE for the isGeneralPurposeV2 parameter is not allowed in the…
- 45676 — Combination of unspecified target edition (sku.name/sku.tier parameters) and the value TRUE for the isGeneralPurposeV2 parameter is not allowed in the…
- 45677 — Combination of unspecified target edition (sku.name/sku.tier parameters) and the value FALSE for the isGeneralPurposeV2 parameter is not allowed in th…
- 45678 — Combination of General Purpose target edition (sku.name/sku.tier parameters) and unspecified value for the isGeneralPurposeV2 parameter is not allowed…
- 45679 — Combination of Business Critical target edition (sku.name/sku.tier parameters) with a specified isGeneralPurposeV2 parameter is not allowed in the cre…
- 45680 — Combination of unspecified target edition (sku.name/sku.tier parameters) with a specified isGeneralPurposeV2 parameter is not allowed in the update op…
- 45681 — Standby replicas are not supported for hyperscale databases.
- 45682 — No backups were found to restore the database to the point in time %s (UTC). Please retry the operation. If the problem persists, contact support to r…
- 45683 — Memory size in GB parameter is not allowed in the instance create/update operation.
- 45684 — Memory size in GB parameter is not allowed in the instance create/update operation for the service tier or hardware generation.
- 45685 — Could not perform the operation due to capacity group resource constraint based on the requested service level objective and storage size. Plus try ag…
- 45686 — Could not complete the operation due to capacity group resource constraint check failed due to the following reason: {0).
- 45687 — General Purpose v2 edition of Managed Instance is not compatible with the specified subnet. Target subnet must be either empty, or all instances in it…
- 45688 — The specified memory value is invalid. Please ensure the memory size in GB is within the allowable range of 28 to 870 and corresponds appropriately to…
- 45689 — Cannot enable public endpoint for the failover group because managed instance '%ls' doesn't have public endpoint enabled. Please enable public endpoin…
- 45690 — Another operation is in progress on virtual network firewall rule {0} on server {1}.
- 45691 — The operation could not be completed because there is at least one database whose number of files is exceeding the limit of %ls files per database on …
- 45692 — The operation could not be completed because Next-Gen General Purpose edition doesn't support Custom Maintenance Window
- 45693 — The database '%.*ls' on server '%.*ls' is already being dropped.
- 45694 — Database '%ls' was not found on SQL managed instance '%ls'. Please check the database name and ensure it matches a database that is currently in 'Rest…
- 45695 — Database '%ls' is not in 'Restoring' state on SQL managed instance '%ls'. Please check the database name and ensure it matches a database that is curr…
- 45696 — Database '%ls' was already restored on SQL managed instance '%ls'. Please check the database name and ensure it matches a database that is currently i…
- 45697 — An existing complete restore request for database '%ls' is already in progress on SQL managed instance '%ls'. Please wait for the current request to c…
- 45698 — Cannot create a database with special characters in its name. Special Characters include \u003C, \u003E, \u002A, \u0025, \u0026, \u003A, \u005C, \u002…
- 45699 — Database copy and geo replication are blocked on databases migrated by whiteglove restore.
- 45701 — Specified public maintenance configuration '{0}' either doesn't exist, or not applicable to the resource or not supported in this region.
- 45702 — Maintenance window feature is not supported for the named replica.
- 45703 — Maintenance window feature is not available for '%ls' hardware generation.
- 45704 — Ring buildout '%ls' does not support deletion of seedNodes.
- 45705 — Standby replicas are not supported in Elastic Pools. Neither source nor target for standby replicas may be inside an Elastic Pool.
- 45706 — Read scale-out cannot be enabled on a standby replica.
- 45707 — Key Rotation for the TDE Protector at the database level is blocked when active transactions are holding up the log encrypted with old keys. Please re…
- 45708 — Migration out of Hyperscale not supported '%ls'.
- 45709 — Specified Backup Storage Redundancy '%ls' is not supported in target region.
- 45710 — Long-term Backup Retention is not supported when Database-level CMK is configured in preview.
- 45711 — Database-level CMK is not supported when Long-term Backup Retention is enabled on the database.
- 45712 — Database-level encryption protector does not exist.
- 45713 — Database-level encryption protector can only be reverted to the server level encryption when the server is configured with Microsoft Managed Key.
- 45714 — Cross tenant CMK can only be configured when the server is configured with a User Assigned Managed Identity. For more information, see https://go.micr…
- 45715 — The preferredEnclaveType is not supported for dedicated SQL Pools.
- 45716 — Configuring the 'VBS' preferredEnclaveType for databases using the DC-series hardware configuration is not supported. DC-series databases are pre-conf…
- 45717 — Database-level encryption protector must be set on the target database while attempting to copy or replicate a database encrypted with a database leve…
- 45718 — While attempting to replicate a database configured with database level encryption protector, the current keys being used by the primary must be passe…
- 45719 — The geo-primary database must be configured with a database level encryption protector before setting a database level encryption protector on the geo…
- 45720 — The database {0} on server {1} cannot be safely dropped because it is encrypted with a customer managed key that is no longer accessible to take the l…
- 45722 — Virtualization-based security (VBS) enclaves are not supported for elastic pools.
- 45723 — Configuring geo-replication is not supported for databases using different values of the preferredEnclaveType property. The primary '{0}' database on …
- 45724 — Planned failover between primary and secondary database with different preferredEnclaveType is not supported for Virtualization-based security (VBS) e…
- 45725 — The geo-primary database must not be configured with a database level encryption protector when failing over to a geo-secondary without a database lev…
- 45726 — Operation on job agent is in progress. Please wait a gew minutes before retrying again.
- 45727 — The create database operation can not be performed at this time due to ongoing Transparent Data Encryption (TDE) key rotation on the server. Please tr…
- 45728 — Adding a database with '{0}' preferredEnclaveType to an elastic pool '{1}' with '{2}' preferredEnclaveType is not supported. Before adding the databas…
- 45731 — The elastic pool contains inaccessible databases which have lost Azure Key Vault access required for TDE configuration. Please move the accessible dat…
- 45735 — Elastic job agent '%.*ls' SLO's assignment is in progress
- 45736 — The given SLO is not supported for job agent. Please retry with the supported SLO.
- 45746 — The operation could not be completed because the Azure Key Vault Key name '%ls' is currently in use.
- 45747 — The operation could not be completed because the Azure Key Vault Key material is different than the current encryption protector key.
- 45748 — Using an old version of AKV key as TDE protector is not allowed. Please use the latest version of the AKV key as the encryption protector.
- 45749 — Per Database CMK identity not setup on the target database.
- 45750 — The create elastic pool operation cannot be performed at this time due to ongoing Transparent Data Encryption (TDE) key rotation on the server. Please…
- 45761 — Certificate with provided name is not found.
- 45762 — The certificate is not authorized to identify application.
- 45763 — Application with provided client Id is not found.
- 45764 — Internal server error.
- 45765 — Internal server error. Please contact Microsoft support and provide '%ls' code.
- 45766 — '%ls' application doesn't have sufficient privileges to manage service principal. Please configure application's permissions.
- 45767 — Failed to create service principal. Another application found with the same identifier uris.
- 45768 — Requested restore details are not available, or have expired.
- 45769 — %ls
- 45770 — Failed to move the database into elastic pool due to internal resource constraints. This may be a transient condition, please retry.
- 45771 — Import/Export with Private Link cannot be used on resources with locks. Please remove locks on the following resources and try again. %ls.
- 45772 — Perform cutover action is not supported at this time. Details: '%.*ls'.
- 45773 — The action failed because no active update-slo operation detected for server: '%.*ls', database: '%.*ls'. Please retry the operation by specifying val…
- 45774 — Invalid use of manual-cutover option for server: '%.*ls', database: '%.*ls'. Please check current and requested service objective and retry the operat…
- 45775 — One or more apps involved in UpdateSLO management operation are unhealthy for database: '%.*ls', on server: '%.*ls'.
- 45776 — The database conversion to Hyperscale timed out because manual cutover was not triggered within the allowed time, and the conversion automatically rol…
- 45777 — %ls is not yet enabled. %ls
- 45778 — The application does not exist in the tenant. Certificate cannot be uploaded to it.
- 45779 — Tenant is deauthenticated. SQL MI first party app cannot authenticate to it.
- 45781 — Database: {0}, on server: {1}, in resource group: {2}, in subscription: {3}, is a data warehouse and cannot use upgrade me now.
- 45782 — Database: {0}, on server: {1}, in resource group: {2}, in subscription: {3}, belongs to an elastic pool and cannot use upgrade me now.
- 45783 — Database: {0}, on server: {1}, in resource group: {2}, in subscription: {3}, was not found.
- 45784 — Database: {0}, on server: {1}, in resource group: {2}, in subscription: {3}, does not have UpgradeMeNow enabled.
- 45785 — ElasticPool: {0}, on server: {1}, in resource group: {2}, in subscription: {3}, was not found.
- 45786 — ElasticPool: {0}, on server: {1}, in resource group: {2}, in subscription: {3}, does not have UpgradeMeNow enabled.
- 45787 — ElasticPool: {0}, on server: {1}, in resource group: {2}, in subscription: {3}, does not contain any database.
- 45788 — The operation cannot be performed since the database '%ls' is geo-replicated and is in the secondary role. Database size limit changes are not allowed…
- 45789 — The limit of one free database offer for subscription '%.*ls' has been reached. Drop the existing free database or use a different subscription to con…
- 45790 — Operation on Long Term Retention backup failed because the backup is immutable.
- 45791 — Server '%.*ls' cannot be moved out of subscription '%.*ls' because it contains a free database. Drop or upgrade the existing free database to continue…
- 45792 — Standby Replication limit reached. The database '%ls' cannot have more than %d standby replicas.
- 45793 — You cannot create Freemium SQL Managed Instance with {0} {1}. For more details visit aka.ms/SQLMIFreemium.
- 45794 — You cannot create Freemium SQL Managed Instance on this region. For more details check aka.ms/SQLMIfreemium.
- 45795 — The operation could not be completed because there is an ongoing maintenance on your SQL managed instance subnet. All Managed Instance create/update o…
- 45796 — A data-file max size consistency error was detected during Hyperscale migration. %ls
- 45797 — Freemium is not enabled for this subscription. For more details check aka.ms/SQLMIfreemium.
- 45798 — The specified edition %ls is not consistent with the instance pool edition %ls.
- 45799 — The specified subnet %ls is not consistent with the instance pool subnet %ls.
- 45900 — The specified hardware family %ls is not consistent with the instance pool hardware family %ls.
- 45901 — The specified license type %ls is not consistent with the instance pool icense type %ls.
- 45902 — Changing the database format from '{0}' to '{1}' is not supported. Check the database format property value specified. For more information, see https…
- 45903 — Changing the database format from '{0}' to '{1}' is not supported. Check the database format property value specified. For more information, see https…
- 45904 — Changing the database format is not supported for this managed instance. Check the database format property value specified. For more information, see…
- 45905 — Specifying the database format property value is not supported at this time.
- 45906 — A freemium instance can not be created in the specified subnet %ls.
- 45907 — GeoDR links are not supported for managed instances inside managed instance pool.
- 45908 — Moving Azure SQL Managed Instance with existing auto-failover group configured into an instance pool is not supported. Remove auto-failover group from…
- 45909 — Creation of zone-redundant SQL managed instances is temporarily disabled for this Azure region. You can create zone-redundant SQL managed instances in…
- 45910 — Creation of zone-redundant SQL managed instances is temporarily disabled for this hardware generation in this Azure region. You can create zone-redund…
- 45911 — Failover group cannot be created because database format of the primary instance is not compatible with the database format of the secondary instance.…
- 45912 — Database format change must be performed on the secondary instance of the failover group first. See https://go.microsoft.com/fwlink/?linkid=2251601 fo…
- 45913 — Operation cannot be performed because database format of the source instance is not compatible with the database format of the destination instance. S…
- 45914 — Restore operation cannot be performed because database format of the source instance is not compatible with the database format of the destination ins…
- 45915 — Failover operation cannot be performed because of database format mismatch between the instances in the failover group. Consider upgrading the databas…
- 45917 — Subscription {0} already has Free SQL Managed Instance. Only one free SQL Managed Instance is allowed per subscription.
- 45918 — The '%.*ls' operation cannot be completed as there exists a database in a process of creation through failover group deployment. Please wait for the f…
- 45919 — Converting to Free SQL Managed instance is not allowed. You can only apply Free offer when you create a new SQL Managed Instance.
- 45920 — Upgrade failed. To successfully upgrade to a paid offer, ensure that you're not making any other changes to your SQL Managed Instance configuration, s…
- 45921 — You cannot stop the instance that has running operation on it's instance pool. Please wait for ongoing operation to finish or cancel ongoing operation…
- 45922 — Maintenance window is set at instance pool level and cannot be set individually per pooled instance.
- 45923 — Cannot move the instance into the pool due to pool database count limit.
- 45924 — Cannot move a zone-redundant instance into the pool as zone-redundancy is not supported in pools.
- 45925 — Deploying managed instances and instance pools into private subnets is not supported.
- 45926 — Deploying failover group is not supported with the free Azure SQL Managed Instance offer.
- 45927 — Unable to determine target service level objective. If restoring from a long-term retention backup of a database that was in an elastic pool, either t…
- 45928 — The server '%ls' already exists in this subscription in a soft-deleted state. You cannot create a server named '%ls' until the existing soft-deleted s…
- 45929 — Operation '{0}' could not be completed because the minimum TLS version required is 1.2 or higher. Earlier versions of TLS are no longer supported as t…
- 45930 — The limit of free databases for subscription '%.*ls' has been reached as part of the free database offer. To continue using for free, drop an existing…
- 45931 — Cannot resume continuous copy if Db getting resumed is already a geo-secondary for another link or DB getting resumed is in a FG and the link being re…
- 45932 — Cannot change continuous copy primary to a database that is outside of the failover group.
- 45933 — Instance maintenance window must be set to match instance pool maintenance window.
- 45934 — All databases in geo replication must contain the same key material as the encryption protector of the source database. Please add the key '%ls' with …
- 45935 — When the automatic-rotation of database level TDE Protector is enabled, both source and target databases must be connected to the same key vault. Plea…
- 45936 — While attempting to replicate a database configured with database level encryption protector, the current keys being used by the primary database must…
- 45937 — Operation '{0}' could not be completed because the maximum allowed TLS version is {1}.
- 45938 — Managed Instance geo-failover cannot be executed at this time. Reason: '%.*ls'.
- 45939 — One or more databases on SQL Managed Instance '{0}' cannot be made accessible because the corresponding inaccessibility root causes have not been miti…
- 45940 — The backup {0} cannot be deleted because there is a legal hold placed on it. Remove the legal hold and retry. backup. ErrorOwner: sqldataintegration E…
- 45941 — The operation could not be completed as the backup is not configured for immutability.
- 45942 — The operation could not be completed as the backup is immutable and locked.
- 45943 — The long-term retention backup with the desired legal hold value already exists backup file backup. ErrorOwner: sqldataintegration
- 45944 — Create and restore operations for SQL dedicated pools (formerly SQL DW) are not supported on servers within a network security perimeter. For more inf…
- 45945 — Cannot set immutability policy mode when backup immutability is not enabled.
- 45946 — Cannot change the state of the database to Inaccessible because the operation is not allowed for encryption protector from Key Vault in region '{0}'.
- 45947 — An unknown exception occurred when accessing Azure Key Vault.
- 45948 — Fabric trident server and customer managed keys doesn't belong to same tenant. Tenant Id information present for trident server is '{0}' where as KV c…
- 45949 — Database can not be added/removed to full disaster recovery failover group '%.*ls'.
- 45950 — Unable to update '%.*ls' on managed instance in the secondary role.
- 45951 — Managed Instance can not be created with reserved subnet name. The following subnet names are reserved in Azure: AzureFirewallSubnet, AzureFirewallMan…
- 45952 — Auditing enablement failed before activating database. Please enable auditing after the database is activated.
- 45953 — The revalidate TDE key operation, which attempts to bring the databases online, is not supported on geo-secondary databases. Databases that were not g…
- 45954 — The revalidate TDE key operation, which attempts to bring the database online, is not supported on geo-secondary databases. To continue, drop this dat…
- 45955 — Creating and updating multi-database capable Managed Instance link is temporarily disabled.
- 45956 — Free SQL Managed Instance only supports Locally Redundant Storage (LRS) for backup storage redundancy. Specify local backup storage redundancy to cont…
- 45957 — The planned failover operation has timed out because safety checks are taking a longer time than expected. Please try again.
- 45958 — All servers participating in active geo-replication or failover groups must maintain same key material as their encryption protectors on their partner…
- 45959 — The server identity is not configured on the partner server '{0}'. Assign the 'Key Vault Crypto Service Encryption User' RBAC role, or the Wrap, Unwra…
- 45960 — Point-in-time backup immutability cannot be locked for database %ls.
- 45961 — Changing database encryption setting is not supported for this database. Manage data encryption at rest at the workspace level.
- 45962 — Point-in-time backup immutability cannot be locked for database %ls without retention specified.
- 45963 — PITR backup immutability has already been locked for database %ls and cannot be removed.
- 45964 — Backup retention cannot be reduced from %d to %d days because backup immutability was lockd.
- 45965 — Workload type update schedule override value '%ls' is not valid. Allowed values are: %ls.
- 45966 — Workload type update schedule override is not supported with %ls.
- 45967 — Workload type update schedule override is not enabled for provided subscription %ls.
- 45968 — Workload type update schedule override values are not configured.
- 45969 — The SQL DB Control Plane first-party application is disabled in Azure tenant.
- 45970 — Auto-pause delay is not supported for Hyperscale geo-secondary database. Requested auto-pause delay: '%ls'.
- 45973 — Key revalidation for database '%ls' is blocked after the database was renamed. Unassign and reassign the managed identity associated with the database…
- 45974 — Cannot create or update this SQL managed instance in a public-production canary region because required ownership tags are missing or invalid: %ls. Sp…
- 45985 — The server cannot be dropped because immutable point-in-time restore (PITR) backups are still within retention and server delete protection is enabled…
- 45986 — Server delete protection is a permanent setting and cannot be disabled once enabled.
- 45987 — Creating a General Purpose v1 (GPv1) managed instance or changing an existing managed instance to GPv1 is not supported in API versions 2026-11-01 and…
- 46501 — External table references '%S_MSG' that does not exist.
- 46502 — Type with name '%.*ls' already exists.
- 46503 — Invalid format for option '%S_MSG'.
- 46504 — External option '%S_MSG' is not valid. Ensure that the length and range are appropriate.
- 46505 — Missing required external DDL option '%S_MSG'.
- 46506 — Invalid set of options specified for '%S_MSG'.
- 46507 — Cannot perform DML on external tables.
- 46508 — Incorrect syntax on external DDL option '%S_MSG'.
- 46509 — FILE_FORMAT must be specified for HADOOP data source.
- 46510 — FILE_FORMAT cannot be specified for RDBMS data source.
- 46511 — EXTERNAL %S_MSG with id %d cannot be found.
- 46512 — %S_MSG cannot be used with %S_MSG data source.
- 46513 — A sharding column name must be provided when using SHARDED distribution.
- 46514 — DISTRIBUTION must be specified when using a SHARD_MAP_MANGER data source.
- 46515 — The specified sharding column name does not match any column in the external table definition.
- 46516 — The specified credential cannot be found or the user does not have permission to perform this action.
- 46517 — XML Parse error when de-serializing PDW Metadata.
- 46518 — The %S_MSG '%ls' is not supported with %S_MSG.
- 46519 — %ls are not supported with %S_MSG.
- 46520 — The external DDL statement contained an unrecognized option.
- 46521 — Queries over external tables are not supported with the current service tier or performance level of this database. Consider upgrading the service tie…
- 46522 — Failed to update '%S_MSG'.
- 46523 — A SCHEMA_NAME must be specified when using OBJECT_NAME.
- 46524 — An OBJECT_NAME must be specified when using SCHEMA_NAME.
- 46525 — External tables are not supported with the %S_MSG data source type.
- 46526 — The %S_MSG operation is not supported with %S_MSG data source type.
- 46527 — Altering the '%S_MSG' property is not permitted for an external data source of type %ls.
- 46528 — SHARDED DISTRIBUTION is allowed for SHARD_MAP_MANGER data source only.
- 46529 — Allowed integer values for FIRST_ROW are between and including 1-101
- 46530 — External data sources are not supported with type %S_MSG.
- 46531 — Support for external data sources of type HADOOP is not enabled. To enable, set 'hadoop connectivity' to desired value.
- 46532 — Sp_rename is not supported for data pool external table.
- 46533 — Internal error occurred during distributed operation.
- 46534 — A maximum of three NULL_VALUES are allowed in the list.
- 46535 — Unable to retrieve secret [%s] from the secret store.
- 46536 — Unable to process secret [%s] from the secret store.
- 46537 — An unexpected internal error, failed to communicate with controller service, HRESULT 0x%x.
- 46538 — An unexpected internal error received from controller service error code [%i].
- 46539 — '%S_MSG' statement failed. At least one partitioning column is required when distribution type is '%S_MSG'.
- 46540 — '%S_MSG' statement failed. Partitioning columns can be specified only if distribution type is '%S_MSG'.
- 46541 — '%S_MSG' statement failed. The column name '%.*ls' specified in the '%S_MSG' option does not match any columns specified in the external table definit…
- 46542 — %S_MSG statement failed. One or more errors occurred while executing the statement. %s
- 46543 — %S_MSG statement failed. Invalid URI provided.
- 46544 — Temporary tables are not supported for this type of external tables.
- 46545 — Creating external data source over data pools is not supported in a system database.
- 46546 — Alter database name is not supported in Big Data Cluster if the database contains external data pool tables. Drop the tables to perform the operation.
- 46547 — CREATE EXTERNAL TABLE failed, because it attempted to set the %.*ls option multiple times.
- 46548 — '%ls' contains an unsupported prefix. Retry with supported connector prefix.
- 46549 — Use of external data source with '%ls' type and '%ls' connector prefix is not supported.
- 46550 — Connector specified in external data source location '%ls' requires FILE_FORMAT to be set.
- 46551 — %ls external table is either not supported or disabled on the server. See 'http://aka.ms/sqlsrvrerrmsg46551' for assistance.
- 46552 — Writing into an external table is disabled. See ' https://go.microsoft.com/fwlink/?linkid=2201073 ' for more information.
- 46553 — Create External Table as Select is disabled. See sp_configure 'allow polybase export' option to enable.
- 46554 — External Table '%.*ls' contains corrupted metadata. Drop external table and create a new one.
- 46555 — CREATE EXTERNAL MODEL failed because the user "%.*ls" specified in the authorization clause does not exist.
- 46556 — Cannot drop the credential '%.*ls' because it is used by an external model.
- 46557 — Argument '%.*ls' is invalid. Please provide a valid Json document.
- 46558 — Option '%S_MSG' is not supported for external tables.
- 46559 — Local temporary external tables are not supported in this edition of SQL Server.
- 46560 — External Table Location option must be a valid OneLake path.
- 46601 — REJECT_TYPE
- 46602 — FILE_FORMAT
- 46603 — REJECT_VALUE
- 46604 — REJECT_SAMPLE_VALUE
- 46605 — LOCATION
- 46606 — DATA_SOURCE
- 46607 — PERCENTAGE
- 46608 — ROW_TERMINATOR
- 46609 — DATA_COMPRESSION
- 46610 — SERDE_METHOD
- 46611 — ENCODING
- 46612 — STRING_DELIMITER
- 46613 — DATE_FORMAT
- 46614 — FIELD_TERMINATOR
- 46615 — FORMAT_TYPE
- 46616 — JOB_TRACKER_LOCATION
- 46617 — EXTERNAL TABLE
- 46618 — HADOOP
- 46619 — RDBMS
- 46620 — SHARD_MAP_MANGER
- 46621 — SHARDING_COLUMN_NAME
- 46622 — DISTRIBUTION
- 46623 — DATABASE_NAME
- 46624 — SHARD_MAP_NAME
- 46625 — CREDENTIAL
- 46626 — REMOTE_SCHEMA_NAME
- 46627 — REMOTE_OBJECT_NAME
- 46628 — SHARED_MEMORY
- 46629 — EXTRACTOR
- 46643 — external tables
- 46644 — external tables for sharded data
- 46645 — Remote Data Archive
- 46646 — provided
- 46647 — seconds
- 46648 — minutes
- 46649 — hours
- 46650 — days
- 46651 — weeks
- 46652 — months
- 46653 — years
- 46654 — database scoped credential
- 46655 — rejected rows location
- 46656 — CONNECTION_OPTIONS
- 46657 — PUSHDOWN
- 46658 — GENERIC
- 46659 — BLOB_STORAGE
- 46660 — GENERIC
- 46661 — CREATE EXTERNAL TABLE
- 46662 — HASH
- 46663 — PARTITION
- 46664 — DROP EXTERNAL TABLE
- 46665 — TRUNCATE EXTERNAL TABLE
- 46666 — ALTER DATABASE
- 46667 — DROP DATABASE
- 46668 — PARSER_VERSION
- 46669 — ERRORFILE_DATA_SOURCE
- 46670 — TABLE_OPTIONS
- 46671 — INTERNAL TABLE
- 46672 — API_FORMAT
- 46673 — MODEL_TYPE
- 46674 — MODEL
- 46675 — PARAMETERS
- 46676 — SET_PARAMETER
- 46677 — LOCAL_RUNTIME_PATH
- 46678 — schema-inferred external tables
- 46679 — system-defined
- 46701 — Query notifications is not an implemented feature for SQL Server Parallel DataWarehousing TDS endpoint.
- 46702 — Remote RPC requests are not an implemented feature for SQL Server Parallel DataWarehousing TDS endpoint.
- 46703 — Conversion error while attempting conversion between IPC blob parameter.
- 46704 — Large object column support in SQL Server Parallel DataWarehouse server is limited to only nvarchar(max) data type.
- 46705 — Unsupported parameter type found while parsing RPC request. The request has been terminated.
- 46706 — Cursor support is not an implemented feature for SQL Server Parallel DataWarehousing TDS endpoint.
- 46707 — The given IPC request with code %d is not supported for SQL Server Parallel DataWarehousing TDS endpoint.
- 46709 — Default parameter support is not an implemented feature for SQL Server Parallel DataWarehousing TDS endpoint.
- 46710 — Unsupported transaction manager request %d encountered. SQL Server Parallel DataWarehousing TDS endpoint only supports local transaction request for '…
- 46711 — Unsupported TDS request packet of type %d encountered on SQL Server Parallel DataWarehousing TDS endpoint. Only batch, rpc and transaction requests ar…
- 46712 — Unexpected error encountered during request processing. Connection will be terminated.
- 46713 — Integrated authentication is not an implemented feature for SQL Server Parallel DataWarehousing TDS endpoint.
- 46716 — Attach Database File is not an implemented feature for SQL Server Parallel DataWarehousing TDS endpoint.
- 46717 — Login as Replication or Remote user is not supported by SQL Server Parallel DataWarehousing TDS endpoint.
- 46718 — Only 'us_english' or 'English' language is supported by SQL Server Parallel DataWarehousing TDS endpoint.
- 46719 — Attempt to reset connection with 'Keep Transaction' failed because the incoming request was not a commit/rollback request. This error can occur if mor…
- 46720 — Parallel query execution on the same connection is not supported.
- 46721 — Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication.
- 46722 — Client driver version is not supported.
- 46723 — Large object column in Global Query is not supported for types other than Nvarchar(MAX), Varchar(MAX), Varbinary(MAX) and Image.
- 46724 — Communication error during bulk copy operation.
- 46801 — GlobalQuery operations
- 46802 — Failed to load module for global query.
- 46803 — Failed to locate entry point for global query module.
- 46804 — Failed to initialize the global query module.
- 46805 — Conversion error while constructing the GlobalQuery request.
- 46806 — An error occurred while executing GlobalQuery operation: %.*ls
- 46807 — An access violation occurred while performing GlobalQuery operation. Execution has been aborted.
- 46808 — An entry corresponding to given Global Query request could not be located. Execution has been aborted.
- 46809 — An error occurred while attempting to execute the Global Query request. Error Code: %d, Severity: %d, State: %d.
- 46810 — An unhandled exception occurred while performing GlobalQuery operation. Execution has been aborted.
- 46811 — An unexpected error with code 0x%x occurred while executing GlobalQuery operation.
- 46812 — %.*ls
- 46813 — %.*ls
- 46814 — %.*ls
- 46815 — %.*ls
- 46816 — %.*ls
- 46817 — %.*ls
- 46818 — %.*ls
- 46819 — %.*ls
- 46820 — %.*ls
- 46821 — %.*ls
- 46822 — %.*ls
- 46823 — %.*ls
- 46824 — %.*ls
- 46825 — %.*ls
- 46826 — Output parameters are not supported with %.*ls.
- 46827 — The option '%ls' must be turned ON to execute queries referencing external tables.
- 46828 — The USE PLAN hint is not supported for queries that reference external tables. Consider removing USE PLAN hint.
- 46829 — The proc %.*ls is only supported for external data sources of type SHARD_MAP_MANAGER or RDBMS.
- 46830 — Internal column references are not supported for external tables.
- 46831 — Provided argument exceeds the current size limit of %u bytes for procedure %.*ls.
- 46832 — An error occurred while establishing connection to remote data source: %ls
- 46833 — An error occurred while executing query on remote server: %ls
- 46834 — An error occurred while retrieving data from remote server: %ls
- 46835 — An error occurred while initializing Global Query: %ls
- 46836 — External table schema does not match actual schema from remote table: %ls
- 46837 — An error occurred while fetching table metadata in Global Query: %ls
- 46838 — An error occurred while fetching data in Global Query: %ls
- 46839 — An error occurred while cancelling Global Query operation: %ls
- 46840 — An error occurred during Global Query cleanup: %ls
- 46841 — An error occurred while executing Global Query operation: %ls
- 46842 — Logical server %ls defined in the elastic query configuration is not in the list of Outbound Firewall Rules on the server. Please add this logical ser…
- 46843 — External data sources of SHARD_MAP_MANAGER type cannot be queried when outbound firewall rules are set.
- 46844 — Microsoft Entra ID only external data sources cannot be queried when not connected using Microsoft Entra authentication.
- 46845 — Logins that query external data sources using Microsoft Entra authentication are not supported.
- 46901 — Stored procedure finished successfully. Polybase engine service is disabled. Please restart Polybase DMS service.
- 46902 — Stored procedure finished successfully. Polybase engine service is enabled. Please restart Polybase engine and DMS services.
- 46903 — This stored procedure is not available because Polybase feature is not enabled.
- 46904 — Failed to get the computer name. This might indicate a problem with the network configuration of the computer. Error: %ls.
- 46905 — Head node cannot be removed from a Polybase computational group.
- 46906 — Unable to retrieve registry value '%ls' from Windows registry key '%ls': %ls.
- 46907 — Unable to delete registry value '%ls' from Windows registry key '%ls': %ls.
- 46908 — Unable to update registry value '%ls' in Windows registry key '%ls': %ls.
- 46909 — Unable to open registry key '%ls': %ls.
- 46910 — Incorrect number of parameters specified for procedure.
- 46911 — Procedure expects parameter '%ls' of type '%ls'.
- 46912 — The option '%ls' must be turned ON to execute requests referencing external tables.
- 46913 — The USE PLAN hint is not supported for queries that reference external tables. Consider removing USE PLAN hint.
- 46914 — INSERT into external table is disabled. Turn on the configuration option 'allow polybase export' to enable.
- 46915 — Table hints are not supported on queries that reference external tables.
- 46916 — Queries that reference external tables are not supported by the legacy cardinality estimation framework. Ensure that trace flag 9481 is not enabled, t…
- 46917 — An internal error occured while attempting to retrieve the encrypted database-scoped credential secret.
- 46918 — An internal error occured while attempting to retrieve the encrypted database-scoped credential secret.
- 46919 — An internal error occured while attempting to retrieve the encrypted database-scoped credential secret.
- 46920 — Polybase feature disabled.
- 46921 — The EXECUTE AT DATA_SOURCE command is not supported for this external data source type.
- 46922 — PolyBase provisioning script performing on master database failed. This is a serious error which might prevent the SQL Server instance from starting. …
- 46923 — PolyBase feature is not installed. Please consult Books Online for more information on this feature.
- 46924 — SQL Server failed to start PolyBase processes due to error 0x%lx.
- 46925 — SQL Server failed to start PolyBase request due to error 0x%lx.
- 46926 — Failed to get PolyBase service account due to error '%ls'.
- 46927 — SQL Server failed to get memory for PolyBase startup.
- 46928 — The specified operation is not supported for this external data source type.
- 46929 — The value '%ld' is not within range for the parameter '%ls'.
- 46930 — PolyBase is not enabled because reading of PolyBase registry entries failed.
- 46931 — PolyBase is not enabled due to error code 0x%lx.
- 46932 — Unable to read PolyBase registry entries.
- 46933 — PolyBase configuration is invalid or corrupt. Re-run PolyBase setup.
- 46934 — The option 'hadoop connectivity' cannot be enabled in this edition of SQL Server.
- 46935 — Cannot obtain S3 temporary credentials to access S3.
- 46936 — Unable to fetch Json Web Token due to insufficient memory.
- 46937 — Unable to fetch Json Web Token due to internal error.
- 46938 — Invalid ADFS endpoint. Please check ADFS %s endpoint specified in connection options for the external data source.
- 46939 — Unable to process response from ADFS endpoint %s.
- 46940 — Unable to send request to ADFS endpoint %s due to error %d.
- 46941 — Request to ADFS endpoint %s failed. Http response status code: %d.
- 46942 — Unable to obtain JSON Web Token from ADFS endpoint %s.
- 46943 — Unable to fetch S3 temporary credentials from STS due to insufficient memory.
- 46944 — Unable to fetch S3 temporary credentials from STS due to internal error.
- 46945 — Invalid STS endpoint. Please check STS endpoint %s specified in connection options for the external data source.
- 46946 — Unable to process response from STS endpoint %s.
- 46947 — Unable to send request to STS endpoint %s due to error %d.
- 46948 — Request to STS endpoint %s failed. Http response status code: %d.
- 46949 — Unable to obtain S3 temporary credentials from STS endpoint %s.
- 46950 — Invalid Json formatting of connection options specified in external data source.
- 46951 — Failure in getting '%s' element from connection options.
- 46952 — Failed to impersonate logged on user when trying to fetch Json Web Token.
- 46953 — Pass through authorization using S3 temporary credentials is not supported. Please use S3 credentials to access storage.
- 46954 — Number of columns specified in '%ls' exceeds the number of columns in external table.
- 46955 — External table not found or you do not have permission to access it. Underlying data description: %ls.
- 46956 — Failed to extract rows from external table. Underlying data description: %ls.
- 46957 — Error encountered while extracting data from external table '%ls'. Underlying data description: %ls.
- 46958 — Columns '%ls' were not found when querying external table. Underlying data description: %ls.
- 46959 — Error encoutered in '%S_MSG' parameter. Expected three part name, but found '%ls'.
- 46960 — Try to reuse default credential name '%.*ls' but its IDENTITY attribute is not 'USER IDENTITY'.
- 46961 — Try to reuse default external data source name '%.*ls' but its LOCATION attribute does not match table location.
- 46962 — Try to reuse default external file format name '%.*ls' but its FORMAT_TYPE attribute '%.*ls' is not consistent with the default file format name.
- 46963 — Try to use a default external file format for file '%.*ls' but could not deduce a supported FORMAT_TYPE for the given extension.
- 46964 — Fail to create the default credential, data source or file format.
- 46965 — Error encountered in fetching delta table rows for file %s. (HRESULT = 0x%x).
- 46966 — Error in reading delta table rows for file %s : %s.
- 46967 — Delta table schema has column '%ls' with unsupported complex type '%ls'.
- 46968 — Error in Delta resolver for file %s : %s.
- 46969 — Selected column does not exist: column '%ls' specified in the WITH clause was not found in the Delta table schema at '%ls'.
- 46970 — Extensibility operation failed for file %s: %s.
- 46971 — A transaction cannot write to multiple databases in an elastic pool.
- 47000 — Reason: FedAuth RPS Initialization failed when fetching CLSID of RPS ProgID.
- 47001 — Reason: FedAuth RPS Initialization failed when creating instance of Passport.RPS COM Object.
- 47002 — Reason: FedAuth RPS Initialization failed when initializing the RPS COM object.
- 47003 — Reason: FedAuth RPS Authentication failed when getting IRPSAuth object.
- 47004 — Reason: FedAuth RPS Authentication failed when getting IRPSPropBag object.
- 47005 — Reason: FedAuth RPS Authentication failed during IRPS::Authenticate.
- 47006 — Reason: FedAuth RPS Authentication failed when getting IRPSValidatedPropertyBag object.
- 47007 — Reason: FedAuth RPS Authentication failed during SetAuthPolicy.
- 47008 — Reason: FedAuth RPS Authentication failed during ValidateTicketWithAuthPolicy.
- 47009 — Reason: FedAuth RPS Authentication failed when fetching Session Key.
- 47010 — Reason: FedAuth RPS Authentication failed when initializing HMAC Hash object.
- 47011 — Reason: FedAuth RPS Authentication failed when computing HMAC Hash Signature.
- 47012 — Reason: FedAuth RPS Authentication failed when comparing HMAC Hash Signature with the one sent by the client.
- 47013 — Reason: FedAuth RPS Authentication failed when fetching MemberId Low.
- 47014 — Reason: FedAuth RPS Authentication failed when fetching MemberId High.
- 47015 — Reason: FedAuth RPS Authentication failed when fetching MemberName.
- 47016 — Reason: FedAuth AzureActiveDirectoryService Initialization failed when opening Certificate Store.
- 47017 — Reason: FedAuth AzureActiveDirectoryService Initialization failed when trying to find ceritificate in store.
- 47018 — Reason: FedAuth AzureActiveDirectoryService Initialization failed when trying to initialize Error object for service proxy.
- 47019 — Reason: FedAuth AzureActiveDirectoryService Initialization failed when trying to create service proxy.
- 47020 — Reason: FedAuth AzureActiveDirectoryService Initialization failed when trying to open service proxy.
- 47021 — Reason: FedAuth AzureActiveDirectoryService Group Expansion failed when trying to initialize Heap object.
- 47022 — Reason: FedAuth AzureActiveDirectoryService Group Expansion failed when trying to initialize Error object.
- 47023 — Reason: FedAuth AzureActiveDirectoryService Group Expansion failed during Group Membership Lookup.
- 47024 — Reason: FedAuth AzureActiveDirectoryService Group Expansion failed during validation of federated context.
- 47025 — Reason: FedAuth AzureActiveDirectoryService Group Expansion failed due to unknown reason.
- 47026 — Reason: Failure occurred when trying to fetch the HMAC signature of prelogin client nonce to set FeatureExtAck
- 47027 — Reason: This was a non-Microsoft domain login attempt in a Non-SDS session.
- 47028 — Reason: This FedAuth library is not supported by the security layer for authentication.
- 47029 — Reason: This FedAuth Ticket type is not supported by the security layer for authentication.
- 47030 — Reason: The Feature Switch for this FedAuth protocol is OFF.
- 47031 — Reason: There was a failure in acquiring the max heap memory limit from config during AAD group expansion.
- 47032 — Reason: There is a user error in FedAuth token parsing. There should be a seperate XEvent called 'fedauth_web_token_failure' which indicate the actual…
- 47033 — Reason: There is a System error in FedAuth token parsing. There should be a seperate XEvent called 'fedauth_web_token_failure' which indicate the actu…
- 47034 — Reason: Authentication was successful, but database is in Recovering state.
- 47035 — Reason: Login failed because it was attempting to use integrated authentication, which we do not support.
- 47036 — Reason: Login failed because USE db failed while checking firewall rules.
- 47037 — Reason: Login failed because Deny External Connections flags is on.
- 47038 — Reason: Login failed because client disconnected when fedauth specific processing was going on during login.
- 47039 — Reason: Login failed because the client is attempting to use certificate authentication without correct permissions.
- 47040 — Reason: Login failed because database is not found.
- 47041 — Reason: Login failed because login token feature extension is not present.
- 47042 — Reason: Login failed because login token feature extension is malformed.
- 47043 — Reason: Token-based server access validation failed with an infrastructure error. Login is disabled.
- 47044 — Reason: Login-based server access validation failed with an infrastructure error. Login is disabled.
- 47045 — Reason: Token-based server access validation failed with an infrastructure error. Login lacks Connect SQL permission.
- 47046 — Reason: Login-based server access validation failed with an infrastructure error. Login lacks Connect SQL permission.
- 47047 — Reason: Token-based server access validation failed with an infrastructure error. Login lacks connect endpoint permission.
- 47048 — Reason: Login-based server access validation failed with an infrastructure error. Login lacks connect endpoint permission.
- 47049 — Reason: VNET Firewall Rule has rejected the login.
- 47050 — Reason: Unexpected error while copying the VNET IPv6 address.
- 47051 — Reason: Unexpected error while parsing the VNET IPv6.
- 47052 — Reason: Unexpected error while extracting VNET metadata info from the IPv6 (VNET parsing).
- 47053 — Reason: Unexpected error on VNET firewall rule table lookup.
- 47054 — Reason: Unexpected error on VNET firewall rule table COUNT lookup.
- 47055 — Reason: VNET Firewall rejected the login due to a the source of a login being outside a VNET
- 47056 — Reason: Firewall rejected the login attempt because VNET firewall rules are not database-level, only server-level.
- 47057 — Reason: Firewall rejected the login because an IPv6 attempt was received when not expected
- 47058 — Reason: Unexpected error on VNET firewall rule table lookup while looking up the IPv4 Allow All rule.
- 47059 — Reason: Unexpected error while swapping the session peer address with the VNET CA.
- 47060 — Reason: Unexpected error on TDS readhandler, payload length > sni packet buf size
- 47061 — Reason: Replicated Master is not ready at this point and user connections are disallowed.
- 47062 — Reason: lock timeout expired while looking up interface endpoints list
- 47063 — Reason: lock timeout expired while looking up interface endpoints list
- 47064 — Reason: The incoming login VNET metadata was not found in the list of interface endpoints configured
- 47065 — Reason: Unexpected error on Interface Endpoints access lockdown check
- 47066 — Reason: Allow All Azure rule can't be evaluated at DB level Firewall Rule for Interface Endpoints connections
- 47067 — Reason: Internal error. Unexpected frontend connection to Vldb page server.
- 47068 — fulltext stoplist
- 47069 — Reason: Replicated Master is not online at this point and user connections are disallowed.
- 47070 — Reason: Azure Active Directory only authentication is enabled. Please contact your system administrator.
- 47071 — Reason: Login failed because login token present in the feature extension is invalid.
- 47072 — Reason: Login failed due to client TLS version being less than minimal TLS version allowed by the server.
- 47073 — Reason: An instance-specific error occurred while establishing a connection to SQL Server. Connection was denied since Deny Public Network Access is s…
- 47074 — The login was denied since the target is not part of a Network Security Perimeter.
- 47075 — Connections to this database are no longer allowed.
- 47076 — Server access failure due to RBAC Deny.
- 47077 — Login was denied since the token used was malformed.
- 47078 — Login was denied since an incorrect token type was used.
- 47079 — Login was denied since perms were requested on an invalid database.
- 47080 — User has insufficient permissions to complete the login.
- 47081 — Cannot verify connect permissions on database '%ls'.
- 47082 — Cannot verify connect permissions on the default database.
- 47083 — Token is expired.
- 47084 — Incorrect or invalid token.
- 47085 — The server is not currently configured to accept this token.
- 47086 — Could not verify credentials on connected endpoint.
- 47087 — Reason: Azure Active Directory only authentication is enabled. Please contact your system administrator.
- 47088 — Reason: Login failed because of invalid feature extension offset.
- 47089 — Reason: Login failed because Azure Dns Caching feature extension is malformed.
- 47090 — Internal API Error. Result %d, File Name %s, Line Number %d
- 47091 — Reason: Login failed because login does not have CONNECT permission on the specified SQL Pool.
- 47092 — Reason: Login failed because login to Datawarehouse Reserved Databases are not allowed.
- 47093 — Reason: Retrieving IPv6 address failed.
- 47094 — Reason: Retrieving IPv6 server firewall rules failed.
- 47095 — Reason: Retrieving IPv6 server database firewall rules failed.
- 47096 — Reason: Login to public IPv6 endpoint is disabled.
- 47097 — Reason: Login to public IPv6 endpoint from an IPv4 source is disabled.
- 47098 — Reason: Retrieving IPv4 address from IPv4 mapped IPv6 address failed.
- 47099 — Sql Authentication connections are not supported.
- 47100 — The cluster type of availability group '%.*ls' doesn't match its primary configuration. Verify that the specified availability group cluster type is c…
- 47101 — The cluster type of availability group '%.*ls' only supports MANUAL failover mode. Verify that the specified availability group cluster type is correc…
- 47102 — The cluster type of availability group '%.*ls' only supports EXTERNAL failover mode. Verify that the specified availability group cluster type is corr…
- 47103 — The cluster type of availability group '%.*ls' only supports AUTOMATIC and MANUAL failover modes. Verify that the specified availability group cluster…
- 47104 — This operation cannot be performed on the availability group '%.*ls' because it has EXTERNAL cluster type. Use the cluster management tools to perform…
- 47105 — The Always On Availability Groups feature must be enabled for this server instance before you can perform availability group operations. Please enable…
- 47106 — Cannot join availability group '%.*ls'. Download configuration timeout. Please check primary configuration, network connectivity and firewall setup, t…
- 47107 — The %ls operation is not allowed by the current availability group configuration. The availability group '%.*ls' only supports one relica which has co…
- 47108 — The %ls operation is not allowed by the current availability group configuration. The availability group '%.*ls' only supports two synchronous mode re…
- 47109 — Availability group '%.*ls' cannot failover to this replica. Configuration-only replica cannot become primary. An attempt to fail over an availability …
- 47110 — The '%.*ls' option is not valid for the '%.*ls' replica as it is a configuration-only. Remove this option, then retry the operation
- 47111 — Local availability replica for availability group '%.*ls' cannot be granted permission to create databases. The replica is a configuration-only and ca…
- 47112 — Only the SESSION_TIMEOUT property can be modified for a configuration-only replica.
- 47113 — The '%.*ls' option is not valid for the '%.*ls' replica for modification. Remove this option, then retry the operation.
- 47114 — Availability replica '%.*ls' cannot be added to availability group '%.*ls'. Configuration-only replicas can only be added to availability groups with …
- 47115 — The '%ls' option is not valid for WSFC availability group '%.*ls'. Remove the option or set the 'CLUSTER_TYPE' option to a different value, then retry…
- 47116 — The external lease cannot be set on availability group '%.*ls'. External Lease updates are not enabled for this availability group.
- 47117 — The '%ls' option must be specified with a valid time value when updating the Availability Group's external write lease status on availability group '%…
- 47118 — The '%ls' option must be specified with a valid value when updating the external lease status on availability group '%.*ls'.
- 47119 — The current write lease of the availability group '%.*ls' is still valid. The lease expiration time cannot be set to an earlier time than its current …
- 47120 — The READ_WRITE_ROUTING_URL '%.*ls' specified for availability replica '%.*ls' is not valid. It does not follow the required format of 'TCP://system-ad…
- 47121 — The replica spec for the local replica '%.*ls' has an invalid availability mode. Valid values are SYNCHRONOUS_COMMIT and ASYNCHRONOUS_COMMIT.
- 47122 — Cannot failover an availability replica for availability group '%.*ls' since it has CLUSTER_TYPE = NONE. Only force failover is supported in this vers…
- 47123 — Creating contained availability group '%.*ls' failed. No other availability groups can exist before creating contained availability group. Verify spec…
- 47124 — Creation of contained availability group master database failed. Only contained availability group can create contained availability group master data…
- 47125 — Joining contained availability group '%.*ls' has failed. Verify there is no other availability group existed, then retry the operation.
- 47126 — Joining contained availability group '%.*ls' failed. Verify that user databases are not present, then retry the operation.
- 47127 — Joining or creating contained availability group '%.*ls' failed. The SQL Server instance is not enabled to create or join contained availability group…
- 47129 — Creating Distributed availability group '%.*ls' has failed. Cannot create Distributed Availability Group on top of Contained Availability Group. Verif…
- 47130 — Creating contained availability group '%.*ls' failed. When creating contained availability group, both master database and msdb database must be inclu…
- 47131 — Creating or joining availability group '%.*ls' failed because there is a contained availability group. Remove contained availability group, then retry…
- 47132 — Joining availability group '%.*ls' with rebuilding contained system DB has failed because rebuilding contained MSDB has failed. This is caused by cont…
- 47133 — Joining availability group '%.*ls' with rebuilding contained system databases has failed because rebuilding contained availability group master databa…
- 47134 — Joining availability group '%.*ls' with 'REBUILD_SYSTEM_DATABASES' has failed. 'REBUILD_SYSTEM_DATABASES' is only valid for joining contained availabi…
- 47135 — Contained availability group system database '%.*ls' cannot be removed from contained availability group '%.*ls'.
- 47136 — Cannot add database '%.*ls' to contained availability group '%.*ls' because it is in the exclusion list. Remove the excluded database from the databas…
- 47137 — Cannot create contained system databases in contained availability group '%.*ls' It might be caused by temporary condition. Retry the operation.
- 47138 — Joining contained availability group '%.*ls' without rebuilding contained system DB has failed because availability group master '%.*ls' had incorrect…
- 47139 — Join contained availability group '%.*ls' failed to create group master '%.*ls' Database ID. Please retry the operation again.
- 47140 — Starting contained availability group '%.*ls' failed. Contained availability group system database '%.*ls' (id = %d) failed to load during startup.
- 47141 — Starting contained availability group '%.*ls' failed. One of contained system databases (masterdbid = %d, msdbid = %d) failed to load during startup.
- 47142 — Creating contained availability group '%.*ls' failed. One of contained system database '%.*ls' already exists. Remove it or add 'reuse_system_database…
- 47143 — Option 'reuse_system_databases' is invalid for creating availability group '%.*ls'. Option 'reuse_system_databases' can only be used with contained av…
- 47144 — Option 'autoseeding_system_databases' is invalid for creating availability group '%.*ls'. Option 'autoseeding_system_databases' can only be used with …
- 47145 — Failed to obtain the resource handle for cluster resource with name or ID '%.*ls'. Cluster service may not be running or may not be accessible in its …
- 47146 — Invalid characters '%ls' found in name '%.*ls' for contained availability group. Remove invalid characters and retry the operation.
- 47147 — Creating contained availability group '%.*ls' failed. When creating contained availability group, neither master database nor msdb database can be inc…
- 47148 — Cannot join database '%.*ls' to contained availability group '%.*ls'. Before joining other databases to contained availability group, contained availa…
- 47149 — Cannot start the job "%s" because this is secondary replica of contained availability group. Start the job in the primary replica of this contained av…
- 47150 — Option 'autoseeding_system_databases' and 'reuse_system_databases' cannot be set at same time for creating availability group '%.*ls'. remove one opti…
- 47151 — Failed to create availability group '%.*ls' with contained clause. It is invalid for this edition. Remove contained clause and retry the operation.
- 47152 — Availability group '%.*ls' that has EXTERNAL or NONE cluster type contains too many databases. Remove some databases from the availability group and r…
- 47201 — Procedure expects '%u' parameters.
- 47202 — Procedure expects '%u' parameters and '%u' for _ex version.
- 47203 — Procedure expects atleast '%u' parameters and '%u' max.
- 47204 — Output parameter '%.*ls' has declared size %u bytes, which is less than the required size of %u bytes.
- 47301 — Data Retention cleanup is disabled for this database. Data Retention cleanup must be enabled on a database to enable data cleanup.
- 47302 — Data Retention Cleanup cannot be applied on table '%.*ls' because it has infinite retention period.
- 47303 — Data retention cleanup on table(database id %lu, table id %ld) cannot be executed. Either data retention cleanup is disabled on the database, appropri…
- 47304 — %ld is not a valid value for data retention period.
- 47305 — '%.*ls' is not a valid period unit for data retention.
- 47306 — The period of %ld %S_MSG is too big for data retention.
- 47307 — Filter column '%.*ls' has unsupported datatype for data retention.
- 47308 — Filter column '%.*ls' does not exist in the target table or view.
- 47309 — Drop column operation failed on table '%.*ls' because the column is being used as a filter column for data retention.
- 47310 — '%.*ls' is being used as the filter column for data retention. Altering the filter column while data retention is 'on' is not supported.
- 47311 — FILTER_COLUMN for data retention has not been defined for table '%.*ls'.
- 47312 — Data retention cannot be set on temporal history table.
- 47313 — Data retention cannot be set on ledger tables or their history tables.
- 47314 — Policy based data retention is not supported for system databases.
- 47401 — Procedure expects '%u' parameters.
- 47402 — Procedure sp_manage_distributed_transaction was called with invalid operation.
- 47403 — MSDTC operation %s on transaction %s failed, %s
- 47404 — Resetting MSDTC log failed, %s.
- 47405 — MSDTC WMI Error, %ls.
- 47406 — WMI cannot connnect, it may not be installed.
- 47407 — Unexpected internal error related to MS DTC.
- 47500 — Manual seeding is not supported option for secondary AG '%.*ls' configuration when secondary participant in distributed availability group is Azure SQ…
- 47501 — Synchronous commit is not supported option for the initial secondary AG '%.*ls' configuration when secondary participant in distributed availability g…
- 47502 — Cannot create distributed availability group '%.*ls' when local AG '%.*ls' contains more than one database in cases when secondary participant is Azur…
- 47503 — AG '%.*ls' already contains one database and adding more is not supported because AG participates in distributed availability group '%.*ls' with secon…
- 47504 — Error related to distributed availability group '%.*ls' with secondary participant on Azure SQL Managed Instance.
- 47505 — Endpoint with type %d does not exist or user does not have permission to view it.
- 47506 — Certificate for endpoint with type %d does not exist or user does not have permission to view it.
- 47507 — Adding memory optimized files to the database replicated to Azure SQL Managed Instance is not supported because its service tier does not support In-m…
- 47508 — Adding multiple log files to the database replicated to Azure SQL Managed Instance is not supported because managed instance does not support multiple…
- 47509 — Adding FileStream or FileTables to the database replicated to Azure SQL Managed Instance is not supported because managed instance does not support Fi…
- 47510 — Adding multiple memory optimized files to the database replicated to Azure SQL Managed Instance is not supported because managed instance does not sup…
- 47511 — Distributed availability group '%.*ls' is not part of the link with Azure SQL Managed Instance. Please create a link between SQL Server and Managed In…
- 47512 — '%ls' cannot be changed during a failover operation in progress. Try again later when the failover is complete.
- 47513 — FAILOVER cannot be started as a previous failover operation is in progress. Try again later when the failover is complete.
- 47514 — Failover cannot be completed as the secondary is unable to catchup with the primary due to synchronization issues. Please check for and correct any li…
- 47515 — Failover cannot be completed because the send queue is too large. Secondary cannot catch up with the primary most likely because workload on the prima…
- 47516 — Failover cannot be completed as the redo log is too large. Most likely secondary might be too busy, or the workload from the primary is too demanding.…
- 47517 — This type of failover can only be executed on the primary replica. Connect to the primary replica, and retry the operation again.
- 47518 — Adding memory optimized table to the database replicated to Azure SQL Managed Instance is not supported because its service tier does not support In-m…
- 47519 — Cannot create distributed availability group '%.*ls' when local AG '%.*ls' does not contain database in cases when secondary participant is Azure SQL …
- 47520 — Database cannot be removed from availability group which participates in distributed availability group in which secondary participant is Azure SQL Ma…
- 47521 — Secondary replica could not be built as the replica request was not received from the primary, or not processed correctly. Check the state of the prim…
- 47522 — Database '%.*ls' has been removed from availability group which participates in Azure SQL Managed Instance link.
- 47523 — 'ALTER AVAILABILITY GROUP MODIFY AVAILABILITY GROUP' command failed. Specified option is not supported for altering distributed availability group in …
- 47524 — A planned failover of Azure SQL Managed Instance link cannot be initiated from the secondary instance. Initiate failover from the primary instance for…
- 47525 — Cannot create the distributed availability group '%.*ls' for the link because the database(s) '%.*ls' in the availability group '%.*ls' use a custom P…
- 47526 — Setting a custom persistent version store (PVS) filegroup is not supported for databases participating in Azure SQL Managed Instance link.
- 47527 — Cannot create distributed availability group '%.*ls' when local AG '%.*ls' is a contained availability group in cases when secondary participant is Az…
- 47600 — Reason: Windows Authentication for Azure AD Principals is not enabled on this instance.
- 47601 — Reason: There was an internal error while attempting Windows Authentication for Azure AD Principals.
- 47602 — When auto-rotation of TDE Protector is enabled, both primary and secondary servers must be connected to the same key vault. Add key '%ls' from the key…
- 47603 — All servers linked by GeoDr should have the same key material as the encryption protector of the primary server. Add the key '%ls' with the same key m…
- 47604 — Service principal is disabled.
- 47605 — Service principal has insufficient permissions.
- 47606 — Reason: There was an user error while attempting Windows Authentication for Azure AD Principals.
- 47607 — Reason: Login failure in mpdw
- 47608 — Reason: Login ack failure in mpdw
- 47609 — Conditional Access Policy is blocking usage of Service Principal.
- 47610 — Reason: An update SLO operation is in progress. The external connections are denied.
- 47611 — Reason: A Geo failover operation is in progress. The external connections are denied.
- 47612 — Reason: The database is in dropping state. The external connections are denied.
- 47613 — Reason: The login cannot obtain a LOCK resource at this time. This may be caused by insufficient resources or other queries holding locks on the syste…
- 47614 — Reason: The database failover caused the login failure.
- 47615 — Reason: The instance could not start up properly because it does not have access to critical resources and it does not allow user connections. Only ba…
- 47616 — Reason: The login cannot obtain a LOCK resource at this time because the database is being updated.
- 47617 — Reason: Mwc max user connection is reached.
- 47618 — Reason: Mwc max system connection is reached.
- 47619 — Reason: Validation of user's permissions failed. Verify the user has the Read item permission. For more information, see https://go.microsoft.com/fwli…
- 47620 — Reason: Authentication was successful, but the database was not found or you have insufficient permissions to connect to it.
- 47700 — Reason: The External Provider Access Token used for authenticating to the SQL Server is Blocklisted.
- 48001 — The operation could not be completed because the associated Network Security Perimeter denied inbound access from '{0}' to the '{1}' server. For more …
- 48002 — The operation could not be completed because the associated Network Security Perimeter denied outbound access from the '{0}' server to '{1}'. For more…
- 48003 — Unable to create the Network Security Perimeter association for server '{0}' because existing geo-replication relationships would become noncompliant.…
- 48004 — Unable to update the Network Security Perimeter association for server '{0}' to Enforced mode because existing geo-replication relationships would bec…
- 48005 — Unable to drop the Network Security Perimeter association for server '{0}' because geo-replication partner servers within the same Network Security Pe…
- 48006 — The operation could not be completed because not all Network Security Perimeter configurations between geo-replication partner servers are compliant. …
- 48007 — The managed identity URL '%ls' is not valid.
- 48008 — The read-only endpoint target server '{0}' must be in a different region than the primary server '{1}' of the failover group. Specify a read-only endp…
- 48009 — The dropped database '{0}' with last restorable point '{1}' cannot be found on the Managed Instance '{2}' within the supported recovery period. Verify…
- 48010 — The Managed Instance '{0}' deleted at '{1}' cannot be found in subscription '{2}' within the supported recovery period. Verify the Managed Instance na…
- 48011 — The dropped database '{0}' with last restorable point '{1}' cannot be found on the Managed Instance '{2}' deleted at '{3}' within the supported recove…
- 48012 — The requested managed instance update exceeds the limit of %d database files. Reduce the number of database files and try again.
- 49301 — One or more errors occurred during a native external table operation. The last error code was 0x%08x. See previous error messages (if any) for further…
- 49302 — One or more SQL Server host errors occurred during a native external table operation. The last error was %d. See previous error messages (if any) for …
- 49303 — Operation not implemented or not supported: '%s'. [0x%8x][%d] '%s'(), %s: %u.
- 49304 — File is invalid or corrupt: '%s'. [0x%08x][%d] '%s'(), %s: %u.
- 49305 — Internal failure: '%s'. [0x%08x][%d] '%s'(), %s: %u.
- 49306 — Internal SQL Server host failure: '%s' %s. [0x%08x][%d] '%s'(), %s: %u.
- 49307 — External Meson client operation failure: '%s'.
- 49308 — The object with name '%s' is not an external table.
- 49309 — Cannot find external table with id %d.
- 49310 — Cannot find column with id %d in object %d.
- 49311 — Column_id %d is already marked as partition column in object_id %d.
- 49312 — Column_id %d is already marked to be part of index_id %d in object_id %d.
- 49313 — Bad directory layout encountered when inferring partition information from path '%ls', starting at root '%ls'. Make sure your directories have column_…
- 49314 — The passed in location path must end with '' or '/'. Please fix the location path '%ls' for object_id %d.
- 49315 — Cannot parse '%ls', directory '%ls' is not part of object_id %d.
- 49401 — Database backup not supported on this database as it has foreign files attached.
- 49402 — Failed to initialize the covering resilient buffer pool extension for foreign file '%.*ls' with HRESULT 0x%x.
- 49403 — Database '%.*ls' does not allow autostart operations. An explicit ONLINE database operation is required.
- 49404 — Value '%.*ls' for option '%.*ls' is not supported in this version of SQL Server.
- 49405 — Skipping the default startup of vldb database '%.*ls'. The database will be started by the fabric. This is an informational message only. No user acti…
- 49406 — Recovery modes other than full are not supported in this version of SQL Server.
- 49407 — Error: %ls.
- 49408 — Error: %ls. Error code: %d.
- 49409 — Special procedure is not available on the current SQL instance.
- 49410 — Change tracking is currently not supported in this version of SQL Server.
- 49411 — Couldn't register the database in the page server database map.
- 49412 — Couldn't take snapshot due to XStore throttling for file "%ls".
- 49413 — Reporting transient fault for the database '%.*ls' because of an upgrade step on secondary compute.
- 49414 — Could not initialize %S_MSG configuration for database '%ls' (URI: '%ls'), Native error [%d].
- 49415 — Planned failover on database '%.*ls' would take too long due to replication lag between the geo-primary and geo-secondary. Please reduce workload and …
- 49416 — Grow file not supported in this version of SQL Server.
- 49417 — Hyperscale does not support database copy with elastic pools.
- 49418 — Fuzzing error: %ls
- 49419 — Striped file max size is not consistent with its range.
- 49420 — Page server manager initialization failed. Native error [%d].
- 49421 — Any ALTER operation on foreign file through pageserver is not supported.
- 49422 — Updating database '%.*ls' physical id failed. The usage is not impacted, please contact product group for manual mitigation.
- 49423 — There was a failure in the log service with physical database ID '%ls' while executing an operation. HRESULT '0x%x'. Reason: '%ls'.
- 49424 — Transformation of the log file to Hyperscale format failed.
- 49425 — Oldest begin LSN is smaller than foreign redo LSN which will prevent Page Server creation. Operation will be rolled back.
- 49426 — Grow of existing striped file failed.
- 49427 — Foreign File Validator encountered an exception: '%ls'. Logical DBID: '%ls', Physical DBID: '%ls'.
- 49428 — Could not access datafile during upgrade.
- 49429 — Invalid range passed from the caller. Start page id '%d', end page id '%d'.
- 49430 — Failed to take over ownership of single remote file. HRESULT 0x%x.
- 49501 — DBCC SHRINKFILE for %.*ls is aborted. Sbs flat files are not supported
- 49502 — %.*ls: Page %d:%d could not be moved because it is an sbs flat file page or the destination is an sbs flat file page.
- 49503 — %.*ls: Page %d:%d could not be moved because it is an off-row persistent version store page. Page holdup reason: %ls. Page holdup timestamp: %I64d.
- 49504 — Error updating failover proc.
- 49505 — Registering extended stored procedure failed because it is not valid to use UNC path for DLL name. Use local path for DLL name instead.
- 49506 — The DBCC operation failed because it is not supported in an explicit transaction when Accelerated Database Recovery is enabled on the database. Commit…
- 49507 — Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, row %d: Row is aborted.
- 49508 — DBCC SHRINKFILE for data files is not supported in this version of SQL Server.
- 49509 — DBCC SHRINKFILE for PMM files is not supported in this version of SQL Server.
- 49510 — Managed instance is busy with another operation. Please try your operation later.
- 49511 — Unable to set one or more trace flags. Unsupported trace flag(s): %ls%ls%ls.
- 49512 — Session level trace flags are not supported on managed instance.
- 49513 — %lsDBCC %ls for databese id %d terminated abnormally due to error state %d. Elapsed time: %d hours %d minutes %d seconds. %.*ls
- 49514 — %lsDBCC %ls for databese id %d found %d errors and repaired %d errors. Elapsed time: %d hours %d minutes %d seconds. %.*ls
- 49515 — Failed to execute AdhocXeventSession command for error: 0x%X, please check error log for details.
- 49516 — Shrink timeout waiting to acquire schema modify lock in WLP mode to process IAM pageID %d:%d on database ID %d
- 49517 — %lu is not a valid value for MAX_DURATION; MAX_DURATION must be equal to %lu.
- 49518 — %.*ls: Page %d:%d could not be moved because its marked for defer deallocation.
- 49519 — DBCC SHRINKDATABASE is not supported in this version of SQL Server. Contact Customer Support Services for more information.
- 49520 — Specifying the database_id parameter in DBCC SHRINKFILE is not supported in this version of SQL Server.
- 49521 — DBCC SHRINKFILE cannot shrink data files when used with database_id parameter.
- 49522 — DBCC operation on database id %d could not add new cache entries for Index Repair.
- 49523 — The operation failed because the Index Repair Manager is not available.
- 49524 — The operation failed because the Index Repair Feature is not supported for the object type %S_MSG (object ID %ld).
- 49525 — User '%.*ls' does not have permission to use the Index Repair Feature for object ID %ld.
- 49526 — An internal error occurred. Unable to get lock on the cache used by the Index Repair Manager.
- 49527 — The operation failed because the Index Repair Feature is not supported for temp tables.
- 49528 — The input row handle could not be decoded. Please use the sys.dm_db_logical_index_corruptions DMV to obtain the row handle.
- 49529 — Index repair failed. Please verify that the corruption exists using DBCC CHECK commands and use the sys.dm_db_logical_index_corruptions DMV to get the…
- 49530 — The requested repair finished successfully.
- 49531 — The operation failed because the internal repair command is invalid.
- 49532 — DBCC SHRINKFILE for data files is not supported in a Hyperscale database when the database is not encrypted or protector change is in progress. Enable…
- 49533 — DBCC SHRINKDATABASE is not supported in a Hyperscale database when the database is not encrypted or protector change is in progress. Enable transparen…
- 49534 — The input row handle is invalid for the given object ID and index ID. Please verify that the corruption exists using DBCC CHECK commands and use the o…
- 49535 — DBCC SHRINKFILE for fileId %d completed, initial size (%I64d KB), current size (%I64d KB). Please retry DBCC SHRINKFILE with target size well above mi…
- 49536 — Cleanup of Index Repair cache entries failed for database ID %d, object ID %d, index ID %d. No new entries will be added to the cache.
- 49537 — The shrink operation was aborted because a page to be moved by shrink is in use by an active transaction on the primary replica or on one or more seco…
- 49538 — The dynamic space management force reset operation was aborted because the connected server is not a page server.
- 49539 — The dynamic space management force reset operation has failed for database ID %d, mode ID %d, failure name %ls.
- 49540 — The specified DBCC command is not supported on this platform.
- 49541 — The command failed due to an internal error. Check the error log for more details.
- 49542 — DBCC SHRINKFILE and SHRINKDATABASE are not supported while the database is in Shared Data Cluster mode. The operation has been blocked. Try again afte…
- 49543 — Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The segment header chain of compressed blob data at page…
- 49600 — SQL tiered storage table schema is corrupt.
- 49601 — SBS Flat File Access not fully initialized, when function '%ls' was called.
- 49602 — Failure waiting for %ls latch in '%ls'.
- 49603 — CREATE FILE encountered operating system error %ls while attempting to copy the physical file '%.*ls'.
- 49701 — Server override on the category is not supported yet (Server: '%.*ls', Category: '%.*ls').
- 49702 — The category name is either invalid or not supported yet. Server: '%.*ls'. CategoryName: '%.*ls'.
- 49703 — Failed to parse server override on server '%.*ls'. The category name is: '%.*ls' and the override string is: '%.*ls'.
- 49704 — Failed to apply server override on category '%.*ls', because physical db or instance '%.*ls' in server '%.*ls' is currently not in 'Ready' or 'Deactiv…
- 49705 — Failed to merge server override into property bag on physical db or instance '%.*ls' of server '%.*ls'. The override string is: '%.*ls'.
- 49716 — Database override on the category is not supported yet (Server: '%.*ls', Database: '%.*ls', Category: '%.*ls').
- 49717 — Failed to apply database override on category '%.*ls', because physical db or instance '%.*ls' in server '%.*ls' is currently not in 'Ready' or 'Deact…
- 49718 — The category name is either invalid or not supported yet. Server: '%.*ls'. Database: '%.*ls'. CategoryName: '%.*ls'.
- 49801 — Dynamic Deactivation Timer task encountered an error (SQL Error Code: %d). Refer to the xel for more details.
- 49802 — Database is unavailable at the moment, please retry connection at later time.
- 49803 — Resource Pool Data Space Usage Timer task encountered an error (SQL Error Code: %d).
- 49804 — Database cannot be deactivated: Server '%.*ls', Database '%.*ls', ServiceLevelObjective '%.*ls'
- 49805 — DynamicActivation feature switch is off for Server '%.*ls', Database '%.*ls', ServiceLevelObjective '%.*ls'
- 49806 — DynamicActivation feature switch is not enabled for all remote storage DB: Server '%.*ls', Database '%.*ls', ServiceLevelObjective '%.*ls'
- 49807 — DynamicActivation is only supported for remote storage DB: Logical Server '%.*ls', Database '%.*ls', ServiceLevelObjective '%.*ls'
- 49808 — Deactivated database cannot be deactivated again: Server '%.*ls', Database '%.*ls'
- 49809 — Database Operation failed for Server '%.*ls', Database '%.*ls' due to unexpected delay. Please try again.
- 49810 — Workflow failed due to throttling: Server '%.*ls', Database '%.*ls'
- 49811 — Deactivation is not supported on Disabled database: Server '%.*ls', Database '%.*ls'
- 49812 — EnableForceNoBackupDeactivation is not enabled: Server '%.*ls', Database '%.*ls'
- 49813 — Deactivation is not supported on databases part of servers in global transaction partnership: Server '%.*ls', Database '%.*ls'
- 49814 — DynamicActivation is not supported for GeoDR DB: Logical Server '%.*ls', Database '%.*ls', ServiceLevelObjective '%.*ls'
- 49815 — Database cannot be deactivated: Server '%.*ls', Database '%.*ls', ServiceLevelObjective '%.*ls'
- 49816 — Server '%.*ls', Database '%.*ls' cannot be online as BlockingMode is set
- 49817 — Failed to query CMS for thottling on database '%.*ls', '%.*ls' due to the exception: '%.*ls'
- 49818 — Cannot deactivate a database when it is already getting deactivated, Server '%.*ls', Database '%.*ls'
- 49819 — Deflation Monitor Timer task encountered an error (SQL Error Code: %d). Refer to the xel for more details.
- 49820 — Managed Server Resource Stats Timer task encountered an error (SQL Error Code: %d).
- 49821 — Rg Metrics Reporting Timer task encountered an error (SQL Error Code: %d).
- 49822 — Move Cost Calculation and Reporting Timer task encountered an error (SQL Error Code: %d).
- 49823 — Database cannot be paused due to missing first full backup: Server '%.*ls', Database '%.*ls'.
- 49824 — (De)activation workflow for database '%.*ls' in server '%.*ls' failed because another (de)activation workflow is in progress. Please wait for the curr…
- 49825 — New connections to paused databases in this region for subscription '%ls' are temporarily disallowed due to too many concurrently resuming databases. …
- 49826 — Managed Server Resource Stats Timer task encountered an error while trying to update server_resource_stats (SQL Error Code: %d).
- 49901 — The number of max worker threads that is configured %u is less than the minimum allowed on this computer. The default number of %u will be used instea…
- 49902 — There are not enough worker threads available for the number of CPUs. This is because one or more CPUs were added. To increase the number of worker th…
- 49903 — Detected %I64d MB of RAM. This is an informational message; no user action is required.
- 49904 — The service account is '%.*ls'. This is an informational message; no user action is required.
- 49905 — Error %u occurred while opening parameters file '%s'. Verify that the file exists, and if it exists, verify that it is a valid parameters file.
- 49906 — Error %u occurred while processing parameters from either the registry or the command prompt. Verify your parameters.
- 49907 — Ignored deprecated SQL Server startup parameters from the registry: %.*ls
- 49908 — The following SQL Server startup parameters are either deprecated or incorrectly specified: %.*ls
- 49909 — Multiple instances of SQL server are installed on this computer. Renter the command, specifying the -s parameter with the name of the instance that yo…
- 49910 — Software Usage Metrics is disabled.
- 49911 — Software Usage Metrics failed to start.
- 49912 — Software Usage Metrics is enabled.
- 49913 — The server could not load DCOM. Software Usage Metrics cannot be started without DCOM.
- 49914 — %ls Trace: %ls
- 49915 — Invalid, incomplete, or deprecated parameters were found in the command line or in the registry. Normally those would be ignored but the '%s' paramete…
- 49916 — UTC adjustment: %d:%02u
- 49917 — Default collation: %ls (%ls %u)
- 49918 — Cannot process request. Not enough resources to process request. Please retry you request later.
- 49919 — Cannot process create or update request. Too many create or update operations in progress for subscription "%ld". Query sys.dm_operation_status for pe…
- 49920 — Cannot process request. Too many operations in progress for subscription "%ld". Query sys.dm_operation_status for pending operations and wait till the…
- 49921 — Total Log Writer threads: %ld. This is an informational message; no user action is required.
- 49922 — Unable to process '%s' notification for subscription '%ld' because it contains '%d' child resources
- 49923 — Managed Server '%s' is disabled. Please enable it and try again.
- 49924 — Subscription '%ld' does not support creating a database with selected service level objective '%ls'. Try creating a database with different service le…
- 49925 — Databases cannot be updated to free service level objective.
- 49926 — Server setup is starting
- 49927 — An error occurred while setting the server administrator (SA) password: error %d, severity %d, state %d.
- 49928 — An error occurred during server setup. See previous errors for more information.
- 49929 — Server setup completed successfully.
- 49930 — Parallel redo is %ls for database '%.*ls' with worker pool size [%d].
- 49931 — An error occurred while configuring engine telemetry: error %d, severity %d, state %d.
- 49932 — An error occurred while initializing security. %ls.
- 49933 — ERROR: The MSSQL_SA_PASSWORD environment variable must be set when using the --reset-sa-password option.
- 49934 — Error %u occurred while reading the RbIo configuration parameters. Verify that the sqlservr.ini or registry entries exist.
- 49935 — Enclave of type %d initialized successfully.
- 49936 — ERROR: The provided PID [%s] is invalid. The PID must be in the form #####-#####-#####-#####-##### where '#' is a number or letter.
- 49937 — ERROR: A failure occurred in the licensing subsystem. Error [%d].
- 49938 — The licensing PID was successfully processed. The new edition is [%s].
- 49939 — Unable to initialize user-specified certificate configuration. The server is being shut down. Verify that the certificate is correctly configured. Err…
- 49940 — Unable to open one or more of the user-specified certificate file(s). Verify that the certificate file(s) exist with read permissions for the user and…
- 49941 — Unable to load one or more of the user-specified certificate file(s). Verify that the certificate file(s) are of a supported format.
- 49942 — Internal error occurred initializing user-specified certificate configuration. Error code [%08X].
- 49943 — The certificate [Certificate File:'%hs', Private Key File:'%hs'] was successfully loaded for encryption.
- 49944 — The allowed TLS protocol version list ['%hs'] is invalid. Verify that the supplied TLS version numbers are supported by SQL Server and separated by sp…
- 49945 — The allowed TLS cipher list ['%hs'] is invalid. See docs.microsoft.com for more information on creating a cipher list.
- 49946 — Internal error occurred initializing the TLS configuration. Error code [%d].
- 49947 — Unable to initialize the TLS configuration. The server is being shut down. Verify that the allowed TLS protocol and cipher lists are configured correc…
- 49948 — Successfully initialized the TLS configuration. Allowed TLS protocol versions are ['%hs']. Allowed TLS ciphers are ['%hs'].
- 49949 — ERROR: Unable to set system administrator password: %s.
- 49950 — The SQL Server End-User License Agreement (EULA) must be accepted before SQL
- 49951 — Server can start. The license terms for this product can be downloaded from
- 49952 — http://go.microsoft.com/fwlink/?LinkId=746388 .
- 49953 — You can accept the EULA by specifying the --accept-eula command line option,
- 49954 — setting the ACCEPT_EULA environment variable, or using the mssql-conf tool.
- 49955 — Environment Variable Startup Parameters:%.*ls
- 49956 — The default language (LCID %d) has been set for engine and full-text services.
- 49957 — The default language (LCID %d) failed to be set for engine and full-text services.
- 49958 — The server collation cannot be changed with user databases attached. Please detach user databases before changing server collation.
- 49959 — ERROR: The environment variable MSSQL_COLLATION contains an invalid collation '%.*ls'.
- 49960 — Did not find an existing master data file %s, copying the missing default master and other system database files. If you have moved the database locat…
- 49961 — Setup step is %scopying system data file '%s' to '%s'.
- 49962 — ERROR: Setup FAILED copying system data file '%s' to '%s': %s
- 49963 — ERROR: '%s' is a directory. Cannot continue.
- 49964 — ERROR: Setup failed to create the system data directory '%s': %s
- 49965 — Unable to load cluster root CA certificate due to OSError:'%s'.
- 49966 — Unable to install the AAD Cert. Verify that '%s' exists and is in the correct PFX format. Error state [%d].
- 49967 — Unable to install the AAD Cert. Cannot load cert path from registry. Error state [%d].
- 49968 — SQL Server shutdown has been initiated with exit code %d.
- 49969 — Could not perform the operation because the region is under high capacity pressure. Please wait for %d hours before retrying the operation.
- 49972 — Cannot add tempdb remote file to local tempdb filegroup in transition to primary.
- 49973 — Cannot remove tempdb remote file to local tempdb filegroup in transition to primary.
- 49974 — CREATE DATABASE statement is not supported in a Synapse workspace. To create a SQL pool, use the Azure Synapse Portal or the Synapse REST API.
- 49975 — Unable to load controller client certificate due to OSError:'%s'.
- 49976 — Cannot process create or update request. Too many create or update operations in progress for subscription '%ls'.
- 49977 — The elastic pool '%ls' is busy with another operation. Please wait until the ongoing operation finishes and try again.
- 49978 — ALTER DATABASE NAME statement is not supported in a Synapse workspace. To update the name of a SQL pool, use the Azure Synapse Portal or the Synapse R…
- 49979 — DROP DATABASE statement is not supported in a Synapse workspace. To delete a SQL pool, use the Azure Synapse Portal or the Synapse REST API.
- 49980 — https://go.microsoft.com/fwlink/?linkid=2139274 .
- 49981 — Server '%ls' requires permissions: '%ls' on Azure Key Vault for key '%ls'. Please grant the server both access and required permissions to key vault a…
- 49982 — Choose a different name for this workspace resource. A '%ls' with the name '%ls' already exists.
- 49983 — The '%ls' operation failed to complete. Retry the operation. Create a support request if the retry attempts do not succeed.
- 49984 — Select a different name for this server. A server with the name '%ls' already exists.
- 49985 — The data exfiltration upsert operation is already in progress.
- 49986 — Failed to perform data exfiltration operation.
- 49987 — The logical server extension '%ls' not found.
- 49988 — Before creating a resource. Grant the workspace Managed Identity required permissions in the Azure Key Vault of the workspace. Then activate your work…
- 49989 — Database is logically paused. Wait for physicalPauseDelay to expire to issue Physical pause (deactivation) of DB.
- 49990 — Choose a different name for this '%ls' resource. Deletion of a '%ls' with the name '%ls' is currently in progress. The selected name can be used when …
- 49991 — The requested service level objective for this pool exceeds the current limit. To increase the limit, please create support ticket.
- 49992 — The count of pools in this workspace exceeds the current limit. To increase the limit, please create support ticket.
- 49993 — The count of pools in this subscription exceeds the current limit. To increase the limit, please create support ticket.
- 49994 — The combined usage of pools on the workspace exceeds the current limit. To increase the limit, please create support ticket.
- 49995 — The combined usage of pools in this subscription exceeds the current limit. To increase the limit, please create support ticket.
- 49996 — The databases count on the workspace exceeds the current limit. To increase the limit, please create support ticket.
- 49997 — The databases count in this subscription exceeds the current limit. To increase the limit, please create support ticket.
- 49998 — Restore/GeoRestore very large database is blocked in this region. To enable it, please create support ticket.
- 49999 — Could not perform the operation because the subscription would exceed the allowed vCore quota of %d.