错误码目录 / Microsoft SQL Server
Microsoft SQL Server 错误码目录 · 第 17 / 18 页
本页收录 Microsoft SQL Server 的 17,993 条错误码知识条目,每条均可打开独立详情页,包含错误说明、编号信息、官方文档与公开资料。
- 41412 — In this availability group, at least one availability replica does not currently have the primary or secondary role.
- 41413 — Some availability replicas are disconnected.
- 41414 — In this availability group, at least one secondary replica is not connected to the primary replica. The connected state is DISCONNECTED.
- 41415 — Availability replica does not have a healthy role.
- 41416 — The role of this availability replica is unhealthy. The replica does not have either the primary or secondary role.
- 41417 — Availability replica is disconnected.
- 41418 — This secondary replica is not connected to the primary replica. The connected state is DISCONNECTED.
- 41419 — Data synchronization state of some availability database is not healthy.
- 41420 — At least one availability database on this availability replica has an unhealthy data synchronization state. If this is an asynchronous-commit availab…
- 41421 — Availability database is suspended.
- 41422 — Either a database administrator or the system has suspended data synchronization on this availability database.
- 41423 — Secondary database is not joined.
- 41424 — This secondary database is not joined to the availability group. The configuration of this secondary database is incomplete. For information about how…
- 41425 — Data synchronization state of availability database is not healthy.
- 41426 — The data synchronization state of this availability database is unhealthy. On an asynchronous-commit availability replica, every availability database…
- 41427 — Availability replica is not joined.
- 41428 — This secondary replica is not joined to the availability group. For an availability replica to be successfully joined to the availability group, the j…
- 41429 — Adding another database to an existing Azure SQL Managed Instance link is not supported, as a single link can contain only one user database. Create a…
- 41500 — An error (0x%08x) occurred when asynchronous operations administrator attempted to notify the client (ID %ls) of the completion of an operation. This …
- 41501 — Failed to register client (ID %ls) with asynchronous operations administrator. A client with this ID has already been registered. Check that the speci…
- 41502 — Failed to deregister client (ID %ls) from asynchronous operations administrator. The client has not registered with the administrator. Check that the …
- 41503 — Client (ID %ls) failed to submit work to asynchronous operations administrator. The client has not registered with the administrator. Check that the s…
- 41504 — Asynchronous operations administrator failed to allocate a work item for the work submitted by client (ID %ls). The administrator may have exhausted a…
- 41505 — Asynchronous operations administrator failed to queue a work item for the work submitted by client (ID %ls) (internal error %d). The administrator may…
- 41600 — An error has occurred while executing an asynchronous operation for a database replica (Windows Fabric partition ID %ls, operation %d, error 0x%08x). …
- 41601 — Valid state transition is not found for local replica with partition ID %ls (current state %ls, trigger %ls, current epoch [%I64d,%I64d], triggering e…
- 41602 — An error has occurred while attempting to access replica publisher's subscriber list (partition ID %ls, SQL OS error code 0x%08x). Refer to the error …
- 41603 — The transport subscriber failed to process the build secondary replica event (partition ID %ls). If this condition persists, contact the system admini…
- 41604 — The transport subscriber failed to process the configuration change replica event (partition ID %ls). If this condition persists, contact the system a…
- 41605 — Cannot associate replica (Windows Fabric replica ID 0x%08X) with the specified Windows Fabric partition (ID %ls). The replica is already associated wi…
- 41606 — Replica (Windows Fabric replica ID 0x%08X, current state '%ls') cannot process configuration-update command for Windows Fabric partition (ID %ls). Con…
- 41607 — Operation timed out while waiting for %ls access to the cached information in the replica controller (Windows Fabric replica ID 0x%08X, partition ID %…
- 41608 — Failed to obtain %ls access to the cached information in the replica controller (Windows Fabric replica ID 0x%08X, partition ID %ls, SQL OS error %d).…
- 41609 — Operation timed out while waiting for %ls access to the list of replica controller objects. If this condition persists, contact the system administrat…
- 41610 — Failed to obtain %ls access to the list of replica controller objects (SQL OS error %d). The operation may have been aborted. Refer to the SQL OS erro…
- 41611 — Replica controller for the local replica (Availability Group ID %ls) cannot be found. Make sure the specified Availability Group ID is correct, then r…
- 41612 — An error has occurred while %ls %ls database (SQL Error Code: %d). Refer to the SQL error code for more details. If this condition persists, contact t…
- 41613 — Fabric Service '%ls' failed to perform database operation '%ls' on '%ls' database (ID %d). The database might be in an incorrect state for the operati…
- 41614 — Fabric Service '%ls' encountered a transient error while performing Windows Fabric operation on '%ls' database (ID %d). Refer to the SQL Server error …
- 41615 — Fabric Service '%ls' encountered a permanent error while performing a Windows Fabric operation on '%ls' database (ID %d). Refer to the SQL Server erro…
- 41616 — SQL Server cannot find the configuration of the replica with ID %ls (Windows Fabric partition ID %ls). Make sure the specified Windows Fabric partitio…
- 41617 — Fabric Service '%ls' is unable to find out start of log and end of log LSN for '%ls' database. Refer to the SQL Server error log for information about…
- 41618 — Attempt to access non-existent or uninitialized Windows Fabric partition '%ls'. This is usually an internal condition, such as the Windows Fabric serv…
- 41619 — Windows Fabric '%ls' (partition ID '%ls')encountered transient error %d while waiting for build replica operation on database '%ls' (ID %d). Refer to …
- 41620 — Build replica operation on database '%ls' (ID %d) of Windows Fabric partition '%ls' (partition ID '%ls') has been cancelled by Windows Fabric. Windows…
- 41621 — Windows Fabric partition '%ls' (partition ID '%ls') encountered error '%ls' and is reporting '%ls' failure to Windows Fabric. Refer to the SQL Server …
- 41622 — Windows Fabric service '%ls' (partition ID '%ls') is trying to update primary replica information for local replica %ls which is neither ACTIVE_SECOND…
- 41623 — The Database Mirroring endpoint port is unavailable. Verify that the DBM endpoint is created.
- 41624 — Drop database '%ls' (ID %d) of Windows Fabric partition '%ls' (partition ID '%ls') has failed. SQL Server has failed to drop the database. If this con…
- 41625 — The internal buffer for the replication URL is insufficient.
- 41626 — Failed to retrieve service desription from Windows Fabric for partition '%ls' (Windows Fabric error 0x%08x). If this condition persists, contact the s…
- 41627 — 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, cont…
- 41628 — Drop database Timer task encountered an error (SQL Error Code: %d). Refer to the SQL error code for more details. If this condition persists, contact …
- 41629 — Fabric replica publisher encountered an error (SQL Error Code: %d, State: %d) while publishing event '%ls' to subscriber of type '%ls' on Fabric parti…
- 41630 — Failed to update primary replica information for partition '%ls' (Windows Fabric error 0x%08x). This is an informational message only. No user action …
- 41631 — Fabric service '%ls' failed to retrieve a known hardware sku while performing a build replica operation on '%ls' database (ID %d). Refer to the cluste…
- 41632 — The system encountered SQL Error %d (severity: %d, state: %d), which has no corresponding error text. Refer to the SQL Error number for more informati…
- 41633 — Fabric Service '%ls' (partition ID '%ls') is unable to allocate a work item for the database restart of '%ls' database (ID %d). The administrator may …
- 41634 — Open replica operation on database '%ls' (ID %d) of Windows Fabric partition ID '%ls' has been cancelled. This is an informational message only. No us…
- 41635 — Open replica operation on database '%ls' (ID %d) of Windows Fabric partition ID '%ls' failed. For more information, see the SQL Server error log. This…
- 41636 — Fabric Service '%ls' (partition ID '%ls') is unable to enqueue a work item for the database restart of '%ls' database (ID %d). The administrator may h…
- 41637 — The database '%ls' (URI: '%ls', partition ID '%ls') is not currently participating in a GeoDR relationship.
- 41638 — Could not retrieve remote replica storage configuration for database '%ls' (URI: '%ls').
- 41639 — Could not retrieve remote replica configuration for database '%ls' (URI: '%ls').
- 41640 — Database '%ls' encountered a transient error (error code: 0x%08X) while performing task '%ls'. Refer to the SQL Server error log for information about…
- 41641 — Could not send global cluster action '%ls' request 0x%x.
- 41642 — Undo of redo is run in Active Secondary role on database '%ls' (ID %d). Recovery lsn: '%S_LSN', Hardened lsn: '%S_LSN'. If this condition persists, co…
- 41643 — Could not retrieve the Layered AG Configuration for database '%ls' (URI: '%ls', partition ID '%ls') . Encountered error (error code: 0x%08X).
- 41644 — Fabric Service '%ls' failed to perform database operation '%ls' on database '%ls'. The database might be in an incorrect state for the operation. If t…
- 41645 — Fabric Service '%ls' (partition ID '%ls') encountered error (error code: 0x%08X) while querying for Fabric property '%ls'.
- 41646 — Invalid Fabric property '%ls' received for partition '%ls'.
- 41647 — Failed to start the report fault thread during replica manager startup.
- 41648 — Get current progress was called on '%ls' database (ID %d) which had undo of redo pending. Refer to the SQL Server error log for information about the …
- 41649 — Could not submit Change Role completion tasks for %ls' (URI: '%ls', partition ID '%ls') . Encountered error (error code: 0x%08X).
- 41650 — Waiting for replica catchup for AGID '%ls' and ReplicaID '%ls' Failed.
- 41651 — Invalid partition id in replica manager
- 41652 — The replica manager is unavailable or not ready.
- 41653 — Database '%.*ls' encountered an error (error type: %d '%.*ls') causing failure of the availability group '%.*ls'. Refer to the SQL Server error log fo…
- 41654 — Failed to start the clean up nonexistant DBs thread during replica manager startup.
- 41655 — Could not submit logical reseeding task for '%ls' (URI: '%ls', partition id: '%ls') . Encountered error (error code: 0x%08X).
- 41656 — Failed to start the windows fabric load balancer reporting thread during replica manager startup.
- 41657 — Database '%ls' (ID %d) of Windows Fabric partition '%ls' (partition ID '%ls') failed the call to UseDB.
- 41658 — Failed to automatically enable Query Store in Database '%ls' (ID %d) of Windows Fabric partition '%ls' (partition ID '%ls') .
- 41659 — Checkpoint for Database '%ls' (ID %d) failed. Encountered error (error code: 0x%08X).
- 41660 — Windows Fabric service '%ls' (partition ID '%ls') received a primary replica information message from remote replica '%ls' with an epoch [%I64d,%I64d]…
- 41661 — There are no waiters on the DataLossEvent for Fabric Service '%ls' (partition ID '%ls').
- 41662 — Database '%ls' (ID %d) of Windows Fabric partition '%ls' (partition ID '%ls') hit exception while running async tasks in Generic Subscriber.
- 41663 — Failed to parse datawarehouse columnar cache settings during replica manager startup.
- 41664 — Failed to refresh remote replica configuration for fabric service '%ls'.
- 41665 — Failed to resolve DW logical node id for physical database '%ls', which is hosted by compute service: '%ls'.
- 41666 — Waiting for replica catchup before GeoDR role change failed for with error %d for database '%ls', DBID %d, AGID '%ls', and ReplicaID '%ls'.
- 41667 — Fabric Service '%ls' (partition ID '%ls') encountered error (error code: 0x%08X) while setting Fabric property '%ls'.
- 41668 — Failed to transition to forwarder role for physical database '%ls' (ID %d) of Windows Fabric partition '%ls' (partition ID '%ls').
- 41669 — Database '%ls' (ID %d) of Windows Fabric partition '%ls' (partition ID '%ls') hit exception while running async tasks in RbIo Subscriber.
- 41670 — Cannot retrieve tempdb remote file lease order id.
- 41671 — Failed to transition to secondary role for physical database '%ls' (ID %d) of Windows Fabric partition '%ls' (partition ID '%ls').
- 41672 — Failed to obtain if the application is the VLDB reverse migration target. Application name: '%ls'. HRESULT [%d].
- 41673 — Failed to start up the log replica for physical database '%ls'. HRESULT [%d].
- 41674 — HyperScale Storage V1 to V2 migration source database '%ls' is already Storage V2.
- 41675 — HyperScale Storage V1 to V2 migration for source database '%ls' is already started.
- 41676 — Source database '%ls' is in geo relationship and is not supported for migration.
- 41677 — Source database '%ls' does not match the logical database id provided.
- 41678 — Failed to transition to PRIMARY role for physical database '%ls' (ID %d) of Windows Fabric partition '%ls' (partition ID '%ls').
- 41679 — Transition to PRIMARY role for physical database '%ls' (ID %d) of Windows Fabric partition '%ls' (partition ID '%ls') has been aborted.
- 41680 — An error has occurred while executing an asynchronous operation (HRESULT 0x%08x).
- 41681 — SQL Server cannot generate grip tds redirection url of the replica with ID %ls (Windows Fabric partition ID %ls).
- 41682 — Fabric Service '%ls', partition (ID %ls), replica (ID 0x%08X) failed to initialize RBIO transport when openning the replica for database '%ls' with er…
- 41683 — Fabric Service '%ls', partition (ID %ls), replica (ID 0x%08X) failed to setup SDA RBIO connections for database '%ls' with error (HRESULT 0x%08x). If …
- 41684 — Fabric Service '%ls', partition (ID %ls), replica (ID 0x%08X), database '%ls' failed to transition to GxM state.
- 41685 — Could not start probe listener for '%ls' (URI: '%ls', partition ID '%ls'). Encountered error (error code: 0x%08X).
- 41686 — Could not stop probe listener for '%ls' (URI: '%ls', partition ID '%ls'). Encountered error (error code: 0x%08X).
- 41687 — Missing probe listener for '%ls' (URI: '%ls', partition ID '%ls').
- 41688 — Invalid probe listener port '%d' for %ls' (URI: '%ls', partition ID '%ls').
- 41689 — Failed to set probe listener endpoint for '%ls' (URI: '%ls', partition ID '%ls'). Encountered error (error code: 0x%08X).
- 41690 — Fabric Service '%ls', partition (ID %ls), replica (ID 0x%08X) failed to set up health monitor for database '%ls' with error (HRESULT 0x%08x).
- 41700 — System views related to Windows Fabric partitions and replicas are not available at this time, because replica manager has not yet started. Wait for r…
- 41701 — The Activation Context is unavailable at this time. The Windows Fabric Runtime is unavailable at this time, retry later. Wait for the activation conte…
- 41702 — The requested Configuration Package is unavailable at this time. The Configuration Package is not a part of the Activation Context. Verify that the re…
- 41703 — The requested Service Endpoint is unavailable at this time. The Service Endpoint is not a part of the Activation Context. Verify that the requested Se…
- 41704 — The datasource name is not correctly formatted. The datasource name exceeds the maximum path length or does not adhere to defined format. Verify that …
- 41705 — The computer name is unavailable. The computer name was not returned.
- 41706 — Unable to get Fabric NodeContext.
- 41801 — Failed to drop the memory optimized container '%.*ls'.
- 41802 — Cannot drop the last memory-optimized container '%.*ls'.
- 41803 — An In-Memory OLTP physical database was restarted while processing log record ID %S_LSN for database '%.*ls'. No further action is necessary.
- 41804 — Internal error for database '%.*ls' (lookup for HkTruncationLsn failed). The operation will be retried. No user action is required. If the problem per…
- 41805 — There is insufficient memory in the resource pool '%ls' to run this operation on memory-optimized tables. See ' http://go.microsoft.com/fwlink/?LinkID…
- 41806 — Parameter "%ls" specified for procedure or function "%ls" is not valid.
- 41807 — A MARS batch failed due to a unique constraint violation on a memory optimized table.
- 41808 — The current MARS batch attempted to update a record that has been updated by another batch within the same transaction.
- 41809 — Natively compiled triggers do not support statements that output a result set.
- 41810 — Stored procedures called from natively compiled triggers do not support statements that output a result set.
- 41811 — XTP physical database was stopped while processing log record ID %S_LSN for database '%.*ls'. No further action is necessary.
- 41812 — ALTER TABLE on memory-optimized tables is not supported with concurrent MARS transactions.
- 41813 — XTP database '%.*ls' was undeployed. No further action is necessary.
- 41814 — The procedure '%.*ls' cannot be called from a user transaction.
- 41815 — Data migration on table id %d cannot be performed because the table is already in the process of migration.
- 41816 — The parameter '%.*ls' for procedure '%.*ls' cannot be NULL.
- 41817 — Invalid object id %d provided as input for procedure '%.*ls'. The object id must refer to a memory-optimized table with a column store index.
- 41818 — An upgrade operation failed for database '%.*ls' attempting to upgrade the XTP component from version %u.%u to version %u.%u. Check the error log for …
- 41819 — A MARS batch failed due to a validation failure for a foreign key constraint on memory optimized table '%.*ls'. Another interleaved MARS batch deleted…
- 41820 — A MARS batch failed due to a validation failure for a foreign key constraint on memory optimized table '%.*ls'. Another interleaved MARS batch inserte…
- 41822 — There is insufficient disk space to generate checkpoint files and as a result the database is in delete-only mode. In this mode, only deletes and drop…
- 41823 — Could not perform the operation because the database has reached its quota for in-memory tables. See ' http://go.microsoft.com/fwlink/?LinkID=623028 '…
- 41824 — The transaction was killed by a concurrent ALTER operation or by a write-write conflict.
- 41825 — Stored procedure '%.*ls' cannot be used to increase the user memory limit on the database.
- 41826 — Stored procedure '%.*ls' tried to set a lower limit to the user memory quota. The operation failed because the user memory consumption is larger than …
- 41827 — Upgrade of XTP physical database '%.*ls' requires restart of XTP engine.
- 41828 — Creation of memory-optimized tables is temporarily disabled. Please try again later.
- 41829 — The database cannot proceed with pricing-tier update as it has memory-optimized objects. Please drop such objects and try again.
- 41830 — Upgrade of XTP physical database '%.*ls' restarted XTP engine.
- 41831 — Data migration on table id %d failed either fully or partially. See errorlog for details.
- 41832 — Index '%.*ls' cannot be created on table '%.*ls', because at least one key column is stored off-row. Index key columns memory-optimized tables must fi…
- 41833 — Columnstore index '%.*ls' cannot be created, because table '%.*ls' has columns stored off-row. Columnstore indexes can only be created on memory-optim…
- 41834 — ALTER TABLE has failed for '%.*ls' with error code %d.
- 41835 — An error (error code: 0x%08lx) occurred while adding encryption keys to XTP database '%.*ls'.
- 41836 — Rebuilding log is not supported for databases containing files belonging to MEMORY_OPTIMIZED_DATA filegroup.
- 41837 — Boot-page adjustment of XTP database '%.*ls' requires restart of XTP engine.
- 41838 — Failed to retrieve size for this file due to an internal error. Please try again later.
- 41839 — Transaction exceeded the maximum number of commit dependencies and the last statement was aborted. Retry the statement.
- 41840 — Could not perform the operation because the elastic pool has reached its quota for in-memory tables. See ' http://go.microsoft.com/fwlink/?LinkID=6230…
- 41841 — Found inconsistent boot-page for database '%.*ls'.
- 41842 — Too many rows inserted or updated in this transaction. You can insert or update at most 4,294,967,294 rows in memory-optimized tables in a single tran…
- 41843 — Unable to construct segment for segment table.
- 41844 — Clustered columnstore indexes are not supported on memory optimized tables with computed columns.
- 41845 — Checksum verification failed for memory optimized checkpoint file %.*ls.
- 41846 — Memory optimized checkpoint table consistency error detected. Checkpoint %I64d does not have unique recoverLsn. PrevLSN = (%I64d:%hu), CurrLSN = (%I64…
- 41847 — Memory optimized checkpoint table consistency error detected. Checkpoint %I64d does not point to a transaction segment definition record.
- 41848 — Memory optimized checkpoint table consistency error detected. Checkpoint %I64d does not have ascending recoverLsn. PrevLSN = (%I64d:%hu), CurrLSN = (%…
- 41849 — Memory optimized segment table consistency error detected. Segments are not contiguous in logical space. Older Segment CkptId = %I64d, LsnInfo = (%I64…
- 41850 — Memory optimized segment table consistency error detected. Segments are not well formed for Segment CkptId = %I64d, LsnInfo = (%I64d:%hu), TxBegin = %…
- 41851 — Memory optimized segment table consistency error detected. Segment definition ordering does not match the (strict) logical ordering. Older Segment Ckp…
- 41852 — Memory optimized segment table consistency error detected. Segment has a NullHkLsn. CkptId = %I64d, Segment LsnInfo = (%I64d:%hu)
- 41853 — Memory optimized segment table consistency error detected. Current segment goes backward further than the definition record of the N-2 segment. Older …
- 41854 — Memory optimized file consistency error detected. An in use file with FileId %.*ls is referenced by the Checkpoint File Table but is not accounted for…
- 41855 — 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 — Memory optimized file consistency error detected. A file with FileId %.*ls of size %I64d bytes is smaller than expected %I64d bytes.
- 41857 — Memory optimized file consistency error detected. A presumably in use file with FileId %.*ls was not found in the Checkpoint File Table.
- 41858 — Memory optimized file consistency error detected. A presumably in use file with FileId %.*ls was not found in the File Watermark Table.
- 41859 — Memory optimized file consistency error detected. A presumably in use file with FileId %.*ls of size %I64d bytes is smaller than expected (%I64d bytes…
- 41860 — Memory optimized file consistency error detected. A presumably unused file with FileId %.*ls was found in the Checkpoint File Table.
- 41861 — Memory optimized large rows table consistency error detected. File Id is %.*ls. Corresponding LSN range is not ascending. Begin Lsn is (%I64d:%hu), En…
- 41862 — Memory optimized large rows table consistency error detected. Corresponding File %.*ls not found in File Table. Begin Lsn is (%I64d:%hu), End Lsn is (…
- 41863 — Checkpoint %I64d points to a root file %.*ls which was in use by a more recent checkpoint.
- 41864 — Checkpoint %I64d has a file %.*ls which has a watermark (%I64d) larger than the more recent checkpoints watermark (%I64d).
- 41865 — File %.*ls does not have a pair file %.*ls
- 41866 — Unprocessed File %.*ls does not have a pair file which is also unprocessed. Processed pair file is %.*ls.
- 41867 — Consistency errors detected in the MEMORY_OPTIMIZED_DATA filegroup. See preceding error messages for details. Consult https://go.microsoft.com/fwlink/…
- 41868 — Memory optimized filegroup checks could not be completed because of system errors. See errorlog for more details.
- 41869 — In-memory OLTP version %u.%u is not supported on this platform.
- 41870 — Dropped %d Orphan Internal Table(s).
- 41871 — Failed to recreate XTP non-durable tables during recovery of the database '%.*ls'.
- 41872 — Warning: Article with varchar(max), nvarchar(max) or varbinary(max) data type column(s) are not supported with memory optimized tables on subscribers …
- 41873 — File in memory-optimized filegroup must have MAXSIZE set to be UNLIMITED.
- 41874 — There are %d orphaned internal table(s) eligible for removal. Investigate the error log for the table identifiers. CHECKPOINT the database, create a f…
- 41875 — The operation on database '%ls' cannot complete because XTP engine is running in checkpoint-only mode due to insufficient memory. Memory-optimized tab…
- 41876 — CREATE TABLE has failed for '%.*ls' with error code 0x%x. This may be a transient condition, please retry.
- 41877 — A user defined function referencing memory optimized tables on a MARS connection with an explicit user transaction is currently disallowed. Use a stat…
- 41878 — In-Memory OLTP database '%.*ls' is Checkpoint V2 Undeployed. No further action is necessary.
- 41879 — Cannot perform operation since In-Memory OLTP database undeployment is in progress. Complete database undeployment before running the file operation.
- 41880 — In-Memory OLTP database undeployment failed. There are in-memory database objects present, or being created.
- 41881 — The Hekaton DLL generator (HkDllGen) process failed while compiling a natively compiled In-Memory OLTP module (exit code: %d). A dump file has been ge…
- 41899 — The operation caused an undefined internal error (HRESULT: %X).
- 41900 — The creation of a Managed Instance link of a database failed because the database has a custom persistent version store (PVS) filegroup set. Consider …
- 41901 — One or more of the options (%ls) are not supported for this statement in SQL Managed Instance. Review the documentation for supported options.
- 41902 — Unsupported device type. SQL Managed Instance supports database restore from URI backup device only.
- 41903 — CREATE DATABASE failed. Cannot create filename %ls. Local file paths are not supported.
- 41904 — BACKUP DATABASE failed. SQL Database Managed Instance supports only COPY_ONLY full database backups which are initiated by user.
- 41905 — Stored procedure %ls is not supported in SQL Database Managed Instance.
- 41906 — Statement '%.*ls' is not supported in SQL Database Managed Instance.
- 41907 — Unsupported file type during restore on SQL Database Managed Instance.
- 41908 — Only 'local' routes are supported in SQL Database Managed Instance.
- 41909 — Modifying logical file name is not supported in SQL Database Managed Instance.
- 41910 — Add/remove/modify of log files is not supported in SQL Database Managed Instance.
- 41911 — Adding or removing XTP file or filegroup is not allowed in SQL Database Managed Instance.
- 41912 — Maximum number of databases for SQL Database Managed Instance reached.
- 41913 — Multiple filestream files are not supported in SQL Database Managed Instance.
- 41914 — SQL Server Agent feature %ls is not supported in SQL Database Managed Instance. Review the documentation for supported options.
- 41915 — Memory-optimized filegroup must be empty in order to be restored on the current tier of SQL Database Managed Instance.
- 41916 — Maximum number of %u files for SQL Database Managed Instance reached.
- 41917 — Dropping local instance via sp_dropserver is not allowed in SQL Database Managed Instance.
- 41918 — Specifying files and filegroups in CREATE DATABASE statement is not supported on SQL Database Managed Instance.
- 41919 — Multiple backup sets in a single backup file are not supported in SQL Database Managed Instance.
- 41920 — This feature is not supported through T-SQL on SQL Database Managed Instance.
- 41921 — Restoring from a backup that contains multiple log files is not supported in SQL Database Managed Instance.
- 41922 — The backup operation for a database with service-managed transparent data encryption is not supported on SQL Database Managed Instance.
- 41923 — Cannot find server certificate with thumbprint '%.*ls'. Please use PowerShell Cmdlet 'Add-AzureRmSqlManagedInstanceTransparentDataEncryptionCertificat…
- 41924 — All files need to be smaller or equal to %d MB in this edition of Managed Instance. File id: %ld. Size: %I64d bytes.
- 41925 — 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.
- 41926 — Secondary filegroup is not supported in this edition of Managed Instance. File id: %ld.
- 41927 — The file name 'XTP' is reserved for the files containing In-Memory OLTP data.
- 41928 — The filegroup name 'XTP' is reserved for the filegroup containing In-Memory OLTP data.
- 41929 — One or more files are not in online state after the restore.
- 41930 — Modifying number of files and max size for TempDb is not yet supported in SQL Database Managed Instance.
- 41931 — Warning: New name of managed database '%.*ls' is same as the old one.
- 41932 — Cannot rename managed database '%.*ls' because it's currently in use.
- 41933 — Failed to initialize detours and local time for Managed Instance. %ls
- 41934 — Statement '%.*ls' is not supported in the current version of the server.
- 41935 — Managed Instance has reached the total capacity of underlying Azure storage account. Azure Premium Storage account is limited to 35TB of allocated spa…
- 41936 — This feature is not supported in the Hyperscale edition of SQL Database Managed Instance.
- 41937 — BACKUP WITH COPY_ONLY cannot be performed until after the next automatic BACKUP LOG operation
- 41938 — BACKUP WITH COPY_ONLY cannot be performed since database encryption key for the database '%.*ls' still exists. Retry command after you drop database e…
- 41939 — The Persistent Version Store filegroup must be set to the PRIMARY filegroup in order to be restored on SQL Database Managed Instance.
- 41940 — Cross-db xact outcome cleanup failed due to unavailable/inaccessible databases.
- 41941 — Changing recovery model for database with ID %lu is not supported and corresponding error has been suppressed as per server configuration. See https:/…
- 41942 — Renaming local instance is not allowed in SQL Database Managed Instance.
- 41943 — SQL Database Managed Instance does not support creating route with TRANSPORT or MIRROR address.
- 41944 — Cannot change the recovery model in Managed Instance Azure Arc environment
- 41945 — Cannot rename managed database '%.*ls' to an empty name.
- 41946 — SQL Database Managed Instance does not support modifying default size of TempDb files.
- 41947 — Memory-optimized filegroup must be empty on the SQL Server source database when replicated to Azure SQL Managed Instance with service tier not support…
- 41948 — Azure SQL Managed Instance link data replication requires source database on SQL Server to have a single log file instead of multiple log files. Consi…
- 41949 — Managed Instance link cannot replicate data because maximum number of %u files were reached on Azure SQL Managed Instance. Consider reducing the numbe…
- 41950 — Source database on SQL Server must not use FileStream or FileTables for data replication to Azure SQL Managed Instance. Consider removing FileStream a…
- 41951 — Azure SQL Managed Instance link cannot be created with source database '%.*ls' on SQL Server, because the database contains files in DEFUNCT state. Re…
- 41952 — Azure SQL Managed Instance link cannot be created with source database '%.*ls' on SQL Server, bacause the database contains unsupported feature '%.*ls…
- 41953 — Functionality cannot be used as it is not available on Azure SQL Managed Instance.
- 41954 — Transient error occurred on database '%.*ls' while trying to change managed instance role to primary. The system will automatically retry the operatio…
- 41955 — Transient error occurred while trying to retrieve backup metadata for database '%.*ls'. The system will automatically retry the operation. If the issu…
- 41956 — Transient error occurred while trying to retrieve backup URIs property for database '%.*ls'. The system will automatically retry the operation. If the…
- 41957 — Backup URIs property for database '%.*ls' contains invalid data. Consider engaging Microsoft support for Azure SQL Managed Instance.
- 41958 — Transient error occurred as backup metadata is unavailable for database '%.*ls' due to error %u. The system will automatically retry the operation. If…
- 41959 — Transient error occurred while reading from backup metadata for database '%.*ls' due to error %u. The system will automatically retry the operation. I…
- 41960 — Transient error occurred while writing to backup metadata for database '%.*ls' due to error %u. The system will automatically retry the operation. If …
- 41961 — Transient error occurred during the instance role change to primary. The system will automatically retry the operation. If the issue persists, contact…
- 41962 — Operation was aborted as replication between SQL Server and Azure SQL Managed Instance did not start within %u minutes since it was initiated. Please …
- 41963 — Certificate cannot be created as it is already used with '%.*ls' feature. Consider using a different certificate.
- 41964 — The '%.*ls' operation cannot be completed as there exists a database in the process of creation through Azure SQL Managed Instance link. Please wait f…
- 41965 — Setting the role cannot be applied as Azure SQL Managed Instance is already in the requested role.
- 41966 — The '%.*ls' operation cannot be completed as '%.*ls' server configuration option is not supported.
- 41967 — The '%.*ls' operation cannot be completed as incorrect value was specified for '%.*ls' server configuration option.
- 41968 — Changing the server role cannot be executed at this time as there exist a previous role change in progress on Azure SQL Managed Instance. Only when th…
- 41969 — Setting the role has failed due to an unknown reason. Please check the error log file. If the issue persists, contact Azure support.
- 41970 — Switching to Primary role in planned fashion is not supported.
- 41971 — Azure SQL Managed Instance link connectivity was lost because either connection to SQL Server failed, or the server did not respond after a prolonged …
- 41972 — Azure SQL Managed Instance link creation failed because of a link type mismatch between multi-database and single-database link configurations. A mult…
- 41973 — The link cannot be established because the endpoint certificate from SQL Server has not been imported to Azure SQL Managed Instance. Please import the…
- 41974 — The link cannot be established because the endpoint certificate from SQL Azure SQL Managed Instance has not been imported to SQL Server. Please downlo…
- 41975 — Unsupported storage type. Azure SQL Managed Instance does not support database backup to the provided storage type.
- 41976 — Connection with availability group '%.*ls' on the server with endpoint '%.*ls' cannot be established as it is not responding. Possible causes could be…
- 41977 — Connection with availability group '%.*ls' on the server with endpoint '%.*ls' is established, but there is no response from the target database. Poss…
- 41978 — The parameters (%ls) are not supported for this stored procedure in SQL Database Managed Instance. Review the documentation for supported parameters.
- 41979 — Managed database cannot be replicated from Managed Instance to SQL Server, as this managed database is encrypted with service managed key. Either unen…
- 41980 — Database cannot be encrypted using the service managed key as it is being replicated from Managed Instance to SQL Server. Switch the encryption protec…
- 41981 — Switching the encryption protector from customer managed (BYOK) to service managed is not allowed as there exists database replication from Managed In…
- 41982 — Database cannot be replicated from Managed Instance to SQL Server as there already exists database geo-replication from this Managed Instance to anoth…
- 41983 — In-Memory OLTP database undeployment is not allowed on SQL Database Managed Instance.
- 41984 — The link cannot be created because database format of the source SQL Managed Instance is not compatible with database format of the destination SQL Se…
- 41985 — Forced failover is not supported on this managed instance link. For database migration, please delete the link instead.
- 41986 — Azure SQL Managed Instance link creation failed because either connection to SQL Server failed, or the server did not respond after a prolonged period…
- 41987 — Managed Instance link cannot be created because Managed Instance side AG name '%.*ls' is already used on Managed Instance '%.*ls'. Choose different na…
- 41988 — The link supporting bi-directional failover requires matching database formats on source and target server.
- 41989 — The parameters (%ls) can only be set/updated on SQL Database Managed Instance. Review the documentation for supported parameters.
- 41990 — %s cannot be null or empty when %s is set to 0 (SQL Server Authentication).
- 41991 — Unable to make database %s on SQL Managed Instance %s accessible because the instance role in failover group changed from %s to %s while the database …
- 41992 — Unable to make database %s on SQL Managed Instance %s accessible due to ongoing geodr operation. Please wait until the conflicting operation completes…
- 41993 — Cannot execute failover of Managed Instance link '%s' because the replica of database '%s' on the managed instance is in an inaccessible state.
- 41994 — Database name '%.*ls' is used in an ongoing Azure SQL Managed Instance link creation operation on SQL Managed Instance %s. Wait for the ongoing operat…
- 41995 — A create operation for the same Managed Instance link is already in progress (operation id '%s') with different 'partnerEndpoint' configuration settin…
- 41996 — Managed failover group creation failed due to subnet overlap between source and target servers. Ensure that the source and target servers are using no…
- 41997 — Managed failover group creation failed due to TCP connectivity check failure. Server '%s' could not establish TCP connection to server '%s' on port %d…
- 41998 — Managed Instance link creation failed because encryption is not enabled on the on-premises SQL Server endpoint. Enable encryption on the database mirr…
- 41999 — Source database on SQL Server must not contain full-text catalog files for data replication to Azure SQL Managed Instance. Consider removing full-text…
- 42001 — Failed to parse XML configuration. The operating system returned error %ls.
- 42002 — Failed to parse XML configuration. The parser returned error %.*ls
- 42003 — Failed to parse XML configuration. A required attribute '%ls' is missing.
- 42004 — Failed to parse XML configuration. A required element '%ls' is missing.
- 42005 — Failed to parse XML configuration. Invalid value for attribute '%ls'.
- 42006 — The default tempdb directory ('%ls') in XDB is not a valid path.
- 42007 — The default tempdb directory ('%ls') in XDB is not a local path.
- 42008 — ODBC error: State: %ls: Error: %d Message:'%ls'.
- 42009 — Instance certificate '%ls' cannot be found.
- 42010 — Cannot initiate cross instance connection.
- 42011 — ODBC initialization error: : %d.
- 42012 — XodbcWrapper Enforced Retry For Testing.
- 42013 — HTTP initialization error: : %d.
- 42014 — Cannot retrieve server admin credential configuration.
- 42015 — Error occurred while attempting to authenticate user remotely. Error %d, State %d.
- 42016 — Error occurred in the DosGuard.
- 42017 — Error occurred in the Redirector's proxy while parsing a packet. Expected: %d, Actual: %d.
- 42018 — Remote transaction has been doomed and cannot commit.
- 42019 — %ls operation failed. %ls
- 42020 — Updating name to '%.*ls' failed.
- 42021 — Initialization of http session handle for fetching federation metadata failed during AzureActiveDirectory initialization.
- 42022 — Initialization of http connect handle for fetching federation metadata failed during AzureActiveDirectory initialization.
- 42023 — Updating userdb properties on copy termination failed.
- 42024 — Switching to logical master database failed.
- 42025 — The extended recovery fork stack in the metadata of FCB is either corrupted or in an unexpected format.
- 42026 — Loading the Active Directory Library failed.
- 42027 — Initialization of the Active Directory Function pointers failed.
- 42028 — The database '%.*ls' has been detached as it was marked as a shared disk instance and was not started. This is an informational message; no user actio…
- 42029 — An internal error happened while generating a new DBTS for database "%.*ls". Please retry the operation.
- 42030 — Updating logical master's sys.databases on seeding completion failed.
- 42031 — This functionality is not supported for A/B test isolated instances.
- 42032 — XODBC Get Authentication Cache failed, state %d
- 42033 — Updating Layered AG Configuration failed.
- 42034 — Boot of federation host failed with error 0x%08X.
- 42035 — %ls operation timed out. Request was sent to the service resulting in response timeout. The operation might start anyway.
- 42036 — %ls operation has been cancelled.
- 42037 — Initialization of http session handle for fetching cert public keys for MWC token signature validation during signature validation service initializat…
- 42038 — Initialization of http connect handle for fetching cert public keys for MWC token signature validation during signature validation service initializat…
- 42039 — Failed to decompress compressed parameter data. The provided VARBINARY data is not valid GZip-compressed UTF-8 content.
- 42101 — Reason: Unable to create or update firewall rules since Deny Public Network Access is set to Yes. Please set Deny Public Network Access to No and retr…
- 42102 — Reason: Unable to set Deny Public Network Access to Yes since there is no private endpoint enabled to access the server. Please set up private endpoin…
- 42103 — The SQL Pool '%.*ls' already exists. Please choose a new name.
- 42104 — Could not create SQL Pool '%.*ls'. Please try again later.
- 42105 — The server role '%.*ls' already exists. Please choose a new name.
- 42106 — Could not create Server Role '%.*ls'. Please try again later.
- 42107 — Could not create SQL Pool '%.*ls', it must be less than %d characters.
- 42108 — Can not connect to the SQL pool since it is paused. Please resume the SQL pool and try again.
- 42109 — The SQL pool is warming up. Please try again.
- 42110 — The IPv6 firewall rule name cannot be empty.
- 42111 — '%.*ls' is not a valid IPv6 address.
- 42112 — The IPv6 address that starts with '%.*ls' is too long. Maximum length is %d.
- 42113 — Start IPv6 address of firewall rule cannot exceed End IPv6 address.
- 42114 — Windows Azure SQL Database supports a maximum of 128 IPv6 firewall rules.
- 42115 — IPv6 Feature Support is not Enabled
- 42116 — Cannot open database "%.*ls" requested by the login because this database is currently being dropped. The login failed.
- 42117 — The elastic pool '%.*ls' has reached its active database count limit. The active database count for the elastic pool cannot exceed (%d) for the curren…
- 42118 — Login failed because the network security perimeter denied inbound access.
- 42119 — This database has reached the monthly free amount allowance for the month of %.*ls and is paused for the remainder of the month. The free amount will …
- 42120 — The connection was denied because the server's Public Network Access is set to 'SecuredByPerimeter', but the resource is not in a Network Security Per…
- 42121 — The operation could not be completed on because attempts to connect were denied by the configured Network Security Perimeter.
- 42122 — Cannot resume database '%.*ls' in any elastic pool because all eligible pools are at capacity.
- 42123 — Login failed as it was determined that the common alias login was invoked, but the common alias login is not currently supported.
- 42124 — Login failed as it was determined that the common alias login was invoked, but the database name has not been provided.
- 42125 — Enabling IPv6 is currently not supported on your server, detailed reason is: %.*ls.
- 42126 — This serverless database is paused and cannot be resumed by this connection.
- 42127 — The login failed due to proxy throttling
- 42128 — Database '%ls' cannot be converted to Hyperscale because it has more than one geo-secondary replica. Reduce the number of geo-secondary replicas to at…
- 42129 — Database '%ls' cannot be converted to Hyperscale because it has chained geo-secondary replicas. Remove chained geo-secondaries and retry the operation…
- 42130 — A geo-secondary replica '%ls' cannot be converted to Hyperscale. To convert both the primary and geo-secondary replicas to Hyperscale, retry the opera…
- 42131 — This SQL database has been disabled. Please reach out to your Fabric Capacity administrator for more information.
- 42132 — The login failed due to database name not being found in alias DB
- 42133 — The firewall rule name cannot contain special characters: '%ls'.
- 42134 — Cannot open database "%.*ls" requested by the login because this database is participating in a failover group as a secondary and has geo link in an i…
- 42135 — A SQL server cannot be associated with a network security perimeter if it contains one or more dedicated SQL pools (formerly SQL DW)
- 42136 — Login failed because the reader endpoint feature is not enabled.
- 42137 — Reason: Login failed because database name cannot be specified for reader endpoint connections.
- 42138 — Reason: Login failed because the Enhanced Routing data sent by the client library is malformed.
- 42139 — Reason: Login on a reader endpoint connection failed because the Enhanced Routing feature extension data is missing.
- 42140 — Login failed because the Enhanced Routing feature is not enabled.
- 42141 — The connection failed due to an internal error.
- 42142 — The limit in the number of connection attempts to the paused database has been reached. New connections to the paused database are disallowed until %.…
- 42143 — Reason: Login failed because the database name specified for the reader endpoint "%.*ls" is not the primary database of that reader endpoint.
- 42144 — Reason: Login failed because no database name was specified for the reader endpoint "%.*ls".
- 42201 — The requested distance metric '%.*ls' is not supported by vector_distance. Provide a valid distance metric.
- 42202 — The provided dimension for the vector (%d) does not match allowed value (%d).
- 42203 — The provided dimension for the vector (%d) is not within the allowed range [1-%d].
- 42204 — The vector dimensions %d and %d do not match.
- 42205 — The vector types '%ls' and '%ls' do not match.
- 42206 — The vector is invalid. Error details: '%ls'.
- 42207 — The distance metric specified for vector_distance is unsupported. Please provide a valid string for distance metric.
- 42208 — The vector LOB type is not supported. Please use a supported vector type.
- 42209 — A system error occurred.
- 42210 — The requested norm function '%.*hs' is not supported by vector_norm/vector_normalize. Please provide a valid norm function.
- 42211 — Truncation of vector is not allowed during the conversion. Ensure the vector size is appropriate before conversion.
- 42212 — Cannot create alias types from a vector datatype.
- 42213 — The vector data types cannot be compared or sorted, except when using the IS NULL operator.
- 42214 — Could not create the vector index on object '%.*ls', because the object is not a user table.
- 42215 — Could not create the vector index on the column '%.*ls' on table '%.*ls', because it is not of type vector.
- 42216 — Internal error occurred while creating the vector index. Please run DBCC CHECKCATALOG and retry if it does not report any error. Please contact suppor…
- 42217 — Table '%.*ls' must have a clustered primary key on a single 4 byte INT column to create a vector index.
- 42218 — Failed to fetch metadata for the vector index. Please retry and contact support if the error persists.
- 42219 — Failed to create internal table %d for the vector index.
- 42220 — Cannot create the vector index on temp objects. '%.*ls' is identified as a temp object.
- 42221 — DROP VECTOR INDEX does not support any options.
- 42222 — Vector data type is not supported in CDC tracked table.
- 42223 — Vector data type is not supported in transactional replication.
- 42224 — Vector data type is not supported in generic replication features.
- 42225 — VECTOR column(s) cannot be natively imported through BULK INSERT or OPENROWSET(BULK) statement.
- 42226 — The column '%.*ls' is not of vector type. Vector search cannot be performed on a non-vector column.
- 42227 — Cannot find a vector index with metric '%.*ls' on column '%.*ls'.
- 42228 — Cannot create vector index on a partitioned table.
- 42229 — Cannot create partitioned index on a table having a vector index.
- 42230 — Cannot create vector index on column '%.*ls' because it already has an existing vector index.
- 42231 — Data modification statement failed because table '%.*ls' has a vector index on it.
- 42232 — TRUNCATE TABLE statement failed because table '%.*ls' has a vector index on it.
- 42233 — Query join hint incompatible with vector search.
- 42234 — Internal SQL error during DiskANN graph build.
- 42235 — Invalid value for optional parameter L (%hu) and R (%hu). Please ensure L >= R.
- 42236 — The value of R (%hu) is too low. Please ensure R is greater than or equal to %d.
- 42237 — The vector index cannot be created because filegroup '%.*ls' does not exist or the filegroup name is incorrectly specified.
- 42238 — Conversion of vector from data type %ls to %ls is not allowed.
- 42239 — Vector index background cleaner cleaned the inbuild vector index ID %d on object ID %d in database ID %d.
- 42240 — Vector data type is not supported in merge replication.
- 42241 — Input JSON contains out-of-range values for %ls.
- 42242 — Input JSON contains %ls type which is not supported in ARM64 architecture.
- 42243 — VECTOR_DISTANCE function does not support different base types for vector arguments.
- 42244 — A vector index cannot be created on tables with security policies. Table '%.*ls' has security policy '%.*ls'.
- 42245 — Drop and recreate the incompatible vector index ID %d on object ID %d.
- 42246 — %ls function does not support vector with base type %ls.
- 42247 — Vector with base type float16 is not supported in transactional replication.
- 42248 — APPROXIMATE cannot be used in a query without %ls.
- 42249 — TOP PERCENT cannot be used with APPROXIMATE.
- 42250 — One or more of the specified ALTER INDEX options is unsupported for a Vector Index.
- 42251 — Cannot create vector index '%.*ls' on table '%.*ls.%.*ls', column '%.*ls', because the column is computed.
- 42253 — Invalid value for parameter TOP_N (%d) and/or L (%d). TOP_N must be less than or equal to L, and both must be between 1 and %d inclusive.
- 42254 — Clustered index is required on table '%.*ls' to create a vector index.
- 42255 — Vector index is not supported on tables with more than %I64u rows.
- 42256 — Cannot use vector index '%.*ls' on table '%.*ls.%.*ls'. The vector index is still being built.
- 42257 — Cannot disable vector index '%.*ls' on table '%.*ls.%.*ls'.
- 42258 — Cannot disable the index used by the primary key constraint on table '%.*ls.%.*ls' because it has a vector index.
- 42259 — Vector search cannot use v1 index '%.*ls' on table '%.*ls.%.*ls', column '%.*ls'. Drop and recreate the vector index to use the current index format.
- 42260 — Cannot create vector index on a memory-optimized table '%.*ls'. Vector indexes are not supported on memory-optimized tables.
- 42261 — Vector index '%.*ls' on table '%.*ls' has internal table schema mismatch.
- 42262 — The data modification statement failed because a vector index build on table '%.*ls' is in progress. Try again once the index build completes.
- 42263 — Cannot create vector index on table '%.*ls' because its clustered index is not available. It might be disabled or in the middle of an online or resuma…
- 42264 — A vector index cannot be created on a temporal history table, and a table with a vector index cannot be used as a temporal history table.
- 42265 — A vector provided for quantization is out of the model range. The DML statement cannot be completed. Drop the vector index and use normalized vectors …
- 42266 — Cannot create a vector index. The table contains only %d rows with non-null vectors, but at least %d are required for vector index creation.
- 42267 — index_options must be a valid JSON object string.
- 42268 — The value is invalid for the %ls parameter.
- 42269 — Incorrect use of TOP WITH APPROXIMATE and VECTOR_SEARCH in the context of CROSS or OUTER APPLY. Please refer to https://go.microsoft.com/fwlink/?linki…
- 42270 — APPROXIMATE cannot be used in a query with %ls.
- 42271 — TOP WITH APPROXIMATE and VECTOR_SEARCH requires ORDER BY on distance column ascending, and no other columns.
- 42272 — The specified %ls value is not supported for vector columns with %d dimensions. Use a lower %ls value.
- 42273 — Omitted TOP_N parameter is not supported by the current vector index. Drop and recreate the vector index, or specify the TOP_N parameter in VECTOR_SEA…
- 42274 — Vector search with newer index version does not support explicit TOP_N parameter.
- 42275 — FORCE_ANN_ONLY requires TOP WITH APPROXIMATE.
- 42276 — Skipped %.*ls for vector index '%.*ls' on table '%.*ls.%.*ls'. %.*ls is not supported for vector indexes.
- 42277 — Vector index insert batch complete [database_id=%d, object_id=%d, index_id=%d]: rowsInserted=%I64d, range=[%I64d, %I64d), graphEdgeRows=%I64d, duratio…
- 42278 — The vector index background update tasks can't start because workload group '%ls' is not found. The operation will be retried in %d seconds.
- 42279 — Data masking is not currently available for vector data type.
- 42280 — Incompatible vector index version %d. Drop and recreate the vector index.
- 42281 — Vector index delete batch complete [database_id=%d, object_id=%d, index_id=%d]: rowsDeleted=%I64d, durationMs=%I64d.
- 42282 — The query vector has %d dimensions but the indexed VECTOR column has %d dimensions.
- 42283 — Vector index delete easy/backoff batch complete [database_id=%d, object_id=%d, index_id=%d]: batchSize=%d, actualBatchSize=%I64d, rowsDeleted=%I64d, b…
- 42284 — Conversion from %ls to %ls vector produced out-of-range values.
- 42285 — Vector conversion with %ls type is not supported in ARM64 architecture.
- 42286 — The FORCE_ANN_ONLY hint cannot be used with vector index '%.*ls' on table '%.*ls.%.*ls' because its approximate nearest neighbor (ANN) graph has not b…
- 42287 — The vector index '%.*ls' on table '%.*ls' has exhausted its internal key space. Check sys.dm_db_vector_indexes for details.
- 42288 — The index values in sparse vector are not in strictly ascending order.
- 42289 — The sparse vector contains an index (%d) that is outside the valid range [0, %d].
- 42290 — The sparse vector has more elements (%d) than the maximum of %d supported for this vector.
- 42291 — The number of index values (%d) in the sparse vector does not match the number of data values (%d).
- 42293 — Conversion of vector from %ls to %ls storage format is not supported.
- 42294 — A sparse vector %ls must be an integer in the range [%d, %d].
- 42295 — The %ls function does not support sparse vectors.
- 42299 — Vector Internal error.
- 42301 — Could not create the semantic index on object '%.*ls', because the object is not a user table.
- 42302 — Could not create the semantic index on the column '%.*ls' on table '%.*ls', because it is not of supported type.
- 42303 — Chunking type other than 'fixed' is not supported.
- 42304 — Chunk size specified for a column of semantic index cannot be less than 1.
- 42305 — Supported range for chunk overlap value is between 0 and 50.
- 42306 — Column '%.*ls' has been specified more than once in semantic index DDL command.
- 42307 — Failed to fetch metadata for the semantic index. Try again and contact support if the error persists.
- 42308 — The base table must have a unique clustered index on not nullable column(s).
- 42309 — DROP SEMANTIC INDEX does not support any options.
- 42310 — Missing EXTERNAL_MODEL in the CREATE SEMANTIC INDEX statement.
- 42311 — An internal error occurred while creating the semantic index. Run DBCC CHECKCATALOG and retry if it does not report any error. Contact support in case…
- 42312 — Cannot create the semantic index on temporary table '%.*ls'.
- 42313 — Cannot create semantic index on a partitioned table.
- 42314 — Specifying hybrid or vector search strategy for semantic index column(s) on table '%.*ls', semantic index '%.*ls' requires external model and vector i…
- 42315 — Cannot create semantic index '%.*ls' on table '%.*ls.%.*ls', column '%.*ls', because the column is computed.
- 42316 — Cannot create semantic index on a memory-optimized table '%.*ls'. Semantic indexes are not supported on memory-optimized tables.
- 42317 — A semantic index cannot be created on a temporal history table, and a table with a semantic index cannot be used as a temporal history table.
- 42318 — An internal error occurred in the semantic index document_id reservation path.
- 42319 — TRUNCATE TABLE statement failed because table '%.*ls' has a semantic index on it.
- 42320 — The EXTERNAL_MODEL PARAMETERS value for the semantic index is too long. Specify at most %d characters.
- 42321 — Missing required parameter for semantic index DMF '%.*ls'.
- 42322 — No table found with the specified name '%.*ls'.
- 42323 — An internal error occurred while processing the semantic index.
- 42324 — The user does not have permission to read semantic index data for the table '%.*ls'. SELECT permission on the table is required.
- 42325 — No semantic index created for specified search columns.
- 42326 — No semantic index active for search.
- 42327 — Vector index is missing or unavailable for one or more of the specified search columns.
- 42328 — Full-text index is missing or unavailable for one or more of the specified search columns.
- 42329 — Cannot %S_MSG external model '%.*ls' because semantic index '%.*ls' on table '%.*ls' references it.
- 42330 — TOP WITH APPROXIMATE and SEMANTIC_SEARCH requires ORDER BY on Semantic_Score descending, and no other columns.
- 42331 — TOP_N cannot be specified in SEMANTIC_SEARCH when TOP WITH APPROXIMATE is used for vector-only search.
- 42332 — Semantic_Score cannot be referenced in WHERE or JOIN predicates when TOP WITH APPROXIMATE is used for vector-only SEMANTIC_SEARCH.
- 42333 — Semantic_Score cannot be used in a computed SELECT expression when TOP WITH APPROXIMATE is used for vector-only SEMANTIC_SEARCH.
- 43001 — '%.*ls' is not a valid login name.
- 43002 — Storage in MB %d exceeds the maximum limit %d.
- 43003 — More than one firewall rules have the same name '%.*ls'.
- 43004 — '%.*ls' is not a valid firewall rule name because it contains invalid characters.
- 43005 — '%.*ls' is not a valid database name because it contains invalid characters.
- 43006 — Database name '%.*ls' is too long.
- 43007 — '%.*ls' is not a valid database charset.
- 43008 — '%.*ls' is not a valid database collation.
- 43009 — Storage in MB %d is below the minimum limit.
- 43010 — '%.*ls' cannot be updated.
- 43011 — '%.*ls' is not a valid version.
- 43012 — The configuration name cannot be empty.
- 43013 — The value for configuration '%.*ls' cannot be empty.
- 43014 — The same configuration '%.*ls' cannot be updated more than once.
- 43015 — The configuration '%.*ls' does not exist for %.*ls server version %.*ls.
- 43016 — The value '%.*ls' for configuration '%.*ls' is not valid. The allowed values are '%.*ls'.
- 43017 — The configuration names you defined are not consistent.
- 43018 — The value '%.*ls' for configuration '%.*ls' is not consistent with default value '%.*ls'.
- 43019 — The source '%.*ls' for configuration '%.*ls' is not valid.
- 43020 — The storage size of %d MB is not a valid configuration. Valid storage sizes range from minimum of %d MB and additional increments of %d MB up to maxim…
- 43021 — The point in time %S_DATE is not valid. Valid point in time range from %d days early to now and not before source server creation time.
- 43022 — The edition %.*ls is not a valid edition. Edition cannot be changed by restoring.
- 43023 — The storage size of %d MB is lower than the source storage size.
- 43024 — The version %.*ls is not a valid version. Version cannot be changed by restoring.
- 43025 — Input parameter is incorrect. Please double check the input.
- 43026 — Cannot drop system database '%.*ls', skipping.
- 43027 — Geo Restore is not supported.
- 43028 — The replication feature is not supported.
- 43029 — Edition %.*ls must be the same as the primary server when creating a replica server.
- 43030 — Version %.*ls must be the same as the primary server when creating a replica server.
- 43031 — The storage size of %d MB is lower than the primary server's storage size.
- 43032 — No available primary server %.*ls is found when creating a replica server.
- 43033 — The primary server %.*ls already has the maximum of replica servers.
- 43034 — The replica server is not in ready state when promoting.
- 43035 — '%.*ls' and '%.*ls' cannot be updated together.
- 43036 — Input parameter is incorrect when creating a replica server. Please double check the input.
- 43037 — An internal error was encountered when processing the restore request. This request has been assigned a tracing ID of '%.*ls'. Message is '%.*ls', and…
- 43101 — The specified endpoint returned an unexpected number of rows. The number of rows in the endpoint response must match the number of rows in the request…
- 43102 — Output column '%.*ls' specified in the WITH clause uses the %ls data type which is not supported by the runtime.
- 43103 — Error converting JSON value '%.*ls' to the %ls data type.
- 43104 — Could not parse the JSON package since it does not conform to the defined format.
- 43105 — Error converting a JSON value to %ls. The result would be truncated.
- 43107 — Unexpected status code received from the external endpoint. HTTP Status Code: %d.
- 43201 — The value %I64d is invalid for %.*ls. Value must be between %d and %d.
- 43202 — The value %I64d is invalid for %.*ls. Value must be greater than %d.
- 43203 — The specified %.*ls '%.*ls' is not supported.
- 43204 — An unexpected error has occurred.
- 45001 — %ls operation failed. Specified federation name does not exist.
- 45002 — %ls operation failed. Specified federation distribution name %.*ls is not valid.
- 45003 — %ls operation failed. Specified data type is not supported as a federation distribution.
- 45004 — %ls operation failed. Specified value is not valid for federation distribution %.*ls and federation %.*ls.
- 45005 — Filter value cannot be set or was already set for this session.
- 45006 — The federation key value is out of bounds for this member.
- 45007 — %ls cannot be run while another federation operation is in progress on federation %.*ls and member with id %d.
- 45008 — A partition in a table group that has a partition key defined is not allowed to be a federation member.
- 45014 — %ls is not supported on %S_MSG.
- 45015 — Specified federation operation id is already in use.
- 45016 — Specified federation %.*ls does not exist.
- 45017 — %ls operation failed. Specified federation name %.*ls is not valid.
- 45018 — Specified federation operation id is invalid for %ls operation.
- 45019 — %ls operation failed. Federation is in invalid state.
- 45020 — %ls operation failed. %d is not a valid federation id.
- 45021 — %ls operation failed. %d is not a valid federation member id.
- 45022 — A column insert or update conflicts with a federation member range. The statement was terminated. The conflict occurred in database '%.*ls', table '%.…
- 45023 — %ls cannot be called on %S_MSG.
- 45024 — ALTER FEDERATION SPLIT operation failed. Specified boundary value already exists for federation distribution %.*ls and federation %.*ls.
- 45025 — %ls operation failed. Specified boundary value is not valid for federation distribution %.*ls and federation %.*ls.
- 45026 — %ls operation failed. Specified boundary value does not exist for federation distribution %.*ls and federation %.*ls.
- 45027 — %ls operation failed. Specified type information is not valid for federation distribution.
- 45028 — %ls operation failed. Specified boundary value is not valid for current federation member.
- 45029 — %ls operation failed. The federation distribution scheme size cannot exceed 900 bytes.
- 45030 — The USE FEDERATION statement is missing the required %.*ls option. Provide the option in the WITH clause of the statement.
- 45031 — The USE FEDERATION statement is not supported on a connection which has multiple active result sets (MARS) enabled.
- 45032 — The USE FEDERATION statement is not allowed under non-revertible impersonated security context.
- 45033 — Federation member %d is not available. Another command is creating or dropping it.
- 45034 — Federation member database cannot be dropped using DROP DATABASE.
- 45035 — Federation member database cannot be renamed using ALTER DATABASE.
- 45036 — ALTER FEDERATION SPLIT operation has been aborted. The %.*ls federation was dropped while the split was still in progress.
- 45037 — ALTER FEDERATION SPLIT operation failed due to an internal error. This request has been assigned a tracing ID of '%.*ls'. Provide this tracing ID to c…
- 45038 — CREATE DATABASE AS COPY OF %S_MSG is not supported.
- 45039 — Federation member database cannot be restored.
- 45040 — Service objective for federation member database cannot be changed using ALTER DATABASE.
- 45041 — Federation member database options cannot be changed.
- 45042 — Federation root database options cannot be changed.
- 45043 — ALTER FEDERATION SWITCH %ls is not supported on %ls members.
- 45044 — ALTER FEDERATION SWITCH IN failed. %.*ls is not a valid database that can be switched in.
- 45045 — ALTER FEDERATION SWITCH IN failed. %ls of the federation key in %.*ls doesn't match with the correponding property of federation %.*ls.
- 45046 — %ls operation failed. The specified value for federation %.*ls does not correspond to a present member.
- 45101 — Parameter "%ls" should contain all configurable dimension properties.
- 45102 — Parameter "%ls" should contain settings for all dimensions.
- 45103 — Cannot reset the last setting for a dimension to non-default.
- 45104 — The default setting cannot be deleted for a dimension.
- 45105 — Cannot assign a deprecated setting as successor.
- 45106 — Cannot create new item. The max provision count has been reached.
- 45107 — Cannot reset service objective to draft from enabled or disabled state.
- 45108 — Default service objective cannot be disabled.
- 45109 — Parameter "%ls" contains conflicting dimension setting selections.
- 45110 — Parameter %s value cannot be applied to service objective in non-draft mode.
- 45111 — Cannot reset the last service objective to non-default.
- 45112 — Cannot delete the default service objective.
- 45113 — Cannot set the service objective as default in draft mode.
- 45114 — Cannot edit setting marked as deprecated.
- 45115 — Cannot assign a disabled service objective to a database.
- 45116 — Cannot delete a setting without a successor assigned for deprecation.
- 45117 — Cannot delete a system service objective.
- 45118 — Cannot assign a system service objective to user database.
- 45119 — Property selections contain conflicting values.
- 45120 — The name '%ls' already exists. Choose a different name.
- 45121 — Server '%ls' does not support memory-optimized data. Make sure both source and target servers are enabled for memory-optimized data.
- 45122 — '%ls'
- 45123 — Updating max size is not supported for database '%ls'. Database size will grow automatically as more data is inserted.
- 45124 — Destination instance does not have sufficient storage space to '%ls'. Please make sufficient storage space available at the destination and try again.
- 45125 — Parameter "%ls" cannot be empty or null.
- 45126 — Parameter "%ls" is invalid.
- 45127 — Parameter "%ls" is invalid.
- 45128 — Parameter "%ls" is invalid.
- 45129 — Parameter "%ls" is invalid.
- 45130 — Parameter "%ls" is invalid.
- 45131 — Parameter "%ls" is invalid.
- 45132 — Every database must be assigned a service objective.
- 45133 — A connection failed while the operation was still in progress, and the outcome of the operation is unknown. Query sys.dm_operation_status in the maste…
- 45134 — The remote partner server name '%ls' could not be resolved.
- 45135 — Only continuous database copies can be updated.
- 45136 — Only continuous database copies can be terminated.
- 45137 — Insufficient permission to create a database copy on server '%ls'.
- 45138 — The destination database name '%ls' already exists on the server '%ls'.
- 45139 — The source server name should be the server of the current connection.
- 45140 — Maximum lag does not support the specified value. Maximum lag must be between '%ls' and '%ls'.
- 45141 — Database copies can only be initiated on the source server.
- 45142 — IsForcedTerminate cannot be set while creating a database copy. This can only be updated on the source server after it is created.
- 45143 — The source database '%ls' does not exist.
- 45144 — Continuous copy cannot be initiated on source database '%ls' because it is a federation root member.
- 45145 — Only continuous database copies can be created.
- 45146 — Database copy property '%ls' is required.
- 45147 — Database copy property '%ls' cannot be changed.
- 45148 — '%ls' is not supported for entity '%ls'.
- 45149 — Continuous copy is not supported on 'master' database.
- 45150 — Feature is disabled.
- 45151 — Changing value(s) '%ls' for entity '%ls' not supported.
- 45152 — Termination of a database copy cannot be performed because the destination server '%ls' is unavailable or the database copy does not exist on the dest…
- 45153 — Management Service is not currently available. Please retry the operation later. If the problem persists, contact customer support, and provide them t…
- 45154 — A free database already exists for subscription '%ld' for the selected region. Subscription can have only one free database per region. To provision a…
- 45155 — A free database operation is already in progress for subscription '%ld'. Subscription can have only one free database per region. To provision another…
- 45156 — Subscription '%.*ls' is busy with another operation. Please try your operation later.
- 45157 — Server '%.*ls' is busy with another operation. Please try your operation later.
- 45158 — Cannot move server '%.*ls' from source subscription '%ls' to target subscription '%ls'. You can have only one free database per subscription. To conti…
- 45159 — Cannot move servers from source subscription '%ls' to target subscription '%ls' since both subscriptions have free databases. You can have only one fr…
- 45160 — Subscription '%ls' doesn't have any servers to move.
- 45161 — Managed instance '%.*ls' is busy with another operation. Please try your operation later.
- 45162 — Operation failed because subscription '%ls' is disabled.
- 45163 — Create Server request must either specify SQL login with password or denote admin login is a federated user by setting 'IsFederatedAdminLogin' propert…
- 45164 — Invalid number of database copies: '%d'. Only one database copy is currently allowed to be created along with the database creation.
- 45165 — Continuous copy is not supported on the free database '%.*ls'.
- 45166 — Database '%.*ls' was %.*ls successfully, but some properties could not be displayed.
- 45167 — An invalid state transition was attempted.
- 45168 — The server '%.*ls' has too many active connections. Try again later.
- 45169 — The subscription '%.*ls' has too many active connections. Try again later.
- 45170 — A trusted certificate was not found for this request.
- 45171 — Secondary database must be created in the same server as primary database unless 'IsContinuous' is specified.
- 45172 — The 'MaximumLag' parameter requires that 'IsContinuous' is specified.
- 45173 — Source server not found for subscription: %ls, resource group: %ls, server name: %ls.
- 45174 — Unable to queue server %ls for migration. There is a pending migration request for the server.
- 45175 — Unable to queue server %ls for migration. A migration is already in progress.
- 45176 — Unable to queue server %ls for migration. The server is using feature %ls that prevents it from being migrated.
- 45177 — Unable to queue server %ls for migration. Failed to find a target cluster for migration.
- 45178 — Database create mode '%ls' is not supported.
- 45179 — The operation timed out and automatically rolled back. Please retry the operation.
- 45180 — Resource with the name '%ls' already exists. To continue, specify a different resource name.
- 45181 — Resource with the name '%ls' does not exist. To continue, specify a valid resource name.
- 45182 — Database '%ls' is busy with another operation. Please try your operation later.
- 45183 — There is an import or export operation in progress on the database '%ls'.
- 45184 — Operation Id '%ls' was not found.
- 45185 — The change role completion notification for logical server '%.*ls', ag id '%ls', local database id '%ls' was ignored as freshness number did not match…
- 45186 — Database create mode '%ls' is not supported in state '%ls'.
- 45187 — The replication mode updated notification for logical server '%.*ls', ag id '%ls', local database id '%ls', partner database id '%ls' was ignored as c…
- 45188 — The operation has been cancelled by user.
- 45189 — Insufficient permission to add secondary on server '%ls'.
- 45190 — '%ls' is an invalid name because it contains one or more unsupported unicode characters.
- 45191 — The operation could not be completed because it would result in data loss on secondary database '%ls' on server '%ls.' Set the 'replace' parameter to …
- 45192 — The value specified for 'allow_connections' does not match the value for the existing replication relation for database '%ls' on server '%ls.'
- 45193 — Database '%ls' on server '%ls' is already the target in another replication relationship.
- 45194 — The operation could not be completed because it would result in target database '%ls' on server '%ls' having a lower service objective than source dat…
- 45195 — The operation could not be completed because database '%ls' on server '%ls' is the source in another replication relationship.
- 45196 — The operation on the resource could not be completed because it was interrupted by another operation on the same resource.
- 45197 — A system maintenance operation is in progress on server '%.*ls' and database '%.*ls.' Please wait a few minutes before trying again.
- 45198 — MODIFY LOG FILE failed. Size is greater than MAXSIZE.
- 45199 — This command requires a database encryption scan on database '%.*ls'. However, the database has changes from previous encryption scans that are pendin…
- 45200 — The server '%ls' are not associated with the tenant '%ls'.
- 45201 — SQL Server Agent service is not running.
- 45202 — Timed out after %ld seconds waiting for Smart Admin job to complete. Please run the stored procedure again.
- 45203 — The parameter @state cannot be NULL, and should be 1 or 0. Specify 1 to start SQL Server Managed Backup to Windows Azure, or 0 to pause.
- 45204 — The parameter %ls cannot be NULL or empty. Provide a valid %ls.
- 45205 — No backup setting is supplied. Please specify at least one backup setting to be configured.
- 45206 — The value specified for parameter @type is invalid. The @type parameter value should either be 'Database' or 'Log'.
- 45207 — %ls
- 45208 — SQL Server Managed Backup to Windows Azure master switch is not turned on.
- 45209 — The parameter value for notification email is not specified or is NULL. Please specify a valid email to enable notifications for Smart Admin.
- 45210 — Database Mail is not enabled for SQL Agent to use for Notifications. Enable Database Mail as the mail system for alerts.
- 45211 — Database mail profile is not setup for SQL Agent notifications.
- 45212 — The value specified for parameter %ls is invalid. Provide a valid %ls.
- 45213 — @full_backup_freq_type , @backup_begin_time , @backup_duration , and @log_backup_freq must be specified if @scheduling_option is set to 'Custom'
- 45214 — @days_of_week must be specified if @full_backup_freq_type is set to 'Weekly'
- 45215 — Local caching is not yet supported.
- 45216 — @full_backup_freq_type , @backup_begin_time , @backup_duration , and @log_backup_freq must not be specified if @scheduling_option is set to 'System'
- 45217 — @encryptor_type , and @encryptor_name must not be specified if @encryption_algorithm is set to 'NO_ENCRYPTION'
- 45218 — @encryptor_type , and @encryptor_name must be specified if @encryption_algorithm is not set to 'NO_ENCRYPTION'
- 45219 — @days_of_week must not be specified if @full_backup_freq_type is set to 'Daily'
- 45220 — An error occurred while configuring for the SQL Agent: error %d, severity %d, state %d.
- 45221 — An error occurred while configuring for the SQL Agent: error %d, severity %d, state %d.
- 45301 — The resource has been moved to another location
- 45302 — SLO '%ls' operation cannot succeed as the memory usage of '%ls' exceeds the quota.
- 45303 — Attempt to cancel activation or rollback activation automatically because of operation timeout, but this is not supported in current state. Please che…
- 45304 — Elastic pool estimate '%.*ls' was not found for server '%.*ls'
- 45305 — Request could not be processed because of conflict in the request: '%.*ls'
- 45306 — The external admin cannot be set because the user or group already exists in the 'master' database.
- 45307 — Advisor '%.*ls' was not found for requested resource
- 45308 — Recommended action '%.*ls' was not found for advisor '%.*ls'
- 45309 — The operation could not be completed because database '%ls' on server '%ls' is recovering from a geo-replication role change and is not currently elig…
- 45310 — Unable to return metrics. Request would return too much data.
- 45311 — The server key '%.*ls' already exists. Please choose a different server key name.
- 45312 — The server key URI '%.*ls' already exists as another server key.
- 45313 — The server key '%.*ls' cannot be deleted because it is currently in use by '%.*ls'.
- 45314 — Server key '%.*ls' does not exist. Make sure that the server key name is entered correctly.
- 45315 — The operation could not be completed because a service objective assignment is in progress for database '%.*ls' on server '%.*ls.' Wait for the servic…
- 45316 — MODIFY FILE failed. Size is greater than MAXSIZE. Please query sys.database_files and use DBCC SHRINKFILE to reduce the file size first.
- 45317 — Server '%.*ls' does not exist in resource group '%.*ls' in subscription '%.*ls'.
- 45318 — Service Fabric Application Version is not available.
- 45319 — The service objective assignment for database '%.*ls' on server '%.*ls' could not be completed as the database is too busy. Reduce the workload before…
- 45320 — The operation could not be completed on server '%.*ls' because the Azure Key Vault key '%.*ls' is disabled.
- 45321 — The operation could not be completed on server '%.*ls' because attempts to connect to Azure Key Vault '%.*ls' have failed
- 45322 — The operation could not be completed because the Azure Key Vault key '%.*ls' expiration date is invalid.
- 45323 — Unable to start a copy because the source database '%ls' is being updated.
- 45324 — The operation could not be completed because the Azure Key Vault Uri is null or empty.
- 45325 — The operation could not be completed because the Azure Key Vault Key name is null or empty.
- 45326 — The operation could not be completed because the Azure Key Vault Key name '%ls' does not exist.
- 45327 — The operation could not be completed because the Azure Key Vault Key name '%ls' is currently set as server encryption protector.
- 45328 — The server identity is not correctly configured on server '%ls'. Please contact support.
- 45329 — An invalid response from Azure Key Vault. Please use a valid Azure Key Vault URI.
- 45330 — The server '%ls' requires the following Azure Key Vault permisions: '%ls'. Please grant the missing permissions to the service principal with ID '%ls'…
- 45331 — The operation could not be completed because the read scale value specified is not supported for a '%ls' database.
- 45332 — The operation could not be completed because the read scale value specified is invalid.
- 45333 — The service request timed out. %ls.
- 45334 — Server edition '%ls' is invalid.
- 45335 — Server type '%ls' is invalid.
- 45336 — The operation could not be completed because '%ls' is an invalid Server Key name. Please provide a key name in the format of 'vault_key_version'. For …
- 45337 — The planned failover operation has rolled back because database '%ls' could not be synchronized with its remote partner. This may be due to a service …
- 45338 — The planned failover operation has rolled back because the remote server '%ls' could not be reached. This may be due to a service outage. Consider usi…
- 45339 — The max size update on the geo-secondary database '%ls' on server '%ls' failed with reason '%ls'.
- 45340 — The operation could not be completed because an Azure Active Directory error was encountered. The error message from Active Directory Authentication l…
- 45341 — The operation could not be completed because an error was encountered when attempting to retrieve Key Vault information for '%ls' from server '%ls'. T…
- 45342 — The operation could not be completed because an Azure Active Directory error was encountered. Please ensure the server '%ls' and key vault '%ls' belon…
- 45343 — The provided Key Vault uri '%ls' is not valid. Please ensure the uri contains the vault, key, and key version information. An example valid uri looks …
- 45344 — Catalog DB creation failed.
- 45345 — Cannot cancel database management operation '%ls' in the current state.
- 45346 — Subnet resource ID '%ls' is invalid. Please provide a correct resource Id for the target subnet.
- 45347 — LongTermRetentionBackup is enabled for server '%ls'. Move server cross subscription is not allowed.
- 45348 — LongTermRetentionBackup is enabled for server '%ls'. Move server cross resource group is not allowed.
- 45349 — The operation could not be completed because certificate rotation is in progress for server '%ls'.
- 45350 — MODIFY MAXSIZE failed. To reduce the database size, the database first needs to reclaim unused space by running DBCC SHRINKDATABASE. Note that this op…
- 45351 — MODIFY MAXSIZE failed. The requested database size is smaller than the amount of data storage used.
- 45352 — Create Managed Instance failed. Provided virtual network subnet is located in %ls, which is a different region than the one you are provisioning Manag…
- 45353 — This private cluster is associated with TR %ls. You specified TR %ls as a parameter.
- 45354 — Tenant ring %d already has positive placement weight set(%d) and can't be used for private cluster for subscription %ls. Please ensure that the ring i…
- 45355 — The storage account %ls is not valid or does not exist.
- 45356 — The storage account credentials are not valid.
- 45357 — Auditing cannot be configured on secondary databases.
- 45358 — Server auditing settings are being updated for server '%ls'. Please wait for the existing operation to complete.
- 45359 — Database name validation failed. The database name is not allowed because it contains trailing whitespace characters.
- 45360 — The operation could not be completed because app config deployment is in progress for the app '%ls'.
- 45361 — Invalid subnet address range (%ls). Address range has to be in CIDR format (IP/MASK) where IP is a valid IPv4 address and MASK is a number between 0 a…
- 45362 — The operation could not be completed because the Azure Key Vault principal certificate has expired. The error message from Active Directory Authentica…
- 45363 — Server automatic tuning settings from previous request have not propagated to all databases yet. Please try again in few minutes.
- 45364 — The operation could not be completed because database '%ls' on server '%ls' is currently unavailable. Try again later. If the problem persists, contac…
- 45365 — vCore value (%d) is not valid. Please specify a valid vCore value.
- 45366 — The retention days of %d is not a valid configuration. Valid backup retention in days must be between %d and %d.
- 45367 — Invalid virtual network configuration. This is not allowed: %ls.
- 45368 — The given rule ID: %s is invalid. You can find valid rule ids in scan results file.
- 45369 — No baseline is set for rule ID: %d. You should first set a baseline for this rule.
- 45370 — Vulnerability Assessment scan on the resource '%ls' is in progress. Please wait for the existing operation to complete.
- 45371 — Cannot cancel management operation '%ls' in the current state.%ls
- 45372 — Automatic tuning option '%.*ls' was not found for requested resource.
- 45373 — Automatic tuning is not supported for SQL Data Warehouse.
- 45374 — HardwareGeneration '%ls' is not valid. Please specify a valid HardwareGeneration value.
- 45375 — vCore value (%d) and HardwareGeneration '%ls' is not a valid combination. Please specify a valid vCore and HardwareGeneration value.
- 45376 — Managed Instance cannot be joined to a classic virtual network. Please provide a Resource Manager vnet to join.
- 45377 — The provided Key Vault uri '%ls' is not valid. Please ensure the key vault has been configured with soft-delete and purge protection. ( https://aka.ms…
- 45378 — geo-redundant-backup not supported for the current edition.
- 45379 — geo-redundant-backup value is not allowed to update
- 45380 — The edition %.*ls is not a valid edition. Edition cannot be changed by update.
- 45381 — SKU Name '%ls' is not valid. Please specify a valid SKU Name.
- 45382 — Read or write operations are not allowed on the storage account '%ls'.
- 45383 — The storage account '%ls' is disabled.
- 45384 — The encryption protectors for all servers linked by GeoDR must be in the same region as their respective servers. Please upload key '%ls' to a Key Vau…
- 45385 — Unexpected Key Vault region found in the response for Key Vault '%ls' associated with server '%ls'. Expected region: '%ls', Region receieved in respon…
- 45386 — The key vault provided '%ls' on server '%ls' uses unsupported RSA Key Size or Key Type. The supported RSA Key Size is 2048 and Key Type is RSA and RSA…
- 45387 — Invalid hardware generation. It isn't allowed to have both Gen4 and Gen5.
- 45388 — Target subnet has associated Network Security Group (NSG). Remove %ls. ( https://go.microsoft.com/fwlink/?linkid=871071 )
- 45389 — Target subnet has no associated Route Table. Associate Route Table with single User Defined Route (UDR): Name: default, Address prefix: 0.0.0.0/0, Nex…
- 45390 — Target subnet has associated Route Table with invalid configuration %ls. Associate Route Table with single User Defined Route (UDR): Name: default, Ad…
- 45391 — Invalid virtual network configuration %ls. Add Azure recursive resolver virtual IP address 168.63.129.16 at the end of your custom DNS list: %ls. ( ht…
- 45392 — SQL service endpoint is currently not allowed on Managed Instance. Remove SQL service endpoint from %ls. ( https://go.microsoft.com/fwlink/?linkid=871…
- 45393 — Target subnet is not empty. Remove all resources from %ls or use a different empty subnet. ( https://go.microsoft.com/fwlink/?linkid=871071 )
- 45394 — Virtual network for the target subnet is locked. Remove the lock from %ls. ( https://go.microsoft.com/fwlink/?linkid=871071 )
- 45395 — Gateway subnet cannot be used for deploying managed instance. Use a different empty subnet. ( https://go.microsoft.com/fwlink/?linkid=871071 )
- 45396 — Target subnet %ls does not exist. Use a different empty subnet. ( https://go.microsoft.com/fwlink/?linkid=871071 )
- 45397 — Managed Instance deployment failed due to conflict with the following network requirements: %ls. Information about the network requirements and how to…
- 45398 — The specified edition %ls is not consistent with the specified SKU %ls.
- 45399 — The specified license type %ls is not valid.
- 45400 — Invalid storage size: %ls GB. Storage size must be specified between %ls and %ls gigabytes, in increments of %ls GB.
- 45401 — Ring buildout '%ls' has no support for small VM roles, role: '%ls'.
- 45402 — Ring buildout '%ls' does not support multiple DB roles.
- 45403 — The operation could not be completed because a service tier change is in progress for managed instance '%.*ls.' Please wait for the operation in progr…
- 45404 — The operation failed because update SLO safety checks could not be completed. Details: '%ls'.
- 45405 — The operation failed because a long running transaction was found on the SQL instance. Please wait for the transaction to finish execution and try aga…
- 45406 — Provisioning of zone redundant database/pool is not supported for your current request.
- 45407 — The operation timed out and failed: '%ls'
- 45408 — Resource not found: '%ls'.
- 45409 — Network resource provider returned following error: '%ls'.
- 45410 — Network resource provider denied access: '%ls'.
- 45411 — Virtual network firewall rules are not currently supported on servers with failover groups configured with automatic failover policy. Please configure…
- 45412 — Failover Groups configured with an automatic failover policy are currently not supported on servers configured with virtual network firewall rules. Pl…
- 45413 — Only one Interface endpoint profile is allowed.
- 45414 — The instance collation cannot be changed on Managed Instance.
- 45415 — Creating secondary of secondary (a process known as chaining) is not supported when enabling Transparent Data Encryption using Azure Key Vault (BYOK).
- 45416 — Cannot create a Managed Instance with collation '%.*ls'. Please use collation 'SQL_Latin1_General_CP1_CI_AS' instead.
- 45417 — Vulnerability Assessment storage container path must be supplied
- 45418 — The operation failed because the SQL instance had high CPU usage of %.*f%%. The current threshold is %.*f%%. Please wait for it to go down and try aga…
- 45419 — The operation failed because the SQL instance had high log write rate of %.*f%%. The current threshold is %.*f%%. Please wait for it to go down and tr…
- 45420 — The operation failed because update elastic pool safety checks could not be completed. Details: '%ls'.
- 45421 — The operation failed because a long running transaction was found on the elastic pool. Please wait for the transaction to finish execution and try aga…
- 45422 — The operation failed because the elastic pool had high CPU usage of %.*f%%. The current threshold is %.*f%%. Please wait for it to go down and try aga…
- 45423 — The operation failed because the elastic pool had high log write rate of %.*f%%. The current threshold is %.*f%%. Please wait for it to go down and tr…
- 45424 — The operation could not be completed because %ls operation is in progress. Please wait for the operation in progress to complete and try again.
- 45425 — The operation could not be completed because total allocated storage size for General Purpose instance would exceed %ls. Please reduce the number of d…
- 45426 — The operation could not be completed because instance has configured geo replicated secondary instance.
- 45427 — Hardware generation of the source is '%.*ls' while that of the PITR target is '%.*ls'.
- 45428 — The operation has failed because you are attempting to deploy managed instance as a geo-replication secondary to the subnet '%.*ls' in which there alr…
- 45429 — The operation failed because it was issued on a custom maintenance window database. This is prohibited by default. Please try again with a switch to d…
- 45430 — The operation failed because it was issued on a custom maintenance window database outside of its maintenance window. Please try again within the next…
- 45431 — The operation failed because it was issued on a database during the default business hours in the region (%ls - %ls). Please try again once they end.
- 45432 — Invalid storage size: Storage size limit (%ls GB) is less that current storage used (%ls GB). Please specify higher storage size limit.
- 45433 — The specified family %ls is not consistent with the specified SKU %ls.
- 45434 — The point in time '%.*ls' for restoration can't be later than now.
- 45435 — The operation could not be completed. The requested sku update would cause the master server to have a larger max_connections value than its replica(s…
- 45436 — The operation could not be completed. The requested storage update would cause the master server to have a larger storage size than its replica(s).
- 45437 — The operation could not be completed. Replication is not enabled for the server.
- 45438 — The timezone cannot be changed on Managed Instance.
- 45439 — Cannot create a Managed Instance with timezone '%.*ls'. Please use timezone 'UTC' instead.
- 45440 — Cannot create a Managed Instance as there are not enough available ip addresses in the selected subnet.
- 45441 — Elastic server restore verification is not supported.
- 45442 — The operation failed because the requested update mode '%ls' did not match the chosen one '%ls'. Please try again later or use a different update mode…
- 45443 — Storage Auto Grow is not supported .
- 45444 — Provisioning of Zone Redundant server is not supported .
- 45445 — Storage Auto Grow is not supported for Primary and Replica Servers.
- 45446 — Geo Redundant Backup not supported for Zone Redundant Server.
- 45447 — Database cannot be paused because it is not supported on a '%ls' database.
- 45448 — Database with '%ls' feature cannot be paused. Operation failed for Logical Server '%.*ls', Database '%.*ls', ServiceLevelObjective '%.*ls'
- 45449 — The database is already paused. Server '%.*ls', Database '%.*ls', Paused Time '%.*ls'.
- 45450 — The database is already resumed. Server '%.*ls', Database '%.*ls'.
- 45451 — Database operation failed because database is paused. Server '%.*ls', Database '%.*ls'
- 45452 — Database operation failed because database is paused. Server '%.*ls', Database '%.*ls'
- 45453 — The operation failed due to throttling. Server '%.*ls', Database '%.*ls'
- 45454 — The operation failed because it is not supported on disabled database. Server '%.*ls', Database '%.*ls'
- 45455 — The operation failed because it is not supported on geo replicated databases. Logical Server '%.*ls', Database '%.*ls', ServiceLevelObjective '%.*ls'
- 45456 — The request failed because there is an ongoing '%.*ls' operation. Server '%.*ls', Database '%.*ls'.
- 45457 — The request failed because there is an ongoing migration on server '%.*ls', database '%.*ls'.
- 45458 — Chosen subnet is delegated and cannot be used for deploying managed instance. Remove delegation from subnet.
- 45459 — Chosen subnet has resource of different type.
- 45460 — Subscription '%.*ls' isn't enabled for a feature '%.*ls'.
- 45461 — Maintenance window parameters are not allowed in the instance update operation.
- 45462 — The specified maintenance window slot '%.*ls' isn't supported.
- 45463 — 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 t…
- 45464 — The operation is not allowed because the current geo-replication configuration does not allow this combination of %ls. Change the setting on the geo-r…
- 45465 — Managed Instance deployment failed due to conflict with the following error related to preparation of network intent policy: %ls. Information about th…
- 45466 — Long Term Retention is not supported : %ls
- 45467 — Long Term Retention policy is invalid : %ls
- 45468 — Cannot fetch SQL Managed Instance available timezones because the functionality is not supported..
- 45469 — The operation could not be completed because an Azure Active Directory error was encountered. The error message from Active Directory Authentication l…
- 45470 — Managed instance deletion failed since there are resource(s) preventing its deletion: %ls ( https://go.microsoft.com/fwlink/?linkid=2109712 ).
- 45471 — The server identity is incorrectly configured on server '%ls'. Follow steps in "Assign an Azure AD identity to your server" ( https://aka.ms/'%ls'byok…
- 45472 — The server '%ls' requires the following Azure Key Vault permissions: '%ls'. Please grant the missing permissions to the service principal with ID '%ls…
- 45473 — The provided Key Vault uri '%ls' is not valid. Please ensure the key vault has been configured with soft-delete and purge protection. ( https://aka.ms…
- 45474 — '%ls' server configuration does not support Data Encryption feature. For information about supported configurations please visit https://aka.ms/'%ls'b…
- 45475 — AAD login '%s' cannot be added because a non AAD login exists with the same name.
- 45476 — The operation could not be completed because managed instance %ls contains databases that are in the Inaccessible state. Please either drop inaccessib…
- 45477 — Changing the hardware generation to deprecated %ls generation is not possible.
- 45478 — '%ls'
- 45479 — Backup storage type parameter is not allowed in the instance update operation.
- 45480 — The Azure SQL Database Service Management API surface has been retired. Please update callers to the Resource Management API. For more information, se…
- 45481 — The login for '%ls' was not able to be provisioned on sql instance '%ls'
- 45482 — The login for '%ls' was not able to be dropped on sql instance '%ls', it is currently in state '%ls'
- 45483 — The login for '%ls' was not able to be dropped on sql instance '%ls', rollback of drop is not supported.
- 45484 — Configuring backup storage account type to '%s' failed during Database create or update.
- 45485 — Managed Instance%ls deployment failed as provided subnet '%ls' was not delegated to Microsoft.Sql/managedInstances. Information on how to set subnet d…
- 45486 — Submitted request could not be accepted as the maximum number of '%ls' concurrent management operations would be exceeded. Terminate some of the ongoi…
- 45487 — Vulnerability Assessment scan was canceled.
- 45488 — Vulnerability Assessment failed to read archived blob.
- 45489 — Vulnerability Assessment storage account is on VNET or have firewalls.
- 45490 — Vulnerability Assessment storage account type is unsupported.
- 45491 — Vulnerability Assessment Baseline file exceeds the size limit (10MB).
- 45492 — Vulnerability Assessment baseline file isn't in the right format.
- 45493 — The baseline received for Vulnerability Assessment is invalid
- 45494 — Unable to perform operation due to server '%.*ls' being in Inaccessible state. Please re-validate the Azure Key Vault Key ( https://aka.ms/'%ls'byokse…
- 45495 — Data Encryption is not supported in the selected region.
- 45496 — Infrastructure Encryption is not supported in the selected region.
- 45497 — '%ls' server configuration does not support Infrastructure Encryption.
- 45498 — The differential backup interval hours of %d is not a valid configuration. Valid differential backup interval must be %ls hours.
- 45499 — Unable to perform operation due to server being in Stopped state. Please start the server first before retrying.
- 45500 — Geo-Restore is not allowed for managed instances with LRS/ZRS backup storage account type.
- 45501 — Unable to perform operation due to server being in Upgrading state. Please wait the server to Ready before retrying.
- 45502 — Upgrade elastic server version to '%ls' failed: %s.
- 45503 — AKV host '%ls' is not resolvable from SQL, on server '%ls'.
- 45505 — Property with name zoneRedundant is specified but not supported in managed instance update operation. Please remove it from operation request and subm…
- 45506 — Property with name zoneRedundant is specified but not supported in managed instance create operation. Please remove it from operation request and subm…
- 45507 — The server in replication is not supported for stopping operation.
- 45508 — The requested storage account type of '%ls' is not supported for edition '%ls'.
- 45509 — Managed Instance Failover cannot be initiated. Automated backup needs to complete the first full backup for a new database. Please try again later.
- 45510 — A conflict request to change backup storage redundancy is still in progress.
- 45511 — The restored database is too large for '%s' edition. Select a target edition with sufficient storage for the allocated database size. After restore, p…
- 45512 — This managed instance cannot be deployed because its DNS-zone does not match the DNS-prefix of its intended virtual cluster for subnet '%.*ls'. Althou…
- 45513 — Native restore file number limit was exceeded. The limit for SQL Managed Instance GP service tier is '%d' files. The restore request was initiated wit…
- 45514 — Specified public maintenance configuration '%ls' for the database '%ls' conflicts with the maintenance configuration '%ls' of the elastic pool '%ls'
- 45515 — The requested partner managed server '%ls' could not be resolved.
- 45516 — The service objective assignment for the resource has failed: the requested maintenance configuration '%ls' is temporarily unavailable. Try again late…
- 45517 — Provided subnet cannot be used for deploying managed instance as it is not on allow list. Only subnets from allow list can be used.
- 45518 — Property with name DatabaseSurfaceAreaVersion cannot be changed from '%ls' to '%ls' because downgrade is not supported.
- 45519 — Property with name DatabaseSurfaceAreaVersion is specified but not available in managed instance update operation. Please remove it from operation req…
- 45520 — Property with name DatabaseSurfaceAreaVersion is specified but not available in managed instance create operation. Please remove it from operation req…
- 45521 — A user assigned managed identity must be specified when identity type is set to 'UserAssigned' or 'SystemAssigned,UserAssigned'. Please specify the us…
- 45522 — The primary user assigned managed identity '%ls' must be a part of the managed identities being assigned to the server '%ls' or already assigned to th…
- 45523 — 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.m…
- 45524 — ZoneRedundant feature is not supported for the selected service tier. For more details visit aka.ms/sqlmi-service-tier-characteristics.
- 45525 — Enabling zoneRedundant feature is not possible once managed instance is created. For more details visit aka.ms/sqlmi-high-availability.
- 45526 — Disabling zoneRedundant feature is not possible once managed instance is created. For more details visit aka.ms/sqlmi-high-availability.
- 45527 — The operation %ls cannot be completed for the instance that has an active %ls configured.
- 45528 — The ImportExport operation with Request Id '%ls' failed due to '%ls'.
- 45529 — You have reached the maximum number of %ls active user certificates for the hybrid link. Please reduce the number of active certificates and try again…
- 45530 — The operation was not allowed because of the outbound firewall rule configuration for '%ls'.
- 45531 — The specified server name cannot be used. Name is available, but still present in the collection due to recent usage. It can take up to 7 days to remo…
- 45532 — The managed identity with ID '%ls' requires the following Azure Key Vault permissions: '%ls' on the key '%ls'. Grant the missing permissions to the id…
- 45533 — A primary user assigned managed identity has not been specified. Please specify the primary managed identity that you would like to use for the server…
- 45534 — Changing managed instance subnet is not supported operation. Please remove this parameter from the request.
- 45535 — Selected subnet is in another Virtual Network. Moving managed instance to another Virtual Network is not possible. Please provide subnet from Virtual …
- 45536 — Provided subnet is having different DNS zone from the current. Changing instance DNS zone is not supported. Please provide subnet with same DNS zone, …
- 45537 — It is not possible to update subnet while running on Gen4 hardware as it is being deprecated. Please upgrade your hardware from Gen4 to Gen5 as part o…
- 45538 — Specify the primary user-assigned managed identity having the following Azure Key Vault permissions '%ls' to access the key '%ls'. Ensure the key is n…
- 45539 — Change identity type to 'UserAssigned' or 'SystemAssigned,UserAssigned' and assign a primary user-assigned managed identity having the following Azure…
- 45540 — Cross '%ls' '%ls' operation is not supported.
- 45541 — No restore point available
- 45542 — User attempted to failover or force-terminate a geo-link while the secondary is in checkpoint-only mode due to insufficient memory and so cannot enter…
- 45543 — The source database of a named replica cannot itself be a named replica.
- 45544 — The operation cannot be performed since the database '%ls' is a named replica.
- 45545 — A named replica must be created in the same subscription and region as the source database.
- 45546 — Backup blob copy failed with exception '{0}'
- 45547 — The create operation has timed out in one of the backend workflows. Please retry the operation.
- 45548 — The operation could not be completed because some of the database files are exceeding General Purpose file size limit of %ls GB.
- 45549 — The backup storage redundancy type selected cannot be used with data in zone-redundant storage. When data is in zone-redundant storage, you can only b…
- 45550 — Database movement of database '{0}' from managed server '{1}' does not exist.
- 45551 — Only one user assigned managed identity is supported at the Database Level.
- 45552 — A user assigned managed identity must be specified when identity type is set to 'UserAssigned'. Please specify the user assigned managed identity to b…
- 45553 — Only one identity delegation is supported at the Database Level.
- 45554 — User assigned managed identities are not supported on 'master', 'model', 'tempdb', 'msdb', or 'resource' databases.
- 45555 — Identity delegations are not supported on 'master', 'model', 'tempdb', 'msdb', or 'resource' databases.
- 45556 — Updating identities is not supported on this resource type.
- 45557 — %ls from the %ls service tier to the %ls service tier are not supported.
- 45558 — Operation cannot be executed as instance is in stopping/stopped state. Please start your instance and submit the request again.
- 45559 — Operation cannot be executed as instance is in starting state. Please wait for start operation to complete then try again.
- 45560 — You cannot start instance that is already started or in starting state.
- 45561 — You cannot stop instance that is already stopped or in stopping state.
- 45562 — You cannot stop the instance that has running operation on an instance or on one or more of its databases. Please wait for ongoing operation to finish…
- 45563 — Stop operation failed because it was interrupted with instance delete operation.
- 45564 — 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…
- 45565 — It is not possible to stop the instance that is part of the failover group. Refer to the following article for limits of managed instance start/stop f…
- 45566 — One or multiple schedule items are missing start and/or stop value. Schedule items must have all values populated. Please correct your schedule and su…
- 45567 — One or multiple schedule items have a time span overlap. Please correct your schedule and submit again.
- 45568 — A time span between two successive actions must be at least 1 hour. Please correct your schedule and submit again.
- 45569 — Managed instance '%.*ls' does not have start/stop schedule configured.
- 45570 — No managed service identities are associated with resource %ls.
- 45571 — Resource identifier internal_id %ls is invalid.
- 45572 — The restore operation of a CRM database failed because a required TDE certificate was missing. Please retry the restore operation to an existing elast…
- 45573 — The backup storage redundancy type selected cannot be used with data stored in zone-redundant storage. When data is in zone-redundant storage, you can…
- 45574 — SQL Managed Instance cannot update the instance zone redundancy because the storage redundancy type is still updating. Complete these updates first, a…
- 45575 — SQL Managed Instance cannot update the instance zone redundancy and the backup storage redundancy for the same managed instance at the same time. Veri…
- 45576 — The managed instance cannot be updated to a multi-availability zone because the backup storage redundancy must be either zone or geo-zone redundant. U…
- 45577 — SQL Managed Instance cannot complete the requested operation because another operation is in progress. Wait for the operation to complete and then try…
- 45578 — The backup redundancy request cannot start because the update is already in progress.
- 45579 — Failed to update the backup storage. Contact Microsoft Support for assistance.