#40860 medium
Errors

Description 40860 16 No Elastic pool '%ls' and service level objective '%ls' combination is invalid.

#connection#severity-medium
#40880 medium
Errors

Description allowed values for service tier '%.*ls'. 40880 16 No The DTUs (%d) for the elastic pool and the storage limit in gigabytes (%d) are inconsistent for service tier '%.*ls'. 40881 16 No The e

#io#severity-medium
#40898 medium
Errors

Description 40898 16 No The elastic pool storage limit in megabytes (%d) does not belong to the allowed values for service tier '%.*ls'. 40899 16 No The DTUs (%d) for the elastic pool and the storage

#io#severity-medium
#40915 medium
Errors

Description 40915 16 No Secondary server for a Failover Group cannot reside in the same region as primary server. Please provide a name of server that is in different Azure region than primary server.

#io#severity-medium
#40931 medium
Errors

Description 40931 16 No Failover Group name '%.*ls' cannot be empty or null. It can only be made up of lowercase letters 'a'-'z', the numbers 0-9 and the hyphen.

#io#severity-medium
#40946 medium
Errors

Description 40946 16 No The Table Auditing or Security Enabled Access feature cannot be turned on for a database that is part of a Failover Group. 40947 16 No The Table Auditing or Security Enabled Ac

#io#severity-medium
#40962 medium
Errors

Description 40962 16 No The VCore min per database must be at least (%d) for service tier '%.*ls'.

#io#severity-medium
#40980 medium
Errors

Description 40980 16 No Partner managed server's managed server/failover group has been dropped. 40981 16 No Database '%.*ls' is not accessible due to Azure Key Vault critical error. 40982 16 No Insta

#io#severity-medium
#40997 medium
Errors

Description 40997 16 No Elastic pool '%ls' does not exist in server '%ls'. Please make sure that the elastic pool name is entered correctly. Please contact Microsoft support if further assistance is n

#io#severity-medium
#41006 medium
Errors

'Description information about this error code, see "System Error Codes" in the Windows Development documentation. 41006 16 No Failed to create the Windows Server Failover Clustering (WSFC) group with '

#io#severity-medium
#41013 medium
Errors

Description not be running or may not be accessible in its current state, or the specified arguments are invalid. Otherwise, contact your primary support provider.

#io#severity-medium
#41019 medium
Errors

'Description your primary support provider. For information about this error code, see "System Error Codes" in the Windows Development documentation. 41019 16 No Failed to drop a Windows Server Failove'

#io#severity-medium
#41025 medium
Errors

Description 41025 16 No Failed to receive Windows Server Failover Clustering (WSFC) change notifications (Error code %d). If this is a WSFC availability group, the WSFC service may not be running or m

#io#severity-medium
#41032 medium
Errors

Description 41032 16 No Failed to delete the Windows Server Failover Clustering (WSFC) registry subkey '%.*ls' (Error code %d). The parent key is %sthe cluster root key. If this is a WSFC availability

#io#severity-medium
#41038 medium
Errors

Description 41038 16 No Failed to enumerate Windows Server Failover Clustering (WSFC) objects (Error code %d). If this is a WSFC availability group, the WSFC service may not be running or may not be a

#io#severity-medium
#41047 medium
Errors

Description 41047 16 No Failed to obtain the Windows Server Failover Clustering (WSFC) node state for the local WSFC node (Error code %d).

#io#severity-medium
#41057 medium
Errors

Description 41057 16 No Failed to create the Windows Server Failover Clustering (WSFC) resource with name '%ls'. The WSFC resource with the specified name already exists.

#io#severity-medium
#41066 medium
Errors

Description 41066 16 No Cannot bring the Windows Server Failover Clustering (WSFC) resource (ID '%.*ls') online (Error code %d).

#io#severity-medium
#41073 medium
Errors

Description 41073 16 No The database '%.*ls' cannot be removed from availability group '%.*ls'. This database does not belong to the availability group. 41074 10 No Always On Availability Group: The l

#io#severity-medium
#41083 medium
Errors

'Description your primary support provider. For information about this error code, see "System Error Codes" in the Windows Development documentation. 41083 16 No Failed to obtain the cluster quorum res'

