错误码目录 / Microsoft SQL Server
Microsoft SQL Server 错误码目录 · 第 15 / 18 页
本页收录 Microsoft SQL Server 的 17,993 条错误码知识条目,每条均可打开独立详情页,包含错误说明、编号信息、官方文档与公开资料。
- 33325 — Failed to construct new endpoint after redirection
- 33326 — Forwarder disconnected during redirection
- 33327 — Failed to parse the specified connection string
- 33328 — Redirector lookup failed with error code: %x
- 33329 — XdbHost encountered error code: %x during socket duplication
- 33330 — XdbHost returned an error during socket duplication
- 33331 — DBCC CLEANUPCONVERSATIONS is not allowed on this server.
- 33332 — DBCC CLEANUPCONVERSATIONS cannot be executed through MARS connection.
- 33333 — The connection had a send posted for over %d seconds. The connection is suspected hung and is being closed.
- 33334 — Error while setting up ssl channel. Error code: (%d, %d, %d)
- 33335 — The connection has been flow controlled in the %d seconds (%d times, where threshold is %d). Min required transfer rate is %d Kbps. Actual transfer ra…
- 33336 — The connection has been flow controlled in the last %d seconds for a period of %d seconds. The connection is extensively flow controlled and is being …
- 33337 — SQL MI SSB Dialog Timer delete action occurred during dispatch or registration.
- 33338 — UCS transport default sending capacity is overridden with the value of %d. Override source: %.*ls. This is an informational message only. No user acti…
- 33339 — The message type may not be NULL. A variable containing a valid message type name is allowed.
- 33401 — FILESTREAM database options cannot be set on system databases such as '%.*ls'.
- 33402 — An invalid directory name '%.*ls' was specified. Use a valid operating system directory name.
- 33403 — The case-sensitive or binary collation '%.*ls' cannot be used with the COLLATE_FILENAME option. Change the collation to a case-insensitive collation t…
- 33404 — The database default collation '%.*ls' is case sensitive and cannot be used to create a FileTable. Specify a case insensitive collation with the COLLA…
- 33405 — An error occurred during the %S_MSG %S_MSG operation on a FileTable object. (HRESULT = '0x%08x').
- 33406 — An invalid filename, '%.*ls', caused a FileTable check constraint error. Use a valid operating system filename.
- 33407 — An invalid path locator caused a FileTable check constraint error. The path locator cannot indicate a root row. Correct the path locator or use the de…
- 33408 — The operation caused a FileTable check constraint error. A directory entry cannot have a data stream associated with the row. Remove the blob data or …
- 33409 — The operation caused a FileTable check constraint error. A file entry cannot have a NULL value for the data stream associated with the row. Insert fil…
- 33410 — An invalid path locator caused a FileTable check constraint error. The parent of a row's path locator must be a directory, not a file. Correct the pat…
- 33411 — The option '%.*ls' is only valid when used on a FileTable. Remove the option from the statement.
- 33412 — The option '%.*ls' is not valid when used with the '%.*ls' syntax. Remove the option from the statement.
- 33413 — The option '%.*ls' can only be specified once in a statement. Remove the duplicate option from the statement.
- 33414 — FileTable objects require the FILESTREAM database option DIRECTORY_NAME to be non-NULL. To create a FileTable in the database '%.*ls', set the DIRECTO…
- 33415 — FILESTREAM DIRECTORY_NAME '%.*s' attempting to be set on database '%.*s' is not unique in this SQL Server instance. Provide a unique value for the dat…
- 33416 — When the FILESTREAM database option NON_TRANSACTED_ACCESS is set to FULL and the READ_COMMITTED_SNAPSHOT or the ALLOW_SNAPSHOT_ISOLATION options are o…
- 33417 — An invalid path locator caused a FileTable check constraint error. The path locator has a level of %d, which is deeper than the limit of %d supported …
- 33418 — FILETABLE_DIRECTORY '%.*s' attempting to be set on table '%.*s' is not unique in the database '%.*s'. Provide a unique value for the option FILETABLE_…
- 33419 — Function %ls is only valid on the varbinary(max) FILESTREAM column in a FileTable.
- 33420 — Unable to process object '%.*s' because it is a three-part or four-part name. Specifying the server or database is not supported in the object identif…
- 33421 — The object name '%.*s' is not a valid FileTable object.
- 33422 — The column '%.*s' cannot be added to table '%.*s' as it is a FileTable. Adding columns to the fixed schema of a FileTable object is not permitted.
- 33423 — Invalid FileTable path name or format.
- 33424 — Invalid computer host name in the FileTable path.
- 33425 — Invalid share name in the FileTable path.
- 33426 — INSERT, UPDATE, DELETE, or MERGE to FileTable '%.*ls' is not allowed inside a trigger on a FileTable.
- 33427 — Function %ls is not allowed on the deleted table inside a trigger.
- 33428 — User does not have permission to kill non-transacted FILESTREAM handles in database ID %d.
- 33429 — The non-transacted FILESTREAM handle %d does not exist.
- 33430 — Killed %d non-transactional FILESTREAM handles from database ID %d.
- 33431 — An invalid path locator caused a FileTable check constraint error. The path locator has a length of %d, which is longer than the limit of %d allowed f…
- 33433 — Unable to perform the Filetable lost update recovery for database id %d.
- 33434 — The current state of the database '%.*s' is not compatible with the specified FILESTREAM non-transacted access level. The database may be read only, s…
- 33435 — Cannot publish the FileTable '%ls' for replication. Replication is not supported for FileTable objects.
- 33436 — Cannot enable Change Data Capture on the FileTable '%ls'. Change Data Capture is not supported for FileTable objects.
- 33437 — Cannot publish the logbased view '%ls' for replication. Replication is not supported for logbased views that depend on FileTable objects.
- 33438 — Cannot enable Change Tracking on the FileTable '%.*ls'. Change Tracking is not supported for FileTable objects.
- 33439 — Cannot use IGNORE_CONSTRAINTS hint when inserting into FileTable '%.*ls', unless FILETABLE_NAMESPACE is disabled.
- 33440 — When inserting into FileTable '%.*ls' using BCP or BULK INSERT, either CHECK_CONSTRAINTS option needs to be on, or FILETABLE_NAMESPACE needs to be dis…
- 33441 — The FileTable '%.*s' cannot be partitioned. Partitioning is not supported on FileTable objects.
- 33442 — The handle ID %d is opened against the server root share and cannot be killed. The lifetime of the handle is controlled by the client who originally o…
- 33443 — The database '%.*s' cannot be enabled for both FILESTREAM non-transacted access and Database Mirroring.
- 33444 — The database '%.*s' cannot be enabled for both FILESTREAM non-transacted access and HADR.
- 33445 — The database '%.*s' is a readable secondary database in an availability group and cannot be enabled for FILESTREAM non-transacted access.
- 33446 — The FILESTREAM database configuration cannot be changed for database '%.*s'. The database is either a mirror database in Database Mirroring, or is in …
- 33447 — Cannot access file_stream column in FileTable '%.*ls', because FileTable doesn't support row versioning. Either set transaction level to something oth…
- 33448 — Cannot disable clustered index '%.*ls' on FileTable '%.*ls' because the FILETABLE_NAMESPACE is enabled.
- 33449 — FILESTREAM File I/O access is enabled, but no listener for the availability group is created. A FILESTREAM PathName will be unable to refer to a virtu…
- 33450 — FILESTREAM File I/O access is enabled. One or more availability groups ('%ls') currently do not have a listener. A FILESTREAM PathName will be unable …
- 33451 — Cannot enable Change Feed on the FileTable '%ls'. Change Feed is not supported for FileTable objects.
- 33501 — Security predicates cannot be added on tables that contain filestream data. Column '%.*ls' on table '%.*ls' contains filestream data.
- 33502 — The column '%.*ls' could not be added to table '%.*ls' because the column contains filestream data and the table is referenced by one or more security…
- 33503 — BLOCK predicates can only be added to user tables. '%.*ls' is not a user table.
- 33504 — The attempted operation failed because the target object '%.*ls' has a block predicate that conflicts with this operation. If the operation is perform…
- 33505 — Partitioned view '%.*ls' is not updatable because table '%.*ls' has an enabled security policy that defines block predicates for this table.
- 33506 — Only natively compiled inline table-valued functions can be used for security predicates on memory optimized tables. Table '%.*ls' is memory optimized…
- 33507 — Function '%ls' cannot be used in the definition of BLOCK security predicates. Modify the BLOCK security predicates for this table or view to not use t…
- 33508 — Column '%.*ls' cannot be passed as a parameter for a BLOCK security predicate because the column definition contains an expression using a window func…
- 33509 — Column '%.*ls' cannot be passed as a parameter for an AFTER UPDATE or AFTER INSERT BLOCK security predicate for this view because it refers to a base …
- 33510 — BLOCK security predicates cannot reference temporal history tables. Table '%.*ls' is a temporal history table.
- 33511 — Table '%.*ls' is memory optimized. Only security policies with schema binding enabled may specify security predicates for memory optimized tables. Cre…
- 33512 — Binding for the non-schema bound security predicate on object '%.*ls' failed with one or more errors, indicating the schema of the predicate function …
- 33513 — Binding for the non-schema bound security predicate on object '%.*ls' failed, because the predicate function is not an inline table-valued function. O…
- 33514 — Incorrect parameter encryption metadata was received from the client. The error occurred during the invocation of the batch and therefore the client c…
- 33515 — The parameter "%.*ls" does not have the same encryption information as the one it was created with. Use sp_refresh_parameter_encryption to refresh the…
- 33516 — The object '%.*ls' is referenced by the security policy '%.*ls'. The currently installed edition of SQL Server does not support security policies. Eit…
- 33517 — The column '%.*ls' of the object '%.*ls' is encrypted. The currently installed edition of SQL Server does not support encrypted columns. Either remove…
- 33518 — Valid values of the database compatibility level are %d, %d, %d, or %d.
- 33519 — An external data source conflicting with '%.*ls' already exists in EDS cache in memory. Use alter step to change the location or credential. Drop and …
- 33520 — Failed to allocate memory for caching external data source '%.*ls' which is used by a database file.
- 33521 — Cannot drop the external data source '%.*ls' because it is being used.
- 33522 — Cannot remove the external data source '%.*ls' because it is being used.
- 33523 — Cryptographic failure due to insufficient memory.
- 33524 — The fn_get_audit_file function is skipping records from '%.*ls'. You must be connected to database '%.*ls' to access its audit logs.
- 33525 — The fn_get_audit_file function is skipping records from '%.*ls'. You must be connected to server '%.*ls' to access its audit logs.
- 33526 — The fn_get_audit_file function is skipping records from '%.*ls', as it does not conform to the auditing blob naming convention.
- 33527 — Error occured while initializing the security functions lookup table. This might be because the installation of SQL Server is corrupted and a required…
- 33528 — Valid values of the database compatibility level are %d, %d, %d, or %d.
- 33529 — The audit filter predicate exceeds the maximum allowed length of %d characters.
- 33530 — The combined length of audit name and blob storage container name exceeds the maximum allowed length (by %d character(s)). Please use shorter audit or…
- 33531 — The specified value for QUEUE_DELAY is not valid with asynchronous log target. Specify value higher than 0.
- 33532 — Invalid value given for parameter PATH. Please specify a valid blob container path with the following format : https://<storageName>.blob.core.windows…
- 33533 — SHUTDOWN on failure option is not supported in this version of SQL Server.
- 33534 — Internal enclave error. Enclave loading failed: invalid path. For more information, contact Customer Support Services.
- 33535 — Internal enclave error: Enclave call failed for method '%s'. For more information, contact Customer Support Services.
- 33536 — VBS enclave attestation failed. Attestation status: '%ls', substatus: '%ls'. For more information, see ' https://go.microsoft.com/fwlink/?linkid=20995…
- 33537 — Internal enclave error. Enclave attestation error: enclave platform returned unexpected output. For more information, contact Customer Support Service…
- 33538 — The credentials of blob storage container '%.*ls' are invalid.
- 33539 — The blob storage '%.*ls' was not found. Verify your storage account name.
- 33540 — Invalid audit or database names, please use valid URL characters.
- 33541 — The credentials of blob storage container '%.*ls' was not found.
- 33542 — Unsupported operation near line '%d'; operations on encrypted columns with string data types require a *_BIN2 collation. However, the column or the va…
- 33543 — Cannot alter column '%.*ls'. The statement attempts to encrypt, decrypt or re-encrypt the column in-place using a secure enclave, but the current and/…
- 33544 — Cannot alter column '%.*ls'. The statement attempts to change the encryption scheme of the column and one or more of the following column properties: …
- 33545 — The statement requires a secure enclave, but the enclave has not been initialized in the SQL Server instance. Check the status of the enclave in sys.c…
- 33546 — The statement triggers enclave computations, but a column encryption key, needed for the computations, has not been found inside the enclave. Check th…
- 33547 — Enclave comparator cache failed to initialize during enclave load.
- 33548 — Internal enclave error: Enclave out of memory. For more information, contact Customer Support Services.
- 33549 — Internal enclave error: OSF Serialization error. For more information, contact Customer Support Services.
- 33550 — Internal enclave error: Invalid data format. For more information, contact Customer Support Services.
- 33551 — Internal enclave error: Nonce checking in secure channel failed. For more information, contact Customer Support Services.
- 33552 — Internal enclave error. Enclave shutdown due to a critical error. For more information, contact Customer Support Services.
- 33553 — A failure occurred during initialization of an Audit to External Monitor target. See the errorlog for details.
- 33554 — Encountered error 0x%08lx while waiting for encryption scan completion consensus. See the errorlog for details.
- 33555 — Unable to find the user-specified certificate [Cert Hash(sha1) "%hs"] in the certificate store of the local computer. Please verify that certificate e…
- 33556 — Invalid character in the thumbprint [Cert Hash(sha1) "%hs"]. Please provide a certificate with a valid thumbprint.
- 33557 — Invalid thumbprint length [Cert Hash(sha1) "%hs"]. Please provide a certificate with a valid thumbprint.
- 33558 — Encryption scan can not be resumed because no encryption scan is in progress.
- 33559 — Specified workload group does not exist. Retry with a valid workload group.
- 33560 — TDE scan for database id [%d] was initiated on %S_DATE (UTC). The encryption scan will resume soon.
- 33561 — Encryption scan can not be suspended because no encryption scan is in progress.
- 33562 — TDE encryption scan state cannot be updated for database id [%d].
- 33563 — TDE scan for database id [%d] was aborted on %S_DATE (UTC). The encryption scan will resume soon.
- 33564 — TDE scan for database id [%d] was suspended on %S_DATE (UTC). To resume scan, run "ALTER DATABASE [%.*s] SET ENCRYPTION RESUME".
- 33565 — Found the certificate [Cert Hash(sha1) "%hs"] in the %S_MSG store but the SQL Server service account does not have access to it.
- 33566 — Found the certificate [Cert Hash(sha1) "%hs"] in the %S_MSG store but it does not have a private key. Please verify and use a valid certificate.
- 33567 — Column '%.*ls.%.*ls' is encrypted using a randomized encryption type and is therefore not valid for use as a key column in a clustered index, constrai…
- 33568 — Internal enclave error: Structured exception within the enclave with status %d. For more information, contact Customer Support Services.
- 33569 — Column '%.*ls.%.*ls' is encrypted using a randomized encryption type using a non *_BIN2 collation and is therefore not valid for use as a key column i…
- 33570 — Specified workload group does not exist. Switching to default workload group for TDE encryption scan.
- 33571 — Cannot create server audit with GUID '%s' in this version of SQL Server: Please specify another GUID value.
- 33572 — Encrypted index recovery: %ls %d
- 33573 — Column '%.*ls.%.*ls' is encrypted using randomized encryption with a non enclave-enabled column encryption key and is therefore not valid for use as a…
- 33574 — Specifying a private key file or binary is not allowed when importing or exporting a certificate using the PFX format.
- 33575 — WITH PRIVATE KEY must be specified when importing or exporting a certificate using the PFX format.
- 33576 — Invalid certificate encoding FORMAT value provided. The supported values are 'DER' and 'PFX'.
- 33577 — The specified PFX file or the binary literal cannot be imported as it contains multiple certificates.
- 33578 — The specified file or the binary literal is not supported as it does not contain a private key.
- 33579 — Cannot drop a value for the column encryption key '%.*ls'; dropping the value makes the key enclave disabled, and one or more objects that are schema-…
- 33580 — Operation supported by enclaves invoked on data encrypted with randomized encryption where the keys are not enclave-enabled. Please clear the proc cac…
- 33581 — Cannot alter column '%.*ls'. The statement attempts to encrypt, decrypt or re-encrypt the column in-place using a secure enclave, but this is not supp…
- 33582 — Cannot create the module. Executing the module requires keys in a secure enclave, but this is not supported for memory-optimized tables.
- 33583 — Could not find Azure AD principal mapping to Windows principal '%ls'.
- 33584 — Found multiple Azure AD principals mapping to Windows principal '%ls'.
- 33585 — Windows principal '%ls' does not map to provided Azure AD principal '%ls', please use a different Azure AD principal.
- 33586 — Warning: Index '%.*ls.%.*ls' has an enclave-enabled key column, however Accelerated Database Recovery is not enabled for database '%.*ls'. Enabling it…
- 33587 — Security predicates cannot be added to external table '%.*ls' because it does not contain a credential.
- 33588 — Invalid encryption algorithm. Always Encrypted with secure enclaves requires data to be encrypted with the AEAD_AES_256_CBC_HMAC_SHA_256 algorithm.
- 33589 — Internal enclave error. Enclave was provided with an invalid expression handle. For more information, contact Customer Support Services.
- 33590 — Database encryption scan for database '%.*ls' was suspended. Reissue ALTER DB to resume the scan.
- 33591 — ALGORITHM has an invalid value. The allowed values are '%ls', '%ls'.
- 33592 — The underlying operating system does not support encrypting private keys using '%ls'. Consider using '%ls'.
- 33593 — Specifying ALGORITHM is not allowed when exporting a certificate using the DER format.
- 33594 — ALGORITHM must be specified when exporting a certificate using the PFX format. The supported algorithms are '%ls', '%ls'.
- 33595 — The session context key '%s' is too long. Maximum allowed length of session context key is %d characters.
- 33596 — Maximum number of session context keys used for audit specification has been exceeded. The maximum allowed number of keys is %d.
- 33597 — Operator Audit option is not supported for this target type, use EXTERNAL_MONITOR target.
- 33598 — The private key password is invalid, or the file was encrypted with an algorithm not supported by the underlying operating system.
- 33599 — Valid values of the database compatibility level are %d, %d, %d, %d, %d, or %d.
- 33801 — Cannot bulk load file split because either secret or file_properties option is missing.
- 33802 — Trident DW BCP failed due to an internal error.
- 34001 — Dialog with queue 'syspolicy_event_queue' has encountered an error: %s.
- 34002 — Dialog with queue 'syspolicy_event_queue' has ended.
- 34003 — Error number %d was encountered while processing an event. The error message is: %s.
- 34004 — Execution mode %d is not a valid execution mode.
- 34010 — %s '%s' already exists in the database.
- 34011 — Specified value for property %s cannot be used with execution mode %d.
- 34012 — Cannot delete %s referenced by a %s.
- 34013 — %s '%s' is referenced by a '%s'. Cannot add another reference.
- 34014 — Facet does not exist.
- 34015 — Policy group %s does not exist.
- 34016 — Invalid target filer: %s. Only filters that restrict the first level below the Server node are allowed.
- 34017 — Automated policies cannot reference conditions that contain script.
- 34018 — Target type "%s" is not a valid target type.
- 34019 — Object "%s" is invalid.
- 34020 — Configuration option "%s" is unknown.
- 34021 — Invalid value type for configuration option "%s". Expecting "%s".
- 34022 — Policy automation is turned off.
- 34050 — %ls
- 34051 — %ls
- 34052 — %ls
- 34053 — %ls
- 34054 — Policy Management cannot be enabled on this edition of SQL Server.
- 34101 — An error was encountered during object serialization operation. Examine the state to find out more details about this error.
- 34102 — An object in serialized stream has version %u but maximum supported version of this class is %u.
- 34103 — Error in formatter during serialize/deserialize. Required to process %d elements but processed only %d elements.
- 34104 — An error was encountered during object serialization operation. The object that failed serialization is %hs.
- 34901 — The global lock manager encountered a severe failure.
- 35001 — Parent Server Group does not exist.
- 35002 — Server type and parent Server Group type are not the same
- 35003 — Cannot move node to one of its children
- 35004 — Could not find server group
- 35005 — An invalid value NULL was passed in for @server_group_id .
- 35006 — An invalid value NULL was passed in for @server_id .
- 35007 — Could not find shared registered server.
- 35008 — Cannot delete system shared server groups.
- 35009 — An invalid value NULL was passed in for @server_type .
- 35010 — An invalid value %d was passed in for parameter @server_type .
- 35011 — The @server_name parameter cannot be a relative name.
- 35012 — You cannot add a shared registered server with the same name as the Configuration Server.
- 35100 — Error number %d in the THROW statement is outside the valid range. Specify an error number in the valid range of 50000 to 2147483647.
- 35101 — One of the SET options FMTONLY or NOEXEC was changes from ON to OFF in a TRY...CATCH block.
- 35102 — Error related to '%ls' where one of participants is Azure SQL Managed Instance.
- 35103 — '%ls' feature where one of participants is Azure SQL Managed Instance is disabled.
- 35104 — Deprecated feature '%ls' with Azure SQL Managed Instance as a participant is not supported in this version of SQL Server.
- 35200 — Failed to add database '%.*ls' to availability group '%.*ls'. The specified availability group is created with basic functionality and supports %d dat…
- 35201 — A connection timeout has occurred while attempting to establish a connection to availability replica '%ls' with id [%ls]. Either a networking or firew…
- 35202 — A connection for availability group '%ls' from availability replica '%ls' with id [%ls] to '%ls' with id [%ls] has been successfully established. This…
- 35203 — Unable to establish a connection between instance '%ls' with id [%ls] and '%ls' with id [%ls] due to a transport version mismatch.
- 35204 — The connection between server instances '%ls' with id [%ls] and '%ls' with id [%ls] has been disabled because the database mirroring endpoint was eith…
- 35205 — Could not start the Always On Availability Groups transport manager. This failure probably occurred because a low memory condition existed when the me…
- 35206 — A connection timeout has occurred on a previously established connection to availability replica '%ls' with id [%ls]. Either a networking or a firewal…
- 35207 — Connection attempt on availability group id '%ls' from replica id '%ls' to replica id '%ls' failed because of error %d, severity %d, state %d.
- 35208 — Availability-group DDL operations are permitted only when you are using the master database. Run the USE MASTER command, and retry your availability-g…
- 35209 — The %ls operation failed for availability replica '%.*ls', because the backup priority value is outside the valid range. The valid range is between %d…
- 35210 — Failed to modify options for availability replica '%.*ls' in availability group '%.*ls'. The specified availability group does not contain an availabi…
- 35211 — The %ls operation is not allowed. The operation attempted to change the configuration of availability replica '%.*ls' to the asynchronous-commit avail…
- 35212 — The %ls operation is not allowed by the current availability-group configuration. This operation would exceed the maximum number of %d synchronous-com…
- 35213 — The %ls operation is not allowed by the current availability-group configuration. This operation would exceed the maximum number of %d automatic failo…
- 35214 — The %ls operation failed for availability replica '%.*ls'. The minimum value for session timeout is %d. Retry the operation specifying a valid session…
- 35215 — The %ls operation is not allowed on availability replica '%.*ls', because automatic failover mode is an invalid configuration on a SQL Server Failover…
- 35216 — An error occurred while adding or removing a log truncation holdup to build secondary replica from primary availability database '%.*ls'. Primary data…
- 35217 — The thread pool for Always On Availability Groups was unable to start a new worker thread because there are not enough available worker threads. This …
- 35218 — An error occurred while trying to set the initial Backup LSN of database '%.*ls'. Primary database is temporarily offline due to restart or other tran…
- 35220 — Could not process the operation. Always On Availability Groups replica manager is waiting for the host computer to start a Windows Server Failover Clu…
- 35221 — Could not process the operation. Always On Availability Groups replica manager is disabled on this instance of SQL Server. Enable Always On Availabili…
- 35222 — Could not process the operation. Always On Availability Groups does not have permissions to access the Windows Server Failover Clustering (WSFC) clust…
- 35223 — Cannot add %d availability replica(s) to availability group '%.*ls'. The availability group already contains %d replica(s), and the maximum number of …
- 35224 — Could not process the operation. Always On Availability Groups failed to load the required Windows Server Failover Clustering (WSFC) library. Verify t…
- 35225 — Could not process the operation. The instance of SQL Server is running under WOW64 (Windows 32-bit on Windows 64-bit), which does not support Always O…
- 35226 — Could not process the operation. Always On Availability Groups has not started because the instance of SQL Server is not running as a service. Restart…
- 35228 — The attempt to set the failure condition level for availability group '%.*ls' failed. The specified level value is out of the valid range [%u, %u]. Re…
- 35229 — The attempt to set the health check timeout value for availability group '%.*ls' failed. The specified timeout value is less than %u milliseconds. Ree…
- 35230 — The specified computer name is either an empty string or is longer than %d Unicode characters. Reenter the command specifying a valid computer name.
- 35231 — The specified server instance name, '%ls', is invalid. Reenter the command specifying a valid instance name.
- 35232 — The specified endpoint URL '%.*ls' is invalid. Reenter the command specifying the correct URL. For information about specifying the endpoint URL for a…
- 35233 — Cannot create an availability group containing %d availability replica(s). The maximum number of availability replicas in an availability group %ls is…
- 35234 — Database name '%ls' was specified more than once. Reenter the command, specifying each database name only once.
- 35235 — The system name '%ls' was specified more than once in the REPLICA ON clause of this command. Reenter the command, specifying a different instance of S…
- 35236 — The endpoint URL was not specified for the availability replica hosted by server instance '%.*ls'. Reenter the command, specifying the endpoint URL of…
- 35237 — None of the specified replicas for availability group %.*ls maps to the instance of SQL Server to which you are connected. Reenter the command, specif…
- 35238 — Database '%.*ls' cannot be added to availability group '%.*ls'. The database does not exist on this SQL Server instance. Verify that the database name…
- 35239 — The ALTER DATABASE <database-name> SET HADR SUSPEND (or SET HADR RESUME) statement failed on database '%.*ls' of availability group '%.*ls''. Either t…
- 35240 — Database '%.*ls' cannot be joined to or unjoined from availability group '%.*ls'. This operation is not supported on the primary replica of the availa…
- 35242 — Cannot complete this ALTER DATABASE <database-name> SET HADR operation on database '%.*ls'. The database is not joined to an availability group. After…
- 35243 — Failed to set resource property '%.*ls' for availability group '%.*ls'. The operation encountered SQL Server error %d. When the cause of the error has…
- 35244 — Database '%.*ls' cannot be added to availability group '%.*ls'. The database is currently joined to another availability group. Verify that the databa…
- 35246 — Failed to create the availability group. A SQL Server instance name could not be validated because the dynamic link library (DLL) file '%ls' could not…
- 35247 — Failed to create the availability group. A SQL Server instance name could not be validated because the dynamic link library (DLL) file '%ls' could not…
- 35248 — The %ls operation is not allowed by the current availability-group configuration. The required_synchronized_secondaries_to_commit %d is greater than t…
- 35249 — An attempt to add or join a system database, '%.*ls', to an availability group failed. Specify only user databases for this operation.
- 35250 — The connection to the primary replica is not active. The command cannot be processed.
- 35251 — This command can be run only on the primary replica. Connect to the primary replica, and retry the command.
- 35252 — The command can only be run on a secondary database. Connect to the correct secondary replica, and retry the command.
- 35253 — Database "%.*ls" is not in the correct state to become the primary database. The log must be restored from the previous primary replica to bring the d…
- 35254 — An error occurred while accessing the availability group metadata. Remove this database or replica from the availability group, and reconfigure the av…
- 35255 — An attempt to start database '%.*ls' failed because the database is already started and online.
- 35256 — The session timeout value was exceeded while waiting for a response from the other availability replica in the session. That replica or the network mi…
- 35257 — Always On Availability Groups Send Error (Error code 0x%X, "NOT OK") was returned when sending a message for database ID %d. If the partner is running…
- 35258 — Error in the hadron simulator.
- 35259 — Database '%.*ls' is already participating in a different availability group.
- 35260 — During an attempted database recovery, an availability database manager was not found for database id %d with availability group ID %d and group datab…
- 35261 — Attempt to perform an Always On Availability Groups operation on a system database, '%ls', failed. System databases are not supported by Always On Ava…
- 35262 — Skipping the default startup of database '%.*ls' because the database belongs to an availability group (Group ID: %d). The database will be started by…
- 35263 — During the undo phase, a function call (%ls) to the primary replica returned an unexpected status (Code: %d). Check for a possible cause in the SQL Se…
- 35264 — Always On Availability Groups data movement for database '%.*ls' has been suspended for the following reason: "%S_MSG" (Source ID %d; Source string: '…
- 35265 — Always On Availability Groups data movement for database '%.*ls' has been resumed. This is an informational message only. No user action is required.
- 35266 — Always On Availability Groups connection with %S_MSG database established for %S_MSG database '%.*ls' on the availability replica '%.*ls' with Replica…
- 35267 — Always On Availability Groups connection with %S_MSG database terminated for %S_MSG database '%.*ls' on the availability replica '%.*ls' with Replica …
- 35268 — Synchronization of a secondary database, '%.*ls', was interrupted, leaving the database in an inconsistent state. The database will enter the RESTORIN…
- 35269 — Synchronization of a secondary database, '%.*ls', was interrupted, leaving the database in an inconsistent state. The database will be marked SUSPECT.…
- 35270 — Received a corrupt FileStream transport message. The '%ls' message section is invalid.
- 35271 — The availability database %ls in availailability group %ls failed to complete a reconfiguration. Refer to the error code for more details. If this con…
- 35272 — Either nvalid parameters were supplied for sys.sp_availability_group_command_internal or user does not have permissions to execute this procedure.
- 35273 — Bypassing recovery for database '%ls' because it is marked as an inaccessible availability database. The session with the primary replica was interrup…
- 35274 — Recovery for availability database '%ls' is pending until the secondary replica receives additional transaction log from the primary before it complet…
- 35275 — A previous RESTORE WITH CONTINUE_AFTER_ERROR operation or being removed while in the SUSPECT state from an availability group left the '%.*ls' databas…
- 35276 — Failed to allocate and schedule an Always On Availability Groups task for database '%ls'. Manual intervention may be required to resume synchronizatio…
- 35277 — Automatic failover is not supported for distributed availability group replica.
- 35278 — Availability database '%.*ls', which is in the secondary role, is being restarted to resynchronize with the current primary database. This is an infor…
- 35279 — The attempt to join database '%.*ls' to the availability group was rejected by the primary database with error '%d'. For more information, see the SQL…
- 35280 — Database '%.*ls' cannot be added to availability group '%.*ls'. The database is already joined to the specified availability group. Verify that the da…
- 35281 — Database '%.*ls' cannot be removed from availability group '%.*ls'. The database is not joined to the specified availability group. Verify that the da…
- 35282 — Availability replica '%.*ls' cannot be added to availability group '%.*ls'. The availability group already contains an availability replica with the s…
- 35283 — Availability replica '%.*ls' cannot be removed from availability group '%.*ls'. The availability group does not contain an availability replica with t…
- 35284 — Availability replica '%.*ls' cannot be removed from availability group '%.*ls', because this replica is on the local instance of SQL Server. If the lo…
- 35285 — The recovery LSN %S_LSN was identified for the database with ID %d. This is an informational message only. No user action is required.
- 35286 — Using the recovery LSN %S_LSN stored in the metadata for the database with ID %d. This is an informational message only. No user action is required.
- 35287 — Always On Availability Groups transport for availability database "%.*ls" failed to decompress the log block whose LSN is %S_LSN. This error can be ca…
- 35288 — Always On Availability Groups log apply for availability database "%.*ls" has received an out-of-order log block. The expected LSN was %S_LSN. The rec…
- 35289 — Failed to send request for file '%.*ls' to the '%.*ls' primary database for the local secondary database. Resuming the database will be retried automa…
- 35290 — Failed to wait for completion of file requests from the '%.*ls' primary database for the local secondary database. Resuming the database will be retri…
- 35291 — Failed to acquire exclusive access to the extended recovery fork stack (error %d). If the problem persists, you might need to restart the instance of …
- 35292 — An internal error occurred when performing an operation on extended recovery forks. This is an informational message only. No user action is required.
- 35293 — Error in retrieving extended recovery forks from the primary replica. The extended-recovery-fork stack changed while being retrieved by the secondary …
- 35294 — Log backup for database "%.*ls" on a secondary replica failed because a synchronization point could not be established on the primary database. Either…
- 35295 — Log backup for database "%.*ls" on a secondary replica failed because the last backup LSN (0x%ls) from the primary database is greater than the curren…
- 35296 — Log backup for database "%.*ls" on secondary replica failed because the new backup information could not be committed on primary database. Check the d…
- 35297 — Log backup for database "%.*ls" on secondary replica created backup files successfully but could not ensure that a backup point has been committed on …
- 35298 — The backup on the secondary database "%.*ls" was terminated, but a terminate backup message could not be sent to the primary replica. This is an infor…
- 35299 — Nonqualified transactions are being rolled back in database %.*ls for an Always On Availability Groups state change. Estimated rollback completion: %d…
- 35301 — The statement failed because a columnstore index cannot be unique. Create the columnstore index without the UNIQUE keyword or create a unique index wi…
- 35302 — The statement failed because specifying sort order (ASC or DESC) is not allowed when creating a columnstore index. Create the columnstore index withou…
- 35303 — The statement failed because a nonclustered index cannot be created on a table that has a clustered columnstore index. Consider replacing the clustere…
- 35304 — The statement failed because a clustered columnstore index cannot be created on a table that has a nonclustered index. Consider dropping all noncluste…
- 35305 — The statement failed because a clustered columnstore index cannot be created on a view. Consider creating a nonclustered columnstore index on the view…
- 35306 — The statement failed because a columnstore index cannot be specified using INDEX specification at the column level.
- 35307 — The statement failed because column '%.*ls' on table '%.*ls' is a computed column. Columnstore index cannot include a computed column implicitly or ex…
- 35308 — The statement failed because a columnstore index cannot be a filtered index. Consider creating a columnstore index without the predicate filter.
- 35309 — The statement failed because a columnstore index cannot be created on a sparse column. Consider creating a nonclustered columnstore index on a subset …
- 35310 — The statement failed because columnstore indexes are not allowed on table types and table variables. Remove the column store index specification from …
- 35311 — The statement failed because a columnstore index cannot have included columns. Create the columnstore index on the desired columns without specifying …
- 35312 — The statement failed because a columnstore index cannot be created on a column with filestream data. Consider creating a nonclustered columnstore inde…
- 35313 — The statement failed because specifying FILESTREAM_ON is not allowed when creating a columnstore index. Consider creating a columnstore index on colum…
- 35314 — The statement failed because a columnstore index cannot be created on a column set. Consider creating a nonclustered columnstore index on a subset of …
- 35315 — The statement failed because a columnstore index cannot be created in this edition of SQL Server. See Books Online for more details on feature support…
- 35316 — The statement failed because a columnstore index must be partition-aligned with the base table. Create the columnstore index using the same partition …
- 35317 — The statement failed because specifying %S_MSG is not allowed when creating a columnstore index. Consider creating a columnstore index without specify…
- 35318 — The statement failed because the %S_MSG option is not allowed when creating a columnstore index. Create the columnstore index without specifying the %…
- 35319 — The table option DATA_COMPRESSION is not allowed when a table specifies a clustered column store index.
- 35320 — Column store indexes are not allowed on tables for which the durability option SCHEMA_ONLY is specified.
- 35321 — Table '%.*ls' uses a clustered columnstore index. Columnstore indexes are not supported in this service tier of the database. See Books Online for mor…
- 35322 — The statement failed because a nonclustered index and the underlying clustered columnstore index must be partition-aligned. Consider creating the nonc…
- 35323 — The statement failed because adding multiple generated value type columns (such as identity and uniqueidentifier types) at once is not supported for c…
- 35324 — The statement failed because specifying SORT_IN_TEMPDB is not allowed when creating a columnstore index without ORDER. Consider creating a columnstore…
- 35325 — The statement failed because the definition of a column belonging to clustered columnstore index cannot be changed. Consider dropping the columnstore …
- 35326 — The statement failed because a nonclustered columnstore index cannot be reorganized. Reorganization of a nonclustered columnstore index is not necessa…
- 35327 — ALTER INDEX REBUILD statement failed because specifying %S_MSG is not allowed when rebuilding a columnstore index. Rebuild the columnstore index witho…
- 35328 — ALTER INDEX REBUILD statement failed because the %S_MSG option is not allowed when rebuilding a columnstore index. Rebuild the columnstore index witho…
- 35329 — The statement failed because specifying ORDER is not allowed when creating the rowstore index '%.*ls' on table '%.*ls'. Consider creating the rowstore…
- 35330 — %S_MSG statement failed because data cannot be updated in a table that has a nonclustered columnstore index. Consider disabling the columnstore index …
- 35331 — Cannot use duplicate column names in the ORDER column list. Column name '%.*ls' appears more than once.
- 35332 — Cannot ORDER on more than %d columns.
- 35333 — ORDER failed because columnstore index '%.*ls' on table '%.*ls.%.*ls' is already ordered.
- 35334 — DBCC DBREINDEX failed because specifying FILLFACTOR is not allowed when creating or rebuilding a columnstore index. Rebuild the columnstore index with…
- 35335 — The statement failed because specifying a key list is not allowed when creating a clustered columnstore index. Create the clustered columnstore index …
- 35336 — The statement failed because specifying key list is missing when creating an index. Create the index with specifying key list .
- 35337 — UPDATE STATISTICS failed because statistics cannot be updated on a columnstore index. UPDATE STATISTICS is valid only when used with the STATS_STREAM …
- 35338 — Clustered columnstore index is not supported.
- 35339 — Multiple columnstore indexes are not supported.
- 35340 — LOB columns are disabled in columnstore.
- 35341 — The statement failed. A columnstore index cannot include a decimal or numeric data type with a precision greater than 18. Reduce the precision or omit…
- 35342 — The statement failed because specifying ORDER is not a valid option for creating the non-clustered columnstore index '%.*ls' on table '%.*ls'. Conside…
- 35343 — The statement failed. Column '%.*ls' has a data type that cannot participate in a columnstore index.
- 35344 — MERGE clause of ALTER PARTITION statement failed because two nonempty partitions containing a columnstore index cannot be merged. Consider an ALTER TA…
- 35345 — MERGE clause of ALTER PARTITION statement failed because two partitions on different filegroups cannot be merged if either partition contains columnst…
- 35346 — SPLIT clause of ALTER PARTITION statement failed because the partition is not empty. Only empty partitions can be split in when a columnstore index ex…
- 35347 — The stored procedure 'sp_tableoption' failed because a table with a columnstore index cannot be altered to use vardecimal storage format. Consider dro…
- 35348 — The statement failed because table '%.*ls' uses vardecimal storage format. A columnstore index cannot be created on a table using vardecimal storage. …
- 35349 — TRUNCATE TABLE statement failed because table '%.*ls' has a columnstore index on it. A table with a columnstore index cannot be truncated. Consider dr…
- 35350 — The statement failed because a columnstore index on a partitioned table must be partition-aligned with the base table. Consider dropping the columnsto…
- 35351 — DROP INDEX statement failed because a columnstore index on a partitioned table must be partition-aligned with the base table (heap). Consider dropping…
- 35352 — %S_MSG statement failed because the operation cannot be performed online on a table with a columnstore index. Perform the operation without specifying…
- 35353 — %s cannot be enabled on a table with a clustered columnstore index. Consider dropping clustered columnstore index '%s' on table '%s'.
- 35354 — The statement failed because a clustered columnstore index cannot be created on a table enabled for %S_MSG. Consider disabling %S_MSG and then creatin…
- 35355 — The statement failed. Column '%.*ls' is either a primary key or a partitioning key that must be included, but a columnstore index cannot include a dec…
- 35356 — This operation is not supported on nonclustered columnstore indexes built in earlier versions of SQL Server. Consider rebuilding the index.
- 35357 — The statement failed because a secondary dictionary reached the maximum size limit. Consider dropping the columnstore index, altering the column, then…
- 35358 — CREATE TRIGGER on table '%.*ls' failed because you cannot create a trigger on a table with a clustered columnstore index. Consider enforcing the logic…
- 35359 — The statement failed because a table with a clustered columnstore index cannot have triggers. Consider removing all triggers from the table and then c…
- 35360 — Referential constraint '%.*ls' cannot be created because the %S_MSG table '%.*ls' has a clustered columnstore index.
- 35361 — The statement failed. A clustered columnstore index cannot be created over referencing column '%.*ls' on table '%.*ls'.
- 35362 — Tuple mover stvf skipped rowset in DW mode
- 35363 — The statement failed because clustered columnstore indexes are not supported in system databases.
- 35364 — ALTER INDEX statement option COMPRESSION_DELAY can only be used with columnstore indexes.
- 35365 — The compression block header at offset %ld is invalid.
- 35366 — The columnstore blob Xpress header is invalid.
- 35367 — The columnstore blob Xpress object header is invalid.
- 35368 — Internal DDL Operation Error: The DDL encountered an unexpected error %d during execution (HRESULT = 0x%x).
- 35369 — GETCHECKSUM can not be used for a table which has a clustered columnstore index.
- 35370 — Cursors are not supported on a table which has a clustered columnstore index.
- 35371 — SNAPSHOT isolation level is not supported on a table which has a clustered columnstore index.
- 35372 — You cannot create more than one clustered index on %S_MSG '%.*ls'. Consider creating a new clustered index using 'with (drop_existing = on)' option.
- 35373 — ALTER INDEX REORGANIZE statement failed on a clustered columnstore index with error %d. See previous error messages for more details.
- 35374 — Columnstore archive decompression failed with error %d.
- 35375 — ALTER INDEX REORGANIZE statement option COMPRESS_ALL_ROW_GROUPS can only be used with clustered columnstore indexes.
- 35376 — Tuple mover stvf got passed invalid arguments
- 35377 — When MARS is on, accessing clustered columnstore indexes is not allowed.
- 35378 — Row groups stvf got passed invalid arguments
- 35379 — Internal error occurred while flushing delete buffer database id %d, table id %d, index id %d, partition number %d. Additional messages in the SQL Ser…
- 35380 — The non-clustered columnstore index '%.*ls' on table '%.*ls' cannot be reorganized due to an active snapshot transaction.
- 35381 — The columnstore blob dictionary header is invalid.
- 35382 — The specified COMPRESSION_DELAY option value %d is invalid. The valid range for disk-based table is between (0, 10080) minutes and for memory-optimize…
- 35383 — The use of user-defined functions is not allowed in default constraints when adding columns to a columnstore index.
- 35384 — The statement failed because column '%.*ls' on table '%.*ls' is a lob column. Non clustered index with lob column as included column cannot co-exist w…
- 35385 — DROP ORDER failed because columnstore index '%.*ls' on table '%.*ls.%.*ls' is not ordered.
- 35386 — Could not get the memory grant of %I64d KB for columnstore compression because it exceeds the maximum configuration limit of %I64d KB in the current w…
- 35387 — TEMPDB ran out of space during spilling. Verify that data is evenly distributed and/or rewrite the query to consume fewer rows. If the issue still per…
- 35388 — The statement failed because column '%.*ls' on table '%.*ls' is a persisted computed column. Adding persisted computed columns to an existing clustere…
- 35389 — The statement failed because column '%.*ls' on table '%.*ls' is a computed column of a LOB type. Columnstore indexes cannot include computed columns o…
- 35390 — Computed columns in columnstore indexes are temporarily disabled. Please rewrite your query to exclude computed columns.
- 35391 — Could not build or rebuild clustered columnstore index '%.*ls' online, because the the table has secondary indexes. Please perform the operation offli…
- 35392 — The statement failed because column '%.*ls' on table '%.*ls' is a computed column. Nonclustered index with computed column as key or included column c…
- 35393 — Columnstore tuple mover unit tests can't be run under master database.
- 35394 — Transaction %d reached %I64u log used bytes and %I64d reserved log bytes. In order to minimize log usage %d suboptimal rowgroups were created, which i…
- 35395 — Transaction %d reached %I64u log used bytes and %I64d reserved log bytes. In order to minimize log usage, %d suboptimal rowgroups were created, which …
- 35396 — Effective DOP of %u is too high for columnstore compression on table id %d because each thread only has %I64d KB for compression. Please retry using t…
- 35397 — %S_MSG statement failed because the operation cannot be performed resumably on a table with a columnstore index. Perform the operation without specify…
- 35398 — Columnstore index operation failed. Please contact Microsoft customer support.
- 35399 — Could not create columnstore index '%.*ls' on table '%.*ls' since data type of column '%.*ls' is not supported in the ORDER list.
- 35400 — Columnstore tuple mover is unable to acquire lock.
- 35401 — ONLINE
- 35402 — ALLOW_ROW_LOCKS
- 35403 — ALLOW_PAGE_LOCKS
- 35404 — sequence
- 35405 — decryption
- 35406 — creation
- 35409 — Replication
- 35410 — Change Tracking
- 35411 — Change Data Capture
- 35412 — CloudDB Async Transport
- 35413 — CloudDB Async Transport Forwarder
- 35415 — mirrored
- 35417 — primary
- 35418 — secondary
- 35419 — feature
- 35420 — operation
- 35421 — statement
- 35422 — index option
- 35423 — table option
- 35424 — operator
- 35425 — value
- 35426 — system column
- 35427 — set option
- 35428 — query hint
- 35429 — transaction isolation level
- 35430 — in-memory index
- 35431 — SCHEDULER
- 35432 — NUMANODE
- 35433 — federation
- 35434 — federation distribution
- 35435 — system database
- 35436 — federation member database
- 35437 — non federation member database
- 35438 — federation root database
- 35439 — it is a system database.
- 35440 — it acts as a distribution database
- 35441 — an internal error occurred
- 35442 — it is involved in a mirroring session. Turn off the mirroring session and try again
- 35443 — it is not in SIMPLE recovery mode. Change the recovery model to SIMPLE and try again
- 35444 — it is a database snapshot
- 35445 — it is a not currently enabled
- 35446 — clause
- 35447 — Cluster Proxy
- 35448 — partition
- 35449 — signing algorithm
- 35450 — table
- 35451 — join hint
- 35452 — Database unavailable
- 35453 — it is a system database. Make sure to target a user database. If you want temporary clustered columnstore tables, consider creating a regular user dat…
- 35454 — a transaction is currently active. Execute sp_db_enable_clustered_columnstores by itself
- 35455 — an internal error occurred
- 35456 — it is involved in a mirroring pair. Consider disabling mirroring, changing the setting, then re-establishing mirroring
- 35457 — it is a database snapshot
- 35458 — it is part of an Always On availability group. Consider removing the database from the availability group, changing the setting, and then adding the d…
- 35459 — it is a replication distribution database. Make sure to target a regular user database
- 35460 — it is not using the SIMPLE recovery model. Consider temporarily changing to the simple recovery model, then downgrading, then switching back
- 35461 — it contains one or more clustered columnstore indexes. Consider dropping these indexes or creating clustered B-tree indexes instead, and trying again
- 35462 — referencing
- 35463 — referenced
- 35464 — columnstore indexes are not supported in the current SQL Server edition. See SQL Server Books Online for supported editions
- 35465 — Unable to allocate the recovery thread
- 35466 — Exception in the recovery thread
- 35467 — Already linked to a partition host
- 35468 — Partition DB marked as suspect
- 35469 — Failed to get Partition DB attributes
- 35470 — Partition Host
- 35471 — Partition metadata not found
- 35472 — memory optimized tables
- 35473 — natively compiled modules
- 35474 — indexes on memory optimized tables
- 35475 — hash indexes
- 35476 — transactions that access memory optimized tables or natively compiled modules
- 35477 — databases that have a MEMORY_OPTIMIZED_DATA filegroup
- 35478 — truncate
- 35479 — start
- 35480 — stop
- 35481 — memory optimized table types
- 35482 — clustered
- 35483 — nonclustered
- 35484 — BUCKET_COUNT
- 35485 — security policy
- 35486 — memory optimized tables that have a column store index
- 35487 — Global Transactions
- 35488 — natively compiled triggers
- 35489 — Upgrade of Hekaton database
- 35490 — memory optimized tables that have max length columns
- 35491 — max length columns in natively compiled modules
- 35492 — column definition
- 35493 — enabled
- 35494 — disabled
- 35495 — memory optimized table
- 35496 — natively compiled module
- 35497 — module
- 35498 — external data source
- 35499 — OUTPUT clauses in natively compiled modules
- 35501 — schemas that contain natively compiled modules
- 35502 — change_tracking_hardened_cleanup_version()
- 35503 — safe_cleanup_version()
- 35504 — server encryption protector
- 35505 — RESUMABLE
- 35506 — MAX_DURATION
- 35507 — Storage
- 35508 — RESUME
- 35509 — PAUSE
- 35510 — ABORT
- 35511 — ABORT
- 35512 — allow_enclave_computations
- 35513 — compute
- 35514 — local computer
- 35515 — current user
- 35516 — query_capture_policy
- 35517 — execution_count
- 35518 — total_compile_cpu_time_ms
- 35519 — total_execution_cpu_time_ms
- 35520 — OPTIMIZE_FOR_SEQUENTIAL_KEY
- 35521 — stale_capture_policy_threshold
- 35522 — day
- 35523 — TRIPLE_DES_3KEY
- 35524 — AES_256
- 35525 — STATISTICS_ONLY
- 35526 — striped_metadata
- 35527 — rbio_connection
- 35528 — unable to read page due to invalid FCB
- 35529 — certificate id
- 35530 — opening
- 35531 — closing
- 35532 — certificate name
- 35533 — norm function failed
- 35534 — string_split
- 35535 — unpack_int
- 35536 — vector index
- 35537 — JSON index
- 35538 — columnstore index
- 35539 — vector base type
- 35540 — external model
- 35541 — ai_generate_chunks
- 35542 — Drop and re-create the distributed availability group with SQL Managed Instance.
- 35543 — Stored procedure called on invalid distributed availability group type or on non-existing distributed availability group.
- 35544 — Empty internal distributed availability group.
- 35545 — Internal distributed availability group naming inconsistency.
- 35546 — An internal distributed availability group detected with more than one associated availability database.
- 35547 — Use sys.sp_mi_dag_repair on the distributed availability group.
- 35548 — column level security
- 35549 — dynamic data masking
- 35550 — Semantic index
- 35551 — QUALIFY
- 35552 — VECTOR type argument. Expected DENSE or SPARSE
- 35553 — a required vector index feature switch (TRUNCATE support or vector index state) is disabled
- 35554 — the vector index version is earlier than 3
- 35555 — the database default collation or a column/parameter still uses this collation. Remove all references to that collation before disabling the feature
- 36001 — %s '%s' already exists in the database.
- 36002 — instance_id already exists in the database.
- 36003 — %s '%s' already exists for the given DAC instance.
- 36004 — DacInstance with the specified instance_id does not exist.
- 36005 — Dac root - database %s does not exist.
- 36006 — Dac Policy with the specified policy id already exists in the parts table.
- 36007 — Dac Part the policy refers to, does not exist.
- 36008 — Dac Policy refers to a non-existent Policy.
- 36009 — %s '%s' already exists in the Dac Parts.
- 36010 — The caller must be a member of the dbcreator fixed server role to perform this action.
- 36011 — The caller must be sysadmin or the creator of the history entry being updated.
- 36012 — Unable to execute T-SQL within procedure due to SQL Server limitation.\nPlease execute following T-SQL in database '%s' context after this procedure f…
- 36101 — Process ID %d is not an active process ID.
- 37001 — This operation is not allowed since there are dependent objects pending installation.
- 37002 — Cannot find the database '%s', because it does not exist or you do not have permission to access it.
- 37003 — This operation is not allowed because a utility control point already exists on this instance of SQL Server.
- 37004 — The specified instance of SQL Server cannot be used as a utility control point because the feature is not enabled in SQL Server '%s'.
- 37005 — The specified instance of SQL Server cannot be managed by a utility control point because the feature is not enabled in SQL Server '%s'.
- 37006 — Cannot perform the operation because the specified instance of SQL Server is not enrolled in a SQL Server utility.
- 37007 — An error occurred during upload to the SQL Server utility control point.
- 37008 — The operation cannot continue. To remove the SQL Server utility control point, the user must be a member of the sysadmin role.
- 37009 — The operation cannot continue. The specified instance of SQL Server is not a SQL Server utility control point.
- 37010 — The operation cannot continue. The SQL Server utility control point has managed instances of SQL Server enrolled.
- 37101 — Server '%.*ls' does not contain elastic job account: '%.*ls'.
- 37102 — Elastic job account '%.*ls' does not contain the resource of type '%.*ls' named '%.*ls'.
- 37103 — Internal job account error occurred : '%.*ls'.
- 37104 — A job account already exists for subscription '%.*ls' for the selected region.
- 37105 — The job account '%.*ls' on server '%.*ls' already exists.
- 37106 — The database '%.*ls' on server '%.*ls' is in use by job account '%.*ls'. The database cannot be deleted or renamed while associated with a job account…
- 37107 — The database '%.*ls' on server '%.*ls' has service level objective '%.*ls' which is not supported for use as a job account database.
- 37108 — A job account could not be linked to database '%.*ls' on server '%.*ls' because it is a geo-secondary database.
- 37109 — Database '%ls' on server '%ls' is already linked to another job account.
- 37201 — An instance pool could not be found with name '%.*ls'.
- 37202 — An instance pool with name '%.*ls' is busy with another ongoing operation.
- 37203 — An instance pool with name '%.*ls' is not empty.
- 37204 — An instance pool with name '%.*ls' does not have enough vCore capacity for given request.
- 37301 — Internal enclave error. The enclave symcrypt method %ls failed with status 0x%08x. For more information, contact Customer Support Services.
- 37302 — Enclave attestation failed due to an internal error. API: '%ls'. Return code: '0x%08x'. For more information, contact Customer Support Services.
- 37303 — Internal error occurred while obtaining an authentication token for an attestation service. Authentication method: %ls, status: 0x%08x.
- 37304 — Cannot initialize %ls enclave for column encryption - the operating system does not support the enclave type.
- 37305 — Invalid enclave configuration: %ls.
- 37306 — Internal enclave error: Cannot initialize the %ls enclave. Error: 0x%08x. For more information, contact Customer Support Services.
- 37307 — Internal enclave error: Cannot initialize the %ls enclave. Load method: %ls. For more information, contact Customer Support Services.
- 37308 — Loaded %ls enclave for Always Encrypted.
- 37309 — Enclave attestation failed due to an error in Intel Data Center Attestation Primitives (DCAP) SGX API: '%ls'. Return code: '0x%08x'. For more informat…
- 37310 — Enclave attestation failed due to an error while parsing the attestation URL provided by the client. URL: '%ls'. Return code: '0x%08x'.
- 37311 — Enclave attestation failed. The attestation URL provided by the client has an invalid scheme name. URL: '%ls'. The supported schemes are: '%ls'.
- 37312 — Enclave attestation failed. The attestation URL specified by the client is not reachable. URL: '%ls'. Return code: '0x%08x'. Check your networking con…
- 37313 — Enclave attestation failed. The attestation service returned an empty response. Attestation URL: '%ls'. Verify the attestation policy. If the policy i…
- 37314 — VBS enclave attestation failed due to an error in Windows Management Instrumentation (WMI). API: '%ls', Return code: '0x%08x'. Check the Host Gurdian …
- 37315 — Credential object named '0x%08x', configured for external authentication, does not exist.
- 37316 — Authentication bearer service failed to return a valid challenge. Verify URL '%ls' is correct. Return code: '0x%08x'.
- 37317 — Failed to look up '%ls' for '%ls'.
- 37318 — Unable to acquire an authentication token for resource_id '%ls' with URL '%ls'. Return code: '0x%08x'. For more information, contact Customer Support …
- 37319 — Failed to obtain an authentication token for URL '%ls'. Return code: '0x%08x'.
- 37320 — Authentication for URL '%ls' failed due to an invalid client id or an invalid secret. Return code: '0x%08x'.
- 37321 — Failed to acquire a token using a managed service identity. Make sure managed identities are enabled on the machine hosting SQL Server. Return code: '…
- 37322 — Failed to acquire a token using a managed service identity. Make sure managed identities are enabled on the machine hosting SQL Server. Error code: '%…
- 37323 — Authentication bearer service failed to return a valid challenge. Verify URL '%ls' is correct. Error code: '%ls'. Error message: '%ls'. Return code: '…
- 37324 — Enclave attestation failed. Attestation service returned Error code: '%ls'. Error message: '%ls'. Attestation URL: '%ls'. Return code: '0x%08x'. Verif…
- 37325 — Enclave attestation failed due to an error in Azure Data Center Attestation Primitives (DCAP) Client. Validate Azure DCAP Client is installed and conf…
- 37326 — Enclave attestation failed due an authorization failure. Verify the identity of SQL Server instance has the required permissions to access an attestat…
- 37327 — Maximum number of concurrent DBCC commands running in the enclave has been reached. The maximum number of concurrent DBCC queries is %d. Try rerunning…
- 37328 — Configuring Always Encrypted enclave in %ls mode.
- 37329 — %ls enclave lost due to internal error. For more information, contact Customer Support Services.
- 37330 — Failed to acquire a token using a managed service identity. Make sure managed identities are enabled on the machine hosting SQL Server. Authentication…
- 37331 — DevOps login, '%s', can not be created as another non-devops server principal with name or object ID already exists.
- 37332 — DevOps user, '%.*ls', can not be created as another non-devops database principal with name or object ID already exists.
- 37333 — The server encountered an unexpected exception. API:'%ls' Return code: '0x%08x'. For more information, contact Customer Support Services.
- 37334 — Internal error occurred while obtaining an authentication token for an external service. Authentication method: %ls, Status: 0x%08x, CorrelationId: %l…
- 37335 — Failed to acquire a token using a managed service identity. Make sure managed identities are enabled on the machine hosting SQL Server. Authentication…
- 37336 — Failed to flush the Ledger Transactions table to disk in database with ID %d due to error %d. Check the errorlog for more information.
- 37337 — Failed to retrieve the information about the latest transaction persisted in sys.db_ledger_transactions in database with ID %d due to error %d. Check …
- 37338 — Error occurred while generating the hash for a ledger transaction. Return code: '%d'.
- 37339 — Error occurred while generating a hash for the MERKLE_TREE_AGG aggregate function. Return code: '%d'.
- 37340 — Failed to generate the Ledger Blocks in the database with ID %d due to error %d. Check the errorlog for more information.
- 37341 — Azure Active Directory Administrator is not enabled for this server. Please set up the AAD Admin on this server and try again.
- 37342 — The logical server AAD tenant ID does not match the given devops AAD tenant ID.
- 37343 — Unexpected data type for encrypted column while generating ledger hash.
- 37344 — CREATE TABLE failed because column '%.*ls' in table '%.*ls' exceeds the maximum of %d columns allowed for ledger tables.
- 37345 — Table cannot have more than one 'GENERATED ALWAYS AS %ls' column.
- 37346 — 'GENERATED ALWAYS AS %ls' column '%.*ls' has invalid data type.
- 37347 — 'GENERATED ALWAYS AS %ls' column '%.*ls' cannot be nullable.
- 37348 — 'GENERATED ALWAYS AS %ls' column '%.*ls' can only be nullable.
- 37349 — LEDGER = ON cannot be specified with SYSTEM_VERSIONING = OFF and APPEND_ONLY = OFF.
- 37350 — LEDGER = ON cannot be specified with SYSTEM_VERSIONING = ON and APPEND_ONLY = ON.
- 37351 — LEDGER = ON cannot be specified with PERIOD FOR SYSTEM_TIME and APPEND_ONLY = ON.
- 37352 — APPEND_ONLY = ON cannot be specified with generated always end columns.
- 37353 — Server identity does not have Azure Active Directory Readers permission. Please follow the steps here : https://learn.microsoft.com/azure/azure-sql/da…
- 37354 — LEDGER = ON cannot be specified with system versioning retention period.
- 37355 — An existing History Table cannot be specified with LEDGER=ON.
- 37356 — System Versioning cannot be altered for Ledger Tables.
- 37357 — SQL Audit could not write to '%s'. Make sure that SAS key is valid or Managed Identity has permissions to access the storage. This is an informative m…
- 37358 — SQL Audit failed to create the audit file for the audit '%s' at '%s'. Make sure that SAS key is valid or Managed Identity has permissions to access th…
- 37359 — Updates are not allowed for the append only Ledger table '%.*ls'.
- 37360 — %S_MSG is not allowed on Ledger tables.
- 37361 — Cannot update ledger history table '%.*ls'.
- 37362 — LEDGER = ON cannot be specified on a table with a column set column.
- 37363 — Copy operation for the database '%.*ls' on the server '%.*ls' cannot be started because both source and target SLOs need to be DC series. Source DB SL…
- 37364 — A transaction cannot update more than %d ledger tables.
- 37365 — The '%s' parameter provided for ledger verification cannot be null.
- 37366 — The hash computed from sys.database_ledger_transactions for block %I64d does not match the hash persisted in sys.database_ledger_blocks.
- 37367 — The computed hash does not match the previous block hash persisted in sys.database_ledger_blocks for block %I64d.
- 37368 — The hash of block %I64d in the database ledger does not match the hash provided in the digest for this block.
- 37369 — Invalid input for parameter '@digests' provided for ledger verification. The value should be a valid JSON document that contains values for the 'block…
- 37370 — Ledger verification successfully verified up to block %I64d.
- 37371 — The computed hash from '%s' and the associated history table does not match the hash persisted in sys.database_ledger_transactions for transaction %I6…
- 37372 — Invalid table ID '%d' is present in database ledger table sys.database_ledger_transactions.
- 37373 — Error occurred while initializing hash algorithm at startup. Return code: '%d'.
- 37374 — Creation of Ledger view failed due to error %d.
- 37375 — Cannot add PRIMARY KEY, UNIQUE KEY or CHECK constraint to the ledger history table '%.*ls'.
- 37376 — Foreign key '%.*ls' is not valid. A ledger history table cannot be used in a foreign key definition.
- 37377 — Foreign key '%.*ls' is not valid. An append only ledger table cannot be the referencing table of a foreign key constraint with cascading actions.
- 37378 — Ledger tables cannot be created on system databases.
- 37379 — Ledger tables cannot contain columns of XML, sql_variant, filestream or user-defined types. Any computed columns cannot be timestamp columns.
- 37380 — Cannot create UNIQUE index on ledger history table '%.*ls'.
- 37381 — Cannot create a trigger on a system-versioned ledger table '%.*ls'.
- 37382 — Switching partition failed on table '%.*ls' because it is not a supported operation on ledger tables or their corresponding history table.
- 37383 — Enabling Change Tracking for ledger history table '%.*ls' is not allowed.
- 37384 — Table '%.*ls' is a FileTable. LEDGER = ON cannot be used on FileTables.
- 37385 — LEDGER = ON is not allowed for table variables.
- 37386 — Cannot drop object '%.*ls' because it is a ledger history table or a ledger view.
- 37387 — Only nullable columns without a default value WITH VALUES can be added to ledger tables.
- 37388 — Column '%.*ls' in table '%.*ls' cannot be dropped because it is already a dropped ledger column.
- 37389 — Cannot ALTER VIEW '%.*ls' because it is a ledger view.
- 37390 — System-time PERIOD cannot be added to table '%.*ls' because it is a ledger table.
- 37391 — ALTER TABLE ALTER COLUMN failed for table '%.*ls' because it is a ledger table and the operation would need to modify existing data that is immutable.
- 37392 — Ledger verification failed.
- 37393 — The default ledger view name is constructed as <table_name>_Ledger, which exceeds the maximum length of %d characters. Specify a ledger table name tha…
- 37394 — Cannot create index on view '%.*ls' because it is a ledger view. The indexes should be created on the ledger table or its history table.
- 37395 — View '%.*ls' is not updatable because it is a ledger view.
- 37396 — Query cannot be executed, access token is expired. Please login with a new access token and execute query again.
- 37397 — Error storing Babylon policy for DBID %d. Major error: %d, Minor error: %d, State: %d
- 37398 — Fatal error: Unable to pull policies for %d consecutive attempts.
- 37399 — TYPE, SID, Default Database, Default Language, Password option not allowed for External logins
- 37401 — Error refreshing the external access control policy from metadata. Error code %d.
- 37402 — Setting LEDGER to ON failed because ledger view '%.*ls' is not specified in two-part name format.
- 37403 — Error in parsing Babylon json policy element/event with error message %s.
- 37404 — Service returned an empty response. URL: '%ls'.
- 37405 — Exception in fetching the external policy. URL: '%ls'. Major error code: %d, Minor error code: %d, State: %d
- 37406 — Error occurred while obtaining an authentication token for external service %ls; no authentication method is configured.
- 37407 — Error in Babylon SDK with error message %s.
- 37408 — The ledger digest storage cannot be configured on secondary databases.
- 37409 — The provided Ledger storage target type '%s' is invalid.
- 37410 — The provided ledger storage path '%s' is invalid.
- 37411 — Uploading ledger digests is being enabled or disabled for database '%s'. Please wait for the previous request to complete.
- 37412 — %ls operation failed for %ls. Error code: %d.
- 37413 — Failed to generate a digest in the database with ID %d due to error %d. Check the errorlog for more information.
- 37414 — Failed to retrieve digest information from path '%ls' due to error %d. Verify that the provided path exists and the required permissions have been gra…
- 37415 — Invalid path specified for a ledger digest URL. Verify that the provided paths are valid.
- 37416 — Fulltext indexes are not allowed on ledger tables.
- 37417 — Uploading ledger digest failed for database with id %d due to error %d.
- 37418 — No digests were found based on the input locations and block IDs.
- 37419 — Unable to %S_MSG audit because %S_MSG contains question mark.
- 37420 — LEDGER = OFF cannot be specified for tables in databases that were created with LEDGER = ON.
- 37421 — Error occurred while reading external policy endpoint.
- 37422 — Error occurred while reading STS Url.
- 37423 — Error occurred while fetching the external access policies. Please check if Managed System Identity is enabled on the server.
- 37424 — Error fetching the external policy resource endpoint.
- 37425 — Error occurred while trying to record the ledger table history operation of the ledger table '%.*ls'.
- 37426 — Error occurred while trying to record the ledger column history operation of the column '%.*ls' in ledger table '%.*ls'.
- 37427 — Cannot alter, drop, or rename object '%.*ls' because it is a ledger dropped object.
- 37428 — Cannot rename ledger object '%.*ls' because it is not a supported operation.
- 37429 — Cannot rename column '%.*ls' of ledger object '%.*ls' because it is not a supported operation.
- 37430 — Cannot alter schema of dropped ledger object '%.*ls' because it is not a supported operation.
- 37431 — Encountered failure while initializing Confidential Ledger Adapter with URL %ls and error code %ld.
- 37432 — Encountered failure while initializing Confidential Ledger Data Iterator with URL %ls and error code %ld.
- 37433 — %ls. The attestation URL specified by the client is not reachable. URL: '%ls'. Return code: '0x%08x'. Check your networking configuration.
- 37434 — Invalid input for parameter '@locations' provided for ledger verification. The value should be a valid JSON document that contains values for the 'pat…
- 37435 — Invalid input for parameter '@table_name' provided for ledger verification. The specified value cannot contain a server or database name and must poin…
- 37436 — Ledger verification failed due to error %d.
- 37437 — Uploading ledger digests is currently not supported for this resource type.
- 37438 — Ledger verification for table '%.*ls' failed because its clustered index is disabled.
- 37439 — The statement failed because a nonclustered index cannot be created on table '%.*ls' that is a ledger table and has a clustered columnstore index.
- 37440 — Cannot update dropped ledger table '%.*ls'.
- 37441 — The statement failed because a clustered columnstore index cannot be created on table '%.*ls' that is a ledger table and has a nonclustered index.
- 37442 — Ledger verification was aborted by the user.
- 37443 — The use of replication is not supported with ledger table '%s'
- 37444 — Enabling Change Data Capture for ledger history table '%ls' is not allowed.
- 37445 — The specified digestStorageEndpoint is invalid. It must be an Azure blob storage or Azure Confidential Ledger endpoint.
- 37446 — Changing the ledger property is not supported for this resource type.
- 37447 — The certificate '%.*ls' has been already added as a trusted issuer for DNS name '%.*ls'
- 37448 — The certificate '%.*ls' cannot be removed from the trusted issuers for the DNS name '%.*ls' because it hasn't been added as a trusted issuer for the D…
- 37449 — Warning: The certificate chain of the certificate specified could not be validated at this time. This may cause issues with the certificate-based auth…
- 37450 — The certificate '%.*ls' cannot be added as a trusted issuer for a DNS name because it is not allowed to sign certificates
- 37451 — DNS name provided exceeds maximum length of %d characters.
- 37452 — Error while trying to invoke external policy pull task.
- 37453 — '%ls' is not a valid option for the @type parameter. Enter 'update' or 'reload'.
- 37454 — Encountered Internal Error while calling %ls. Error code %ld, State %ld.
- 37455 — Server identity does not have permissions to access MS Graph. For more information, see https://go.microsoft.com/fwlink/?linkid=2323824 .
- 37456 — Ownership change is not supported for external tables governed by OneLake Security.
- 37457 — DDL statement executed on the database is not allowed because Azure Active Directory only authentication is enabled on the server.
- 37458 — Posted digest is not globally committed in Azure Confidential Ledger. Ledger URL '%ls' and error code %ld.
- 37459 — Encountered Internal Error while calling Azure Confidential Ledger. Ledger URL '%ls' and error code %ld.
- 37460 — Failed to parse response from Identity Service. Ledger URL '%ls' and error code %ld.
- 37461 — Encountered error while trying to retrieve AAD Token to call Azure Confidential Ledger. Ledger URL '%ls' and error code %ld.
- 37462 — Encountered error while trying to retrieve Network Certificate from Identity Service. Ledger URL '%ls' and error code %ld.
- 37463 — Service Principal or Managed Identity is not authorized to call Azure Confidential Ledger. Ledger URL '%ls' and error code %ld.
- 37464 — AAD Authentication is enabled. This is an informational message only; no user action is required.
- 37465 — Server identity does not have the required permissions to access the MS graph. For more information, see https://go.microsoft.com/fwlink/?linkid=23234…
- 37466 — Endpoint is required.
- 37467 — The server encountered an unexpected exception.
- 37468 — The source and target table names provided as parameters to 'sp_copy_data_in_batches' must be valid table names and cannot be null or empty.
- 37469 — The source and target table names provided as parameters to 'sp_copy_data_in_batches' cannot contain a database or server name.
- 37470 — The source and target tables provided to 'sp_copy_data_in_batches' must be user tables.
- 37471 — The source and target tables provided to 'sp_copy_data_in_batches' cannot be memory optimized tables.
- 37472 — The target table '%.*ls' provided to 'sp_copy_data_in_batches' cannot be the source of merge or transactional replication or have change tracking or c…
- 37473 — The target table '%.*ls' provided to 'sp_copy_data_in_batches' cannot have an XML, spatial or fulltext index.
- 37474 — The target table '%.*ls' provided to 'sp_copy_data_in_batches' cannot have a disabled clustered index.
- 37475 — The target table '%.*ls' provided to 'sp_copy_data_in_batches' cannot have any non-clustered indexes or statistics other than the ones for the cluster…
- 37476 — The source and target tables provided to 'sp_copy_data_in_batches' cannot have a column set column.
- 37477 — The source and target tables provided to 'sp_copy_data_in_batches' cannot have any security policies.
- 37478 — The source and target tables provided to 'sp_copy_data_in_batches' cannot be graph node or edge tables.
- 37479 — The target table '%.*ls' provided to 'sp_copy_data_in_batches' cannot have any indexed views referencing it.
- 37480 — The target table '%.*ls' provided to 'sp_copy_data_in_batches' must be empty.
- 37481 — The target table '%.*ls' provided to 'sp_copy_data_in_batches' cannot have any INSERT trigger.
- 37482 — The source and target tables provided to 'sp_copy_data_in_batches' must be using the same partition function and partitioning columns.
- 37483 — The source and target tables provided to 'sp_copy_data_in_batches' must have the same number of columns when excluding the TRANSACTION ID and SEQUENCE…
- 37484 — 'sp_copy_data_in_batches' failed because column '%.*ls' at ordinal %d in table '%.*ls' has a different name than the column '%.*ls' at the same ordina…
- 37485 — 'sp_copy_data_in_batches' failed because column '%.*ls' has data type %s in source table '%.*ls' which is different from its type %s in target table '…
- 37486 — 'sp_copy_data_in_batches' failed because column '%.*ls' does not have the same collation, nullability, sparse, ANSI_PADDING, vardecimal, identity or g…
- 37487 — 'sp_copy_data_in_batches' failed because column '%.*ls' in table '%.*ls' is computed column but the same column in '%.*ls' is not computed or they do …
- 37488 — The source and target tables provided to 'sp_copy_data_in_batches' cannot contain columns of data type text, ntext, image or with the ROWGUIDCOL or FI…
- 37489 — The target table '%.*ls' provided to 'sp_copy_data_in_batches' cannot have any RULE constraints.
- 37490 — 'sp_copy_data_in_batches' failed because computed column '%.*ls' defined as '%.*ls' in table '%.*ls' is different from the same column in table '%.*ls…
- 37491 — The target table '%.*ls' provided to 'sp_copy_data_in_batches' cannot have clustered columnstore index.
- 37492 — The source and target tables provided as parameters to 'sp_copy_data_in_batches' cannot be temporary tables.
- 37493 — Internal enclave error: Cannot initialize the %ls enclave. Load method: %ls. Last Error: 0x%08x. For more information, contact Customer Support Servic…
- 37494 — Authentication bearer service failed to return a valid challenge. Verify URL '%ls' is correct and reachable. Return code: '0x%08x'. Please check netwo…
- 37495 — Ledger verification to detect inconsistencies for index '%.*ls' (database ID %d) failed due to exception %d, state %d.
- 37496 — Ledger verification detected inconsistencies for index '%.*ls' (database ID %d). There are %ld rows that are inconsistent between the table and the in…
- 37497 — Internal parsing error: Fail to parse the service URL '%ls'. Failure method: %ls. Return code: '0x%08x'. For more information, contact Customer Suppor…
- 37498 — Snapshot isolation must be enabled on the database when sp_verify_database_ledger is executed.
- 37499 — Ledger verification detected an inconsistency in the definition of ledger view '%.*ls' for the ledger table '%.*ls'.
- 37501 — A value cannot be given for the column '%.*ls' on ledger table '%.*ls' because it is a dropped ledger column.
- 37502 — The column '%.*ls' on ledger table '%.*ls' cannot be dropped because it is a TRANSACTION_ID or SEQUENCE_NUMBER GENERATED ALWAYS column.
- 37503 — The column '%.*ls' on ledger table '%.*ls' cannot be dropped because it is an identity or computed column.
- 37504 — Failed to convert string to guid when fetching tenantID fabric property %.*ls'
- 37505 — A secondary of secondary database (chaining) cannot be created because automatic upload of ledger digests has been configured for this database.
- 37506 — Automatic upload of ledger digests cannot be enabled because this database is configured with secondaries of secondaries (chaining).
- 37507 — CertPFX using AES encryption is not supported on the current operating system.
- 37508 — Unable to locate PFXExportCertStoreEx API in crypt32.dll, needed for CertPFX using AES encryption ErrorCode: %d.
- 37509 — Unable to locate PFXExportCertStoreEx API in securityapi.dll, needed for CertPFX using AES encryption ErrorCode: %d.
- 37510 — Unable to determine the blob length needed to export the PFX certificate. ErrorCode: %d.
- 37511 — Unable to export the PFX certificate. ErrorCode: %d.
- 37512 — The column '%.*ls' on ledger table '%.*ls' is a sequence number generated always column and cannot be referenced by computed columns, check constraint…
- 37513 — Cannot create %S_MSG on view '%.*ls'. It contains references to sequence number generated always columns.
- 37514 — Cannot bind a rule to a temporal or ledger history table.
- 37515 — Cannot bind a rule to a sequence number generated always column.
- 37516 — Server response exceeded the buffer size. Ledger URL '%ls' and error code %ld.
- 37517 — Internal error occurred while obtaining ARC resource information from IMDS endpoint. Substate: '%ls', status: 0x%08x.
- 37518 — Internal error occurred while obtaining ARC resource information from IMDS endpoint. Error code: '%ls'. Error message: '%ls'. Return code: '0x%08x'.
- 37519 — Internal error occurred while obtaining ARC resource information from IMDS endpoint. Return code: '0x%08x'.
- 37520 — Error retrieving IMDS endpoint.
- 37521 — Geo-replication cannot be stopped because the database has Ledger Digest Uploads enabled. Disable Ledger Digest Uploads and retry the operation.
- 37522 — The Geo-primary database cannot be dropped because the database has Ledger Digest Uploads enabled. Disable Ledger Digest Uploads and retry the operati…
- 37523 — The Azure Confidential Ledger server identity check failed. Ledger URL '%ls' and error code %ld.
- 37524 — IMDS resource information. Subscription ID: %ls, Resource Group: %ls, Name: %ls.
- 37525 — Command '%.*ls' is not supported as Azure Active Directory is not configured for this instance.
- 37526 — A ledger table cannot be created while database mirroring is enabled.
- 37527 — Database '%.*ls'cannot be started as a primary replica because it might be missing ledger transactions for which digests have already been generated. …
- 37528 — Vardecimal cannot be enabled on table '%.*ls' because it is a ledger table or a ledger history table.
- 37529 — Bound transactions are not supported with ledger tables.
- 37530 — Failed to set the ledger digest storage endpoint to '%ls' due to error %d. Verify that the provided Azure Storage account exists, it contains a contai…
- 37531 — Failed to set the ledger digest storage endpoint to '%ls'. Verify that you have created a credential object to provide SQL Server access to the '%ls' …
- 37532 — Ledger table '%.*ls' cannot contain check constraints, filtered indexes and statistics or computed columns that reference columns using a multi-part i…
- 37533 — Computed column '%.*ls' cannot be added to ledger table '%.*ls'. Ledger tables do not support computed columns that use CLR functions or types.
- 37534 — Error while trying to read database information from master metadata. Transaction is not active anymore.
- 37535 — Principal name with object id '%ls' must begin with the original principal name followed by a user-defined suffix to differentiate between the names. …
- 37536 — Internal error occurred while obtaining version information from IMDS endpoint. Substate: '%ls', status: 0x%08x.
- 37537 — Internal error occurred while obtaining version information from IMDS endpoint. Error code: '%ls'. Error message: '%ls'. Return code: '0x%08x'.
- 37538 — Internal error occurred while obtaining version information from IMDS endpoint. Return code: '0x%08x'.
- 37539 — Uploading ledger digest failed for database with id %d due to outbound firewall rules.
- 37540 — The provided ledger digest storage location is not in the list of Outbound Firewall Rules on the server. Please add this to the list of Outbound Firew…
- 37541 — Provider '%ls' is no longer supported. Please use MSOLEDBSQL provider instead. ( https://go.microsoft.com/fwlink/?linkid=2206241&clcid=0x409 )
- 37542 — The operation could not be completed because attempts to connect to Azure Key Vault (AKV) were denied by the configured Network Security Perimeter. Ke…
- 37543 — The trust of the certificate imported could not be verified with the Certificate Authority (CA) or verified through the Internet. Most likely the host…
- 37544 — The length of the AAD bearer token exceeded the maximum allowed length. Ledger URL '%ls' and error code %ld.
- 37545 — '%ls' is not a valid object id for '%ls' or you do not have permission.
- 37546 — Can only specify object_id when creating user from external provider.
- 37547 — The user attempting to perform this operation does not have permission as it is currently logged in as a member of an Azure Active Directory (AAD) gro…
- 37548 — The user attempting to perform this operation does not have permission as it is currently logged in as a member of an Azure Active Directory (AAD) gro…
- 37549 — Cannot open session for %S_MSG '%.*ls'. Provider error code: %d. (%.*ls). For more information, see https://go.microsoft.com/fwlink/?linkid=2323435 .
- 37550 — Cannot initialize cryptographic provider. Provider error code: %d. (%.*ls). For more information, see https://go.microsoft.com/fwlink/?linkid=2323435 …
- 37551 — Cannot create key '%.*ls' in the provider. Provider error code: %d. (%.*ls). For more information, see https://go.microsoft.com/fwlink/?linkid=2323435…
- 37552 — Cannot export %S_MSG from the provider. Provider error code: %d. (%.*ls). For more information, see https://go.microsoft.com/fwlink/?linkid=2323435 .
- 37553 — Invalid algorithm '%.*ls'. Provider error code: %d. (%.*ls). For more information, see https://go.microsoft.com/fwlink/?linkid=2323435 .
- 37554 — Key with %S_MSG '%.*ls' does not exist in the provider or access is denied. Provider error code: %d. (%.*ls). For more information, see https://go.mic…
- 37555 — Invalid algorithm id: %d. Provider error code: %d. (%.*ls). For more information, see https://go.microsoft.com/fwlink/?linkid=2323435 .
- 37556 — Key validation failed since an attempt to get algorithm info for that key failed. Provider error code: %d. (%.*ls). For more information, see https://…
- 37557 — A server principal with the object ID '%ls' already exists with the name '%ls'.
- 37558 — A login with the object ID '%ls' already has an account with the user name '%ls'.
- 37559 — Object_id is not a valid option
- 37560 — Encryption scan cannot be suspended because it is already in suspended state.
- 37561 — Database encryption key cannot be altered because the database is not encrypted.
- 37562 — When key change is in progress, only suspend and resume operations are allowed.
- 37563 — The primary managed identity is not selected for this server. Enable the primary managed identity for Microsoft Entra authentication for this server. …
- 37564 — The managed identity with Client_ID/Application_ID '%ls', is the primary identity assigned for this server.
- 37565 — Microsoft Graph is currently experiencing a high volume of requests. Please wait for %d seconds and try again.
- 37566 — Operations on customer managed key '%s' are not allowed because the key has been disabled in Azure Key Vault '%s'. Please enable the key. For help res…
- 37567 — Operations on customer managed key '%s' are not allowed in Azure Key Vault '%s'. Please allow the following operations on the key: "get", "wrapKey", "…
- 37568 — One of required operations on customer managed key '%s' is not allowed for currently chosen RBAC role of the managed instance '%s' identity on Azure K…
- 37569 — Connection to Azure Key Vault '%s' was forbidden by Azure Key Vault firewall policy. Please review the Azure Key Vault firewall policy to enable conne…
- 37570 — One of required operations on customer managed key '%s' on Azure Key Vault '%s' is not allowed for currently set key vault policy used by managed inst…
- 37571 — Azure Key Vault '%s' operation requested by Managed Instance '%s' failed due to insufficient permissions (inner error code: '%s'). For help resolving …
- 37572 — Customer managed key '%s' was not found in Azure Key Vault '%s'. If it was recently deleted, recovery could be possible if 'soft-delete' protection is…
- 37573 — Connection to Azure Key Vault '%s' could not be established. Please review network settings for Managed Instance '%s'. For help resolving this issue, …
- 37574 — Azure Key Vault URI '%s' could not be resolved. Please ensure the key vault URI is valid and that your network settings for Managed Instance '%s' are …
- 37575 — SQL Server Audit [%ls] could not write to the Otel (OpenTelemetry) Audit Target (Error Code: %d).
- 37576 — The current version of SQL Server Connector for Microsoft Azure Key Vault does not support managed identity. Upgrade the SQL Server Connector to the l…
- 37577 — Current scenario is blocked for Fabric DW.
- 37578 — An internal error has occurred. Please retry the operation. If the issue persists, contact support for assistance.
- 37579 — The security policy '%.*ls' cannot reference tables with vector indexes. Table '%.*ls' has a vector index.
- 37580 — Principal '%.*ls' not found during implicit user creation, error detail: '%.*ls'.
- 37581 — Principal '%.*ls' had ambiguous match during implicit user creation, error detail: '%.*ls'.
- 37582 — Implicit user creation failed for principal '%.*ls' due to system error '%.*ls'.
- 37583 — An internal error occurred during %S_MSG %S_MSG. Please retry the operation. Error code: %d.
- 37584 — An internal error occurred while performing a cryptography operation. Operation: '%ls', status: 0x%08x.
- 37585 — Datawarehouse session internal error. If the issue persists, contact support for assistance.
- 37586 — Invalid AES key length %u.
- 37587 — Federated Managed Identity '%.*ls' cannot be created because a database principal with the same name already exists.
- 37588 — The field '%ls' or more specified in the REQUIRED_FIELDS audit option are invalid.
- 37589 — An internal VSM attestation service log while performing enclave attestation operation. Log Source: %d, message: '%ls'.
- 37590 — The system table '%s' cannot be used because it is not a valid Microsoft system table.
- 37591 — A duplicate field-name '%ls' specified in the REQUIRED_FIELDS audit option.
- 37592 — REQUIRED_FIELDS audit option cannot be an empty string.
- 37593 — The REQUIRED_FIELDS audit option exceeds the maximum allowed length of %d characters.
- 37594 — The REQUIRED_FIELDS audit option is only supported for EXTERNAL_MONITOR target.
- 37595 — The maximum number of HTTP redirect hops was exceeded while calling Azure Confidential Ledger. Ledger URL '%ls' and error code %ld.
- 37596 — The HTTP redirect target failed security validation while calling Azure Confidential Ledger. Ledger URL '%ls' and error code %ld.
- 37597 — User security synchronization failed due to system error '%.*ls'.
- 37598 — [%ls]: Exception: Error: %d, State: %d.
- 37599 — The number of column encryption keys sent by the client for enclave computations exceeds the maximum allowed limit of %d.
- 37601 — [Auditing][%ls] Could not allocate memory for %ls.
- 37602 — [Auditing][%ls] Error while reading AuditPolicy from WinFab property. [ErrorCode: %d].
- 37603 — [Auditing][%ls] The 'State' in AuditPolicy is 'UNKNOWN'. [ErrorCode: %d].
- 37604 — [Auditing][%ls] Error while constructing AuditQueryParameters from AuditPolicy. [ErrorCode: %d].
- 37605 — [Auditing][%ls] Could not configure auditing to %ls. DetailedMessage: [%ls]. [Error: %d].
- 37606 — [Auditing][%ls][Informational] Error while trying to get Audit Policy (%ls) from WinFab properties [ErrorCode: %d].
- 37607 — [Auditing][%ls][Informational] Property '[%ls]' under Namespace '[%ls]' failed to retrieve. [Error: %d].
- 37608 — [Auditing][%ls][Informational] Xpath [%ls] for WinFab Property '[%ls]' under Namespace '[%ls]' failed to retrieve. [Error: %d].
- 37609 — [Auditing][%ls][Informational] Property '[%ls]' under Namespace '[%ls]' has invalid value [Len: %lu] [Error: %d].
- 37610 — [Auditing][%ls][Informational] Property '[%ls]' under Namespace '[%ls]' is empty or null [Len: %lu] [Error: %d].
- 37611 — [Auditing][%ls] Could not combine paths. DetailedMessage: [%ls]. [path1: %ls] [path2: %ls] [separator: %lc] [Error: %d].
- 37612 — [Auditing][%ls] Error: One or more of 'baseStr', 'searchStr' is nullptr. [baseStr: %ls] [searchStr: %ls] [Error: %d].
- 37613 — [Auditing][%ls] Error: Length of 'searchStr' is zero [Error: %d].
- 37614 — [Auditing][%ls] Could not inject query parameter. [Parameter: %ls] [Value: %ls] [ErrorCode: %d].
- 37615 — [Auditing][%ls] Could not get query template. [auditQueryType: %ls] [ErrorCode: %d].
- 37616 — [Auditing][%ls] Could not inject parameters into audit query template. [auditQueryType: %ls] [ErrorCode: %d].
- 37617 — [Auditing][%ls] Error occurred while constructing %ls [ErrorCode: %d].
- 37618 — [Auditing][%ls] Could not generate audit query to execute. [auditQueryType: %ls] [ErrorCode: %d].
- 37619 — An unexpected error occurred. Please try again after some time. If the error persists, please contact Customer Support.
- 37620 — StartTimeFilter is not in a supported format. Please either use DEFAULT or a UTC based timestamp in this format - 'YYYY-MM-DDThh:mm:ssZ'. For example …
- 37621 — EndTimeFilter is not in a supported format. Please either use DEFAULT or a UTC based timestamp in this format - 'YYYY-MM-DDThh:mm:ssZ'. For example - …
- 37622 — The batch length (%d wchars) exceeds the maximum length supported by audit logging (%d wchars). Reduce the batch size and retry.
- 38001 — Cannot find the file id %d in the database '%s'.
- 38002 — Only users having %s permission can execute this stored procedure.
- 39001 — Only SELECT statement is supported for input data query to 'sp_execute_external_script' stored procedure.
- 39002 — SQL failed to boot extensibility for error code 0x%lx.
- 39003 — SQL successfully boots extensibility.
- 39004 — A '%s' script error occurred during execution of 'sp_execute_external_script' with HRESULT 0x%x.
- 39005 — STDOUT message(s) from external script: %.*ls%.*ls
- 39006 — External script execution status: %.*ls.
- 39007 — The specified language ': %.*ls' is not supported/configured.
- 39008 — Invlid Parameter name '%ls' specified for Procedure. This clashes with internal parameters.
- 39009 — Output parameter in external script execution is not yet supported.
- 39010 — External script execution encountered an unexpected error (HRESULT = 0x%x).
- 39011 — SQL Server was unable to communicate with the LaunchPad service. Please verify the configuration of the service.
- 39012 — Unable to communicate with the runtime for '%s' script. Please check the requirements of '%s' runtime.
- 39013 — SQL Server encountered error 0x%x while communicating with the '%s' runtime. Please check the configuration of the '%s' runtime.
- 39014 — Parallelism in external script execution is not yet supported.
- 39015 — SELECT INTO statement is not supported for input data query to 'sp_execute_external_script' stored procedure.
- 39016 — The parameterized external script expects the parameter '%.*ls', which was not supplied.
- 39017 — Input data query returns column #%d of type '%ls' which is not supported by the runtime for '%s' script. Unsupported types are binary, varbinary, time…
- 39018 — Parameter '%.*ls' uses a data type that is not supported by the runtime for '%s' script. Unsupported types are timestamp, datetime2, datetimeoffset, t…
- 39019 — An external script error occurred: %.*ls%.*ls
- 39020 — Feature 'Advanced Analytics Extensions' is not installed. Please consult Books Online for more information on this feature.
- 39021 — Unable to launch runtime for '%s' script. Please check the configuration of the '%s' runtime.
- 39022 — STDERR message(s) from external script: %.*ls%.*ls
- 39023 — 'sp_execute_external_script' is disabled on this instance of SQL Server. Use sp_configure 'external scripts enabled' to enable it.
- 39024 — Parallel execution of 'sp_execute_external_script' failed. Specify WITH RESULT SETS clause with output schema.
- 39025 — External script execution failed as extensibility environment is not ready yet. Retry the operation when the server is fully started.
- 39026 — The parameter name 'r_rowsPerRead' is specified multiple times in 'sp_execute_external_script' call. The name 'r_rowsPerRead' is reserved for specifyi…
- 39027 — Parameter '%.*ls' was specified multiple times to sp_execute_external_script stored procedure.
- 39029 — The external language '%.*ls' returned error messages: '%.*ls'.
- 39030 — Variable '%.*ls' has unsupported data type for parameter exchange in EXEC EXTERNAL LANGUAGE statement.
- 39031 — Cannot parse the output schema of the builtin function 'PREDICT'.
- 39032 — The function PREDICT expects parameters in the form of 'name = value'.
- 39033 — The parameter name '%.*ls' has already been declared. Parameter names must be unique in a PREDICT function call.
- 39034 — The parameter 'PARAMETERS' in PREDICT function contains a definition that doesn't match the supplied arguments.
- 39035 — The function PREDICT has too many arguments supplied.
- 39036 — The function PREDICT expects parameter '%.*ls' which was not supplied.
- 39037 — The function PREDICT contains a parameter '%.*ls' that has an invalid type.
- 39038 — The function PREDICT expects parameter 'PARAMETERS' of type ntext/nchar/nvarchar.
- 39039 — Error converting the parameter value for '%.*ls' to '%.*ls'.
- 39040 — The function 'PREDICT' does not support SQL identifier or variable for 'PARAMETERS'.
- 39041 — The parameter 'PARAMETERS' has an invalid definition.
- 39042 — %s EXTERNAL LIBRARY failed because the library source parameter %d is not a valid expression.
- 39043 — %s EXTERNAL LIBRARY failed because filename '%.*ls' is too long.
- 39044 — %s EXTERNAL LIBRARY failed because it could not open the physical file '%.*ls': %ls.
- 39045 — %s EXTERNAL LIBRARY failed because it could not read from the physical file '%.*ls': %ls.
- 39046 — CREATE EXTERNAL LIBRARY failed because the user "%.*ls" specified in the authorization clause does not exist.
- 39047 — External library '%.*ls' already exists for owner '%.*ls' in database '%.*ls'.
- 39048 — Failed to %s external library '%ls': %ls.
- 39049 — Message(s) from 'PREDICT' engine: %.*ls%.*ls
- 39050 — Error occurred during execution of the builtin function 'PREDICT' with HRESULT 0x%x. Out of memory.
- 39051 — Error occurred during execution of the builtin function 'PREDICT' with HRESULT 0x%x. Model is corrupt or invalid.
- 39052 — Error occurred during execution of the builtin function 'PREDICT' with HRESULT 0x%x. Model type is unsupported.
- 39053 — The function PREDICT expects parameter 'RUNTIME' of type ntext/nchar/nvarchar.
- 39054 — The 'RUNTIME' parameter is invalid.
- 39055 — %ls can only be called in combination with the OUTER APPLY clause.
- 39056 — Could not parse the list of columns to be passed to %ls. Only simple column references are accepted.
- 39057 — The value provided for the '%.*ls' parameter is too large.
- 39058 — The parameter '%.*ls' has a type that is not supported.
- 39092 — Initialization of native scoring libraries failed with HRESULT 0x%x.
- 39093 — 'PREDICT' function does not take parameters of varchar(max), nvarchar(max) or varbinary(max) type except for 'MODEL' parameter.
- 39094 — 'PREDICT' function only supports models smaller than 100 MB.
- 39096 — Execution failed because its WITH clause specified different output columns from what 'PREDICT' function tries to return. The schema returned by 'PRED…
- 39097 — Input data column #%d is of type '%ls' which is not supported by 'PREDICT' function. Unsupported types are binary, varbinary, timestamp, datetime2, da…
- 39098 — Error occurred during execution of the builtin function 'PREDICT' with HRESULT 0x%x.
- 39099 — Feature or option 'PREDICT' is not yet implemented. Please consult Books Online for more information on this feature or option.
- 39101 — '%.*ls' failed because it is not supported in the edition of this SQL Server instance.
- 39102 — Duplicate column names are not allowed in '%.*ls'. Column name '%.*ls' is a duplicate.
- 39103 — Parameter '@input_data_1_order_by_columns' is not allowed without parameter '@input_data_1_partition_by_columns'.
- 39104 — Column '%.*ls' in '%.*ls' is not defined in the SELECT clause of '@input_data_1' parameter.
- 39105 — Invalid syntax for parameter '@input_data_1_partition_by_columns'. Specify a list of comma separated columns.
- 39106 — Invalid syntax for parameter '@input_data_1_order_by_columns'. Specify a list of comma separated columns and an optional argument for sorting order <A…
- 39107 — Columns in parameters '@input_data_1_partition_by_columns' and '@input_data_1_order_by_columns' must be unique. Column name '%.*ls' appears in both pa…
- 39108 — Maximum number of concurrent external script users has been reached. Limit is %d. Please retry the operation. External script request id is %ls.
- 39109 — The combined total number of columns given in parameters '@input_data_1_partition_by_columns' and '@input_data_1_order_by_columns' exceeds the maximum…
- 39110 — Maximum number of concurrent external script queries for this user has been reached. Limit is %d. Please retry the operation. External script request …
- 39111 — The SQL Server Machine Learning Services End-User License Agreement (EULA) has not been accepted.
- 39112 — Duplicate file specification supplied for platform '%.*ls'.
- 39113 — Number of file specifications exceeds the maximum of %d.
- 39114 — CREATE EXTERNAL LIBRARY statement failed because of duplicate file specification. Only one file specification per platform is allowed in a CREATE EXTE…
- 39115 — ALTER EXTERNAL LIBRARY statement failed because the content for platform '%.*ls' does not exist or is not correctly defined in the external library.
- 39116 — ALTER EXTERNAL LIBRARY REMOVE PLATFORM statement failed because an external library requires at least one file specification to be defined.
- 39117 — %.*ls EXTERNAL LANGUAGE statement failed because the parameter '%s' is not a valid expression.
- 39118 — %s EXTERNAL LANGUAGE statement failed because the specified file path '%.*ls' is too long. Maximum length of file path is %d characters.
- 39119 — %s EXTERNAL LANGUAGE failed because it could not open the physical file '%.*ls': %ls.
- 39120 — %s EXTERNAL LANGUAGE statement failed because it could not read from the physical file '%.*ls': %ls.
- 39121 — CREATE EXTERNAL LANGUAGE statement failed because the user "%.*ls" specified in the authorization clause does not exist or have permission.
- 39122 — CREATE statement failed. External language '%.*ls' already exists.
- 39123 — %.*ls EXTERNAL LANGUAGE statement failed because the parameter '%s' is not specified.