#io#severity-medium
#41091 medium
Errors

Description 41091 10 No Always On Availability Groups: The local replica of availability group '%.*ls' is going offline because either the lease expired or lease renewal failed. This is an information

#io#severity-medium
#41100 medium
Errors

Description 41100 16 No The availability group '%.*ls' and/or its local availability replica does not exist. Verify that the specified availability group name is correct, and that the local availabili

#io#severity-medium
#41108 medium
Errors

Description 41108 16 No An error occurred while removing availability group '%.*ls'. The DROP AVAILABILITY GROUP command removed the availability group configuration from the local metadata. However,

#connection#severity-medium
#41118 medium
Errors

Description 41118 16 No Cannot map database ID %d to the availability database ID '%.*ls' within availability group '%.*ls'. Another local database, (ID %d).

#io#severity-medium
#41128 medium
Errors

Description 41128 16 No Failed to perform database operation '%s' on database '%.*ls' (ID %d) in availability group '%.*ls'. The database might be in an incorrect state for the operation.

#io#severity-medium
#41137 medium
Errors

Description 41137 10 No Abandoning a database operation '%ls' on availability database '%.*ls' of availability group '%.*ls'.

#io#severity-medium
#41146 medium
Errors

Description user action is required. 41146 16 No Failed to bring Availability Group '%.*ls' online.

#connection#severity-medium
#41156 medium
Errors

Description group name is correct. The availability group may need to be recreated if the drop operation was unintentional. 41156 16 No Cannot drop availability group '%.*ls' from this instance of SQL

#corruption#severity-medium
#41164 medium
Errors

Description availability group is in the correct state for the command. If this is a Windows Server Failover Clustering (WSFC) availability group, also verify that the WSFC cluster is in the correct s

#io#severity-medium
#41172 medium
Errors

Description either remove or rename the existing WSFC group, or retry the operation specifying a different availability group name. 41172 16 No An error occurred while dropping availability group '%.*

#io#severity-medium
#41182 medium
Errors

Description availability group state in Windows Server Failover Cluster is correct, then retry the operation.

#io#severity-medium
#41189 medium
Errors

Description 41189 16 No Availability group '%.*ls' failed to process the %s-%s command. The availability group configuration has been updated.

#io#severity-medium
#41196 medium
Errors

Description 41196 16 No Failed to create availability group '%.*ls', because a Windows Server Failover Cluster (WSFC) group with the specified name already exists. An attempt to roll back the operatio

#io#severity-medium
#41208 medium
Errors

Description that the corresponding language statistics has been installed. 41208 10 No Warning: The population for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d') encount

#io#severity-medium
#41306 medium
Errors

Description 41306 16 No The nesting limit of %d for conditional blocks and exception blocks, for natively compiled modules, has been exceeded. Please simplify the module.

#io#severity-medium
#41324 medium
Errors

Description used in a natively compiled module. 41324 16 No The memory optimized table variable '%.*ls' cannot be used in a batch with a 'USE' statement.

#io#severity-medium
#41340 medium
Errors

Description transaction. The transaction was aborted. Please retry the transaction. 41340 16 No The transaction executed too many insert, update, or delete statements in memory optimized tables. The t

#io#severity-medium
#41356 medium
Errors

Description terminated. 41356 16 No Filegroups with MEMORY_OPTIMIZED_DATA can only be created in 64-bit installations of SQL Server.

#io#severity-medium
#41370 medium
Errors

Description 41370 16 No Resource pool '%.*ls' does not exist or resource governor has not been reconfigured. 41371 16 No Binding to a resource pool is not supported for system database '%.*ls'. This o

#io#severity-medium
#41384 medium
Errors

Description 41384 16 No Database '%.*ls' has exceeded the maximum number of XTP checkpoint files, and can no longer support write operations in durable memory- optimized tables. For more information,

#io#severity-medium
#41399 medium
Errors

Description 41399 16 No The sort operation is too complex. Consult SQL Server Books Online for more information. Database Engine events and errors Understanding Database Engine errors Cause and resolu

#io#severity-medium
#41401 medium
Errors

Description 41401 16 No WSFC cluster service is offline. 41402 16 No The WSFC cluster is offline, and this availability group is not available. This issue can be caused by a cluster service issue or b

#io#severity-medium
#41417 medium
Errors

Description 41417 16 No Availability replica is disconnected. 41418 16 No This secondary replica is not connected to the primary replica. The connected state is DISCONNECTED. 41419 16 No Data synchron

#io#severity-medium
#41501 medium
Errors

Description 41501 16 No Failed to register client (ID %ls) with asynchronous operations administrator. A client with this ID has already been registered. Check that the specified client ID is correct,

#io#severity-medium
#41606 medium
Errors

Description with a Windows Fabric partition (ID %ls). If this condition persists, contact the system administrator. 41606 16 No Replica (Windows Fabric replica ID 0x%08X, current state '%ls') cannot p

#io#severity-medium
#41616 medium
Errors

Description 41616 16 No SQL Server cannot find the configuration of the replica with ID %ls (Windows Fabric partition ID %ls).

#io#severity-medium
#41627 medium
Errors

Description 41627 10 No An error has occurred while Dropping %ls database (SQL Error Code: %d). Refer to the SQL error code for more details. If this condition persists, contact the system administrat

#io#severity-medium
#41638 medium
Errors

Description 41638 16 No Could not retrieve remote replica storage configuration for database '%ls' (URI: '%ls'). 41639 16 No Could not retrieve remote replica configuration for database '%ls' (URI: '%

#io#severity-medium
#41654 medium
Errors

Description information about the errors that were encountered. If this condition persists, contact the system administrator.

#io#severity-medium
#41669 medium
Errors

Description 41669 16 No Database '%ls' (ID %d) of Windows Fabric partition '%ls' (partition ID '%ls') hit exception while running async tasks in RbIo Subscriber.

#connection#severity-medium
#41700 medium
Errors

Description 41700 16 No System views related to Windows Fabric partitions and replicas are not available at this time, because replica manager has not yet started. Wait for replica manager to start, t

#io#severity-medium
#41809 medium
Errors

Description 41809 16 No Natively compiled triggers do not support statements that output a result set.

#io#severity-medium
#41825 medium
Errors

Description 41825 16 No Stored procedure '%.*ls' cannot be used to increase the user memory limit on the database.

#io#severity-medium
#41855 medium
Errors

Description the Storage Interface. 41855 16 No Memory optimized file consistency error detected. Could not find a file with FileId %.*ls in the File Watermark Table visible by checkpoint ID %u. 41856

#io#severity-medium
#41874 medium
Errors

Description 41874 10 No There are %d orphaned internal table(s) eligible for removal. Investigate the error log for the table identifiers. CHECKPOINT the database, create a full database backup, and r

#connection#severity-medium
#41909 medium
Errors

Description 41909 16 No Modifying logical file name is not supported in SQL Database Managed Instance. 41910 16 No Add/remove/modify of log files is not supported in SQL Database Managed Instance. 419

#io#severity-medium
#41925 medium
Errors

Description 41925 16 No If DB has multiple data files, all files need to have max size larger than %d MB in this edition of Managed Instance. File id: %ld. Size: %I64d bytes.

#io#severity-medium
#41942 medium
Errors

Description 41942 16 No Renaming local instance is not allowed in SQL Database Managed Instance.

#io#severity-medium
#41956 medium
Errors

Description issue persists, contact Microsoft Support for Azure SQL Managed Instance. 41956 21 No Transient error occurred while trying to retrieve backup URIs property for database '%.*ls'.

#io#severity-medium
#41967 medium
Errors

Description 41967 16 No The '%.*ls' operation cannot be completed as incorrect value was specified for '%.*ls' server configuration option. 41968 16 No Changing the server role cannot be executed at t

#connection#severity-medium
#41980 medium
Errors

Description Either unencrypt the database on Managed Instance, or switch the encryption service protector to customer-managed (BYOK) and try again. 41980 16 No Database cannot be encrypted using the s

#connection#severity-medium
#41992 medium
Errors

Description the database was in the inaccessible state. Please restore the original database role by executing geo-failover and try again. 41992 16 No Unable to make database %s on SQL Managed Instanc

#connection#severity-medium
#42020 medium
Errors

Description 42020 16 No Updating name to '%.*ls' failed. 42021 16 No Initialization of http session handle for fetching federation metadata failed during AzureActiveDirectory initialization. 42022 16

#io#severity-medium
#42201 medium
Errors

Description 42201 16 No The requested distance metric '%ls' is not supported by vector_distance. Please provide a valid distance metric.

#io#severity-medium
#42219 medium
Errors

Description 42219 16 No Failed to create internal table %d for the vector index. 42220 16 No Cannot create the vector index on temp objects. '%.*ls' is identified as a temp object. 42221 16 No DROP VE

#io#severity-medium
#42239 medium
Errors

Description 42239 10 No Vector index background cleaner cleaned the inbuild vector index ID %d on object ID %d in database ID %d. 42240 16 No Vector data type is not supported in merge replication. 42

#io#severity-medium
#43005 medium
Errors

Description 43005 16 No '%.*ls' is not a valid database name because it contains invalid characters. 43006 16 No Database name '%.*ls' is too long. 43007 16 No '%.*ls' is not a valid database charset.

#io#severity-medium
#43026 medium
Errors

Description 43026 16 No Cannot drop system database '%.*ls', skipping. 43027 16 No Geo Restore is not supported. 43028 16 No The replication feature is not supported.

#io#severity-medium
#43202 medium
Errors

Description 43202 16 No The value %I64d is invalid for %.*ls. Value must be greater than %d. 43203 16 No The specified %.*ls '%.*ls' is not supported. 43204 16 No An unexpected error has occurred. 450

#io#severity-medium
#44695 medium
Errors

Look up part or all of the assert expression online for any known issues. For example, if you search for , you might find KB4469554 - FIX: Assertion error occurs during restore of compressed backups i

#io#severity-medium
#45024 medium
Errors

Description 45024 16 No ALTER FEDERATION SPLIT operation failed. Specified boundary value already exists for federation distribution %.*ls and federation %.*ls. 45025 16 No %ls operation failed. Speci

#connection#severity-medium
#45042 medium
Errors

Description 45042 16 No Federation root database options cannot be changed. 45043 16 No ALTER FEDERATION SWITCH %ls is not supported on %ls members. 45044 16 No ALTER FEDERATION SWITCH IN failed. %.*l

#io#severity-medium
#45119 medium
Errors

Description 45119 16 No Property selections contain conflicting values. 45120 16 No The name '%ls' already exists. Choose a different name. 45121 16 No Target server '%ls' does not support memory-opti

#connection#severity-medium
#45140 medium
Errors

Description 45140 16 No Maximum lag does not support the specified value. Maximum lag must be between '%ls' and '%ls'. 45141 16 No Database copies can only be initiated on the source server. 45142 16

#io#severity-medium
#45158 medium
Errors

Description 45158 16 No Cannot move server '%.*ls' from source subscription '%ls' to target subscription '%ls'. You can have only one free database per subscription.

#connection#severity-medium
#45176 medium
Errors

Description progress. 45176 16 No Unable to queue server %ls for migration. The server is using feature %ls that prevents it from being migrated. 45177 16 No Unable to queue server %ls for migration.

#io#severity-medium
#45210 medium
Errors

Description specify a valid email to enable notifications for Smart Admin. 45210 16 No Database Mail is not enabled for SQL Agent to use for Notifications.

#io#severity-medium
#45306 medium
Errors

Description 45306 16 No The external admin cannot be set because the principal name '%ls' already exists in the 'master' database. 45307 16 No Advisor '%.*ls' was not found for requested resource 4530

#io#severity-medium
#45323 medium
Errors

Description 45323 16 No Unable to start a copy because the source database '%ls' is being updated. 45324 16 No The operation could not be completed because the Azure Key Vault Uri is null or empty. 45

#io#severity-medium
#45337 medium
Errors

Description 45337 16 No The planned failover operation has rolled back because database '%ls' could not be synchronized with its remote partner.

#io#severity-medium
#45365 medium
Errors

Description customer support. 45365 16 No vCore value (%d) is not valid. Please specify a valid vCore value. 45366 16 No The retention days of %d is not a valid configuration. Valid backup retention i

#io#severity-medium
#45416 medium
Errors

Description Vault (BYOK). 45416 16 No Cannot create a Managed Instance with collation '%.*ls'. Please use collation 'SQL_Latin1_General_CP1_CI_AS' instead. 45417 16 No Vulnerability Assessment storage

#io#severity-medium
#45429 medium
Errors

Description are no existing managed instances, or if deploying to a subnet with existing managed instance disable the geo-replication option.

#connection#severity-medium
#45444 medium
Errors

Description 45444 16 No Provisioning of Zone Redundant server is not supported . 45445 16 No Storage Auto Grow is not supported for Primary and Replica Servers.

#io#severity-medium
#45463 medium
Errors

Description 45463 16 No The server %ls no longer has access to the Azure Key Vault required for the current TDE configuration. In order to change the encryption setting for the server you must first r

#io#severity-medium
#45475 medium
Errors

Description 45475 16 No A Microsoft Entra ID login '%s' cannot be added because a non Microsoft Entra ID login exists with the same name.

#io#severity-medium
#45491 medium
Errors

Description 45491 16 No Vulnerability Assessment Baseline file exceeds the size limit (10MB). 45492 16 No Vulnerability Assessment baseline file isn't in the right format.

#io#severity-medium
#45511 medium
Errors

Description 45511 16 No The restored database is too large for '%s' edition. Select a target edition with sufficient storage for the allocated database size. After restore, perform a shrink database o

#io#severity-medium
#45523 medium
Errors

Description 45523 16 No One or more identity id(s) provided are not valid ARM resource id(s). Please provide valid id(s) and try again. For more information, see https://go.microsoft.com/fwlink/?linki

#io#severity-medium
#45536 medium
Errors

Description Network '%ls'. 45536 16 No Provided subnet is having different DNS zone from the current. Changing instance DNS zone is not supported.

#io#severity-medium
#45547 medium
Errors

Description 45547 16 No The create operation has timed out in one of the backend workflows. Please retry the operation.

#io#severity-medium
#45564 medium
Errors

Description 45564 16 No It is not possible to stop the instance with zone redundancy enabled. Refer to the following article for limits of managed instance start/stop feature: https://go.microsoft.com

#io#severity-medium
#45578 medium
Errors

Description then try again. 45578 16 No The backup redundancy request cannot start because the update is already in progress. 45579 16 No Failed to update the backup storage. Contact Microsoft Support

#io#severity-medium
#45602 medium
Errors

Description 45602 16 No Database recovery requests are invalid when issued against a database that is not configured to use geo-redundant backup storage.

#io#severity-medium
#45622 medium
Errors

Description be specified between %ls MBps and %ls MBps, in increments of %ls MBps. 45622 16 No Geo-redundant backup storage is not permitted for databases under subscription '%s'. 45623 16 No Managed

#io#severity-medium
#45638 medium
Errors

Description 45638 16 No Enabling long-term backup retention for a database during a reverse migration from Hyperscale is not supported.

#io#severity-medium
#45656 medium
Errors

Description 45656 16 No The operation could not be completed because the Azure Key Vault Key name '%ls' is currently set as encryption protector on geo-primary. 45657 16 No DTC for Azure SQL Managed I

#io#severity-medium
#45672 medium
Errors

Description remote storage cannot be enabled due to a conflict with an existing route. Check the route table for the subnet hosting the instance to identify and solve the conflict. 45672 16 No Cross s

#io#severity-medium
#45685 medium
Errors

Description 45685 16 No Could not perform the operation due to capacity group resource constraint based on the requested service level objective and storage size. Plus try again in 24 hours. 45686 16

#io#severity-medium
#45698 medium
Errors

'Description to complete, or try again with a different database that is in ''Restoring'' state. 45698 16 No Cannot create a database with special characters in its name. Special Characters include u003'

#io#severity-medium