New sys.messages Entries in SQL Server 2017

I’m only showing the English (1033) ones here, message ID and then text. Some of the new messages are very Azure-specific, and while I love to think that we’d get some of these features in the boxed product, I think Microsoft is just getting down to a standard shared list of message IDs.

However, some of them are rather…well, I’ll just bold the ones that made me raise an eyebrow:

  • 10147 – Cannot create %S_MSG on the view ‘%.*ls’ because it uses temporal FOR SYSTEM_TIME clause.
  • 10148 – Cannot create %S_MSG on the view ‘%.*ls’ because it uses OPENJSON.
  • 10149 – Index that has SNAPSHOT_MATERIALIZATION cannot be created on view ‘%.*ls’ because view definition contains memory-optimized table(s).
  • 10342 – Assembly ‘%.*ls’ cannot be loaded because this edition of SQL Server only supports SAFE assemblies.
  • 10343 – CREATE or ALTER ASSEMBLY for assembly ‘%.*ls’ with the SAFE or EXTERNAL_ACCESS option failed because the ‘clr strict security’ option of sp_configure is set to 1. Microsoft recommends that you sign the assembly with a certificate or asymmetric key that has a corresponding login with UNSAFE ASSEMBLY permission. Alternatively, you can trust the assembly using sp_add_trusted_assembly.
  • 10344 – Internal table access error: failed to access the Trusted Assemblies internal table with HRESULT: 0x%x. Contact Customer Support Services.
  • 10345 – The assembly hash ‘0x%.*ls’ is already trusted.
  • 10346 – The assembly hash ‘0x%.*ls’ is not currently trusted. No action was taken.
  • 10636 – Ignore in Optimization cannot be set for ‘%.*ls’ on ‘%.*ls.%.*ls’ because it is only applicable to non-clustered B-tree or columnstore indexes.
  • 10637 – Cannot perform this operation on ‘%.*ls’ with ID %I64d as one or more indexes are currently in resumable index rebuild state. Please refer to sys.index_resumable_operations for more details.
  • 10638 – ALTER INDEX ‘%S_MSG’ failed. There is no pending resumable index operation for the index ‘%.*ls’ on ‘%.*ls’.
  • 10639 – Resumable index operation for %S_MSG ‘%.*ls’ failed because the index contains column ‘%.*ls’ of type timestamp as a key column.
  • 10640 – Ignore in Optimization cannot be set for an index on ‘%.*ls.%.*ls’ because it is only applicable to indexes on user defined disk-based tables.
  • 10641 – ALTER INDEX PAUSE failed. There is no actively running resumable index operation for the index ‘%.*ls’ on ‘%.*ls’.
  • 10642 – SNAPSHOT_MATERIALIZATION cannot be set for index ‘%.*ls’ on ‘%.*ls’ because it is only applicable to indexes on views.
  • 10643 – SNAPSHOT_MATERIALIZATION cannot be set for ‘%.*ls’ on ‘%.*ls’ because it is only applicable to clustered indexes on views.
  • 10644 – Resumable index operation for %S_MSG ‘%.*ls’ failed because the index contains the computed column ‘%.*ls’ as a key or partitioning column. If this is a non clustered index, the column will be implicitly included as a key column if it is part of the clustered index key.
  • 10645 – Warning: An existing resumable operation with the same options was identified for the same index on ‘%.*ls’. The existing operation will be resumed instead.
  • 10646 – Index ‘%.*ls’ on view ‘%.*ls’ that has SNAPSHOT_MATERIALIZATION cannot be dropped using the DROP_EXISTING option.
  • 10647 – Index ‘%.*ls’ on ‘%.*ls’ that has SNAPSHOT_MATERIALIZATION cannot be altered.
  • 10648 – SNAPSHOT_MATERIALIZATION cannot be set for partitioned index ‘%.*ls’ on ‘%.*ls’.
  • 10649 – Nonclustered index ‘%.*ls’ cannot be created on ‘%.*ls’ that has clustered index ‘%.*ls’ with SNAPSHOT_MATERIALIZATION.
  • 10650 – Refresh of snapshot view(s) requires snapshot isolation to be enabled on the database.
  • 10651 – Refresh of snapshot view failed because view ‘%.*ls.%.*ls’ does not exist.
  • 10652 – Refresh of snapshot view failed because ‘%.*ls.%.*ls’ is not a snapshot view.
  • 10653 – Refresh of snapshot view failed.
  • 10654 – Refresh of snapshot view failed because lock could not be obtained on the database.
  • 10655 – Refresh of snapshot view failed because view is not specified in two-part name format.
  • 10656 – The resumable index operation for index ‘%.*ls’ on object ‘%.*ls’ was paused.
  • 10657 – The resumable index ‘%.*ls’ on object ‘%.*ls’ has been paused for ‘%.2f’ hours.
  • 10658 – Stored procedure ‘%ls’ is currently disabled.
  • 10659 – An ALTER INDEX ‘%S_MSG’ was executed for index ‘%.*ls’ on object ‘%.*ls’ by hostname ‘%.*ls’.
  • 10712 – The pseudocolumn ‘%.*ls’ cannot be part of an index.
  • 10719 – Foreign key relationships from a memory optimized table with DURABILITY set to SCHEMA_AND_DATA to a memory optimized table with DURABILITY set to SCHEMA_ONLY are not supported.
  • 10936 – Resource ID : %d. The %ls limit for the elastic pool is %d and has been reached. See ‘http://go.microsoft.com/fwlink/?LinkId=267637’ for assistance. (Note from Brent – remember, this message is in the on-premises boxed product.)
  • 10937 – Default workload group does not allow to alter attribute ‘%.*ls’.
  • 1104 – TEMPDB ran out of space during spilling. Create space by dropping objects and/or rewrite the query to consume fewer rows. If the issue still persists, consider upgrading to a higher service level objective.
  • 11431 – The %S_MSG option is not permitted as the %S_MSG option is not turned ‘%ls’.
  • 11432 – %S_MSG = %d is not a valid value; %S_MSG must be greater than 0 and less than %d.
  • 11433 – ‘%.*ls’ with %S_MSG option is not suppported on %S_MSG ‘%.*ls’.
  • 11434 – The %S_MSG option is not supported for the disabled index ‘%.*ls’ on %S_MSG ‘%.*ls’.
  • 11435 – The %S_MSG option is not supported for Heaps at %S_MSG ‘%.*ls’.
  • 11436 – Cannot alter table ‘%.*ls’ because non-nullable column ‘%.*ls’ cannot be declared as hidden without either a DEFAULT constraint, the GENERATED ALWAYS attribute, or the IDENTITY attribute.
  • 11437 – Cannot alter table ‘%.*ls’ because at least one column must be declared as non-hidden.
  • 11438 – The %S_MSG option cannot be set to ‘%ls’ when the %S_MSG option is set to ‘%ls’.
  • 11557 – The stored procedure ‘sp_get_jobs_database_scoped_credential’ is not available.
  • 11558 – The distributed_move JSON string could not be parsed. Please check the formatting of the JSON.
  • 11559 – The distributed_move JSON parameter %.*ls is missing or incorrectly formatted. Please check the formatting of the JSON.
  • 11560 – The distributed_move parameter %.*ls value is outside its valid range. Please try again with a valid parameter.
  • 11903 – Cannot create table ‘%.*ls’ because non-nullable column ‘%.*ls’ cannot be declared as hidden without either a DEFAULT constraint, the GENERATED ALWAYS attribute, or the IDENTITY attribute.
  • 11904 – Cannot create table ‘%.*ls’ because at least one column must be declared as non-hidden.
  • 11905 – Resumable index operations can only be performed in Enterprise edition of SQL Server.
  • 12110 – Statement ‘%.*ls’ failed, because it attempted to set the ‘%.*ls’ option for the secondaries replica while this option is only allowed to be set for the primary.
  • 12352 – System stored procedures that cause schema changes to %S_MSG are not supported inside user transactions.
  • 12353 – Computed columns in indexes on memory optimized tables must be declared as PERSISTED.
  • 12354 – The function %ls with an argument in a Japanese_140 collation is currently not supported with %S_MSG.
  • 12355 – The persistence of a computed column in a memory optimized table cannot be altered. Drop and re-create the column with the desired persistence.
  • 12445 – Cannot set Query Store max_storage_size_mb to %lu. The maximum allowed limit is %lu MB.
  • 12446 – Query Store stored procedure is not available on readable secondary replica.
  • 12447 – Query plan with plan_id (%ld) cannot be forced for query with query_id (%ld) as plan forcing is not supported for this type of statement.
  • 12449 – Query plan cannot be forced for this query as plan forcing is not supported for resumable index builds.
  • 12500 – SELECT INTO not allowed in the CTAS statement.
  • 12501 – Different number of columns in CREATE TABLE and SELECT query.
  • 12502 – Data types cannot be defined using CREATE TABLE AS SELECT syntax.
  • 12503 – Specifying schema elements in the CREATE SCHEMA statement is not supported.
  • 12504 – Distribution column ‘%.*ls’ must be implictly or explictly specified in the insert select query as the target table ‘%.*ls’ is a hash distributed table.
  • 12701 – Failed to lock external data source object (EDS name: %.*ls). Lock Mode: %.*ls.
  • 12702 – Failed to lock external data source manager. Lock Mode: %.*ls.
  • 12703 – Referenced external data source “%ls” not found.
  • 12704 – Bad or inaccessible location specified in external data source “%ls”.
  • 12705 – Referenced external data source “%ls” type is “%ls”. Please use BLOB_STORAGE type to reference Azure Blob Storage locations.
  • 12844 – ALTER DATABASE statement failed; this functionality is not available in the current edition of SQL Server.
  • 13327 – external library
  • 13328 – QUERY_TUNING_MODE
  • 13329 – QDS server name
  • 13330 – WAIT_STATS_CAPTURE_MODE
  • 13764 – Online alter column is not supported for system-versioned temporal table ‘%.*ls’.
  • 13765 – Setting finite retention period failed on system-versioned temporal table ‘%.*ls’ because the history table ‘%.*ls’ does not contain required clustered index. Consider creating a clustered columnstore or B-tree index starting with the column that matches end of SYSTEM_TIME period, on the history table.
  • 13766 – Cannot drop the clustered index ‘%.*ls’ because it is being used for automatic cleanup of aged data. Consider setting HISTORY_RETENTION_PERIOD to INFINITE on the corresponding system-versioned temporal table if you need to drop this index.
  • 13767 – The clustered index ‘%.*ls’ is being used for automatic cleanup of aged data, and can be converted to either a clustered columnstore or B-tree index starting with the column that matches end of SYSTEM_TIME period, on the history table. Consider setting HISTORY_RETENTION_PERIOD to INFINITE on the corresponding system-versioned temporal table if you need to rebuild this index with a modified column specification, not supported with temporal history retention.
  • 13768 – Retention cleanup of history table for a temporal table (database id %lu, table id %ld) has not been executed. Either the cleanup is disabled on the database, appropriate lock could not be obtained or the temporal table does not exist anymore.
  • 13769 – Setting SYSTEM_VERSIONING to ON failed for table ‘%.*ls’ because ‘%.*ls’ with REMOTE_DATA_ARCHIVE enabled cannot be used as a history table when a finite retention period is specified.
  • 13770 – Setting finite retention period failed on system-versioned temporal table ‘%.*ls’ because REMOTE_DATA_ARCHIVE is enabled on the corresponding history table ‘%.*ls’.
  • 13771 – Setting finite retention period failed on system-versioned temporal table ‘%.*ls’ because corresponding history table ‘%.*ls’ has both clustered columnstore and non-clustered indexes. Consider dropping non-clustered indexes from the history table and try again.
  • 13772 – Cannot create non-clustered index on temporal history table ‘%.*ls’ since it has finite retention period and clustered columnstore index defined.
  • 13773 – Clustered column store temporal retention cleanup attempted on non-clustered column store table ‘%.*ls’.
  • 13776 – Table ‘%.*ls’ does not exist or you do not have the required permissions to complete the operation.
  • 13777 – Stored procedure ‘sp_cleanup_temporal_history’ is temporarily disabled. Please contact customer support for more information.
  • 13778 – The only allowed ALTER TABLE operations on temporal in-memory history table ‘%.*ls’ are ADD INDEX, DROP INDEX and ALTER INDEX.
  • 13779 – Defining a column store index on temporal in-memory history table ‘%.*ls’ is not supported.
  • 13780 – Setting finite retention period failed on system-versioned temporal table ‘%.*ls’ beacause the history table ‘%.*ls’ is clustered column store that contains large object columns.
  • 13781 – Wrong type for column ‘%.*ls’: the system-versioned temporal table ‘%.*ls’ cannot contain large object columns, because it has finite retention and the clustered column store history table ‘%.*ls’.
  • 13782 – Cannot create clustered column store index ‘%.*ls’ on table ‘%.*ls’ because it contains large object columns and is the history table of temporal table ‘%.*ls’ that has finite retention.
  • 13783 – Data modification failed on system-versioned table ‘%.*ls’ because column ‘%.*ls’ cannot be output into the history table ‘%.*ls’.
  • 13800 – Insert bulk statement does not support recompile.
  • 13900 – Identifier ‘%.*ls’ in a MATCH clause could not be bound.
  • 13901 – Identifier ‘%.*ls’ in a MATCH clause is not a node table or an alias for a node table.
  • 13902 – Identifier ‘%.*ls’ in a MATCH clause is not an edge table or an alias for an edge table.
  • 13903 – Edge table ‘%.*ls’ used in more than one MATCH pattern.
  • 13904 – All node and edge tables within a single MATCH clause must reside in the same database.
  • 13905 – A MATCH clause may not be directly combined with other expressions using OR or NOT.
  • 13906 – A MATCH clause is only permitted in a WHERE clause or in the ON clause of a GRAPH JOIN.
  • 13907 – Cannot modify permissions for graph column ‘%.*s’.
  • 13908 – Cannot access internal graph column ‘%.*ls’.
  • 13909 – The internal graph column ‘%.*ls’ cannot be added to an index; use pseudocolumn ‘%.*ls’ instead.
  • 13910 – Cannot create a node or edge table as memory optimized.
  • 13911 – Cannot create a node or edge table as a remote data archive.
  • 13912 – A node or edge table cannot be created as or altered to a temporal table.
  • 13913 – Internal graph columns cannot be altered.
  • 13914 – Cannot create a node or edge table as a temporary table.
  • 13915 – Cannot create a node or edge table as an external table.
  • 13916 – The graph column ‘%.*ls’ cannot be used as a non-key column in an index.
  • 13917 – After expanding the computed graph column ‘%.*ls”, the index ‘%.*ls’ on table ‘%.*ls’ exceeds the maximum number of columns in the key list. The maximum number of index key columns is %d.
  • 13918 – Adding constraint to column ‘%.*s’ of a node or edge table is not allowed.
  • 13919 – Identifier ‘%.*ls’ in a MATCH clause corresponds to a derived table. Derived tables are not supported in MATCH clauses.
  • 13920 – Identifier ‘%.*ls’ in a MATCH clause is used with a JOIN clause or APPLY operator. JOIN and APPLY are not supported with MATCH clauses.
  • 13921 – JSON data for INSERT/UPDATE of graph pseudocolumn ‘%.*ls’ is malformed.
  • 13922 – Remote tables are not supported in MATCH clauses.
  • 13923 – Pseudocolumn ‘%.*s’ is invalid because it references a node or edge table that is not in the current database.
  • 13924 – Select * is not permitted because it refers to a node or edge table ‘%.*s’ which is not in the current database.
  • 13925 – Cannot drop or disable index or constraint ‘%.*s’ because the last unique index or constraint on ‘%.*s’ cannot be dropped or disabled.
  • 13926 – The use of replication is not supported for node or edge table ‘%ls’.
  • 13927 – Change Data Capture is not supported for node or edge table ‘%ls’.
  • 13928 – Use pseudocolumn ‘%.*ls’ to add a constraint on a node or edge table.
  • 13929 – The pseudocolumn ‘%.*ls’ cannot be part of an index unless the index is on a node or edge table that contains that pseudocolumn.
  • 15701 – Statement ‘%.*ls’ failed, because it attempted to set the Automatic Tuning option ‘%.*ls’ multiple times.
  • 15702 – Cannot perform action because Automatic Tuning cannot be enabled on system database %.*ls.
  • 15703 – Setting Automatic Tuning option ‘%.*ls’ to %.*ls for database ‘%.*ls’.
  • 15704 – Automatic Tuning option ‘%.*ls’ is disabled by system.
  • 15705 – Automatic Tuning option %.*ls cannot be enabled, because Query Store is not turned on.
  • 15706 – Automatic Tuning option %.*ls cannot be enabled, because Query Store is in READ_ONLY mode.
  • 15707 – Automatic Tuning is only available for enterprise customers. (Note from Brent: that’s interesting wording. Usually they call it Enterprise Edition because even enterprise customers run Standard Edition.)
  • 15716 – Only one Automatic Tuning option can be given in ALTER DATABASE statement.
  • 16202 – Keyword or statement option ‘%.*ls’ is not supported on the ‘%.*ls’ platform.
  • 16601 – Credential of database ‘%ls’ are invalid.
  • 16602 – Cannot delete sync agent ‘%ls’ because it is used by sync member ‘%ls’.
  • 16603 – Cannot add database ‘%ls’ into sync group because the database name is invalid.
  • 16604 – Hub database ‘%ls’ is invalid. (Note from Brent: these sync/hub/member messages are related to SQL Data Sync.)
  • 16605 – Member database ‘%ls’ is invalid.
  • 16606 – Database ‘%ls’ cannot be deleted because it is used as a sync metadata database which still contains sync groups and/or sync agents.
  • 16607 – Sync metadata database ‘%ls’ is invalid.
  • 16608 – Cannot create or update sync group because the sync group name ‘%ls’ is invalid.
  • 16609 – Cannot create or update sync group ‘%ls’ because the conflict resolution policy is invalid.
  • 16610 – Cannot create sync group because the sync group name ‘%ls’ is used.
  • 16611 – Cannot create or update sync group ‘%ls’ because the sync schema contains circular reference.
  • 16612 – Cannot create or update sync group ‘%ls’ because the table ‘%ls’ in sync schema contains no clustered index.
  • 16613 – Cannot delete sync group ‘%ls’ because the sync group is syncing.
  • 16614 – Cannot create or update sync group ‘%ls’ because database ‘%ls’ is invalid.
  • 16615 – Cannot create or update sync group ‘%ls’ because the sync interval is invalid.
  • 16616 – Cannot update sync schema because the data type change is not supported.
  • 16617 – Sync group ‘%ls’ is not ready to update sync schema because there are some ongoing operations on the sync group.
  • 16618 – Cannot update sync schema because some columns are missing in database ‘%ls’.
  • 16619 – Cannot update sync schema because some tables are missing in database ‘%ls’.
  • 16620 – Cannot update sync schema because the format of sync schema is invalid.
  • 16621 – Sync group ‘%ls’ is not in active state. Make sure the sync schema of it is set.
  • 16622 – Hub database ‘%ls’ is suspended because the credential of it is invalid.
  • 16623 – Sync group ‘%ls’ is invalid.
  • 16624 – Cannot create or update sync member because the sync member name ‘%ls’ is invalid.
  • 16625 – Cannot create or update the sync member ‘%ls’ because the database type ‘%ls’ provided is invalid.
  • 16626 – Cannot create or update the sync member ‘%ls’ because the sync direction ‘%ls’ provided is invalid.
  • 16627 – Cannot create or update the sync member ‘%ls’ because the sync agent ‘%ls’ provided is invalid.
  • 16628 – Cannot create or update the sync member ‘%ls’ because the SQL Server database ID ‘%ls’ provided is invalid.
  • 16629 – Cannot create sync member because the sync member name ‘%ls’ provided is used.
  • 16630 – Cannot create sync member ‘%ls’ because the database ‘%ls’ provided is already added as a sync member.
  • 16631 – Cannot delete sync member ‘%ls’ when it is syncing.
  • 16632 – Sync member ‘%ls’ is invalid.
  • 16633 – Cannot create sync agent because the sync agent name ‘%ls’ provided is used.
  • 16634 – Sync agent ‘%ls’ is invalid.
  • 16635 – Cannot create sync group ‘%ls’ because the maximum number of sync groups can be created is %d.
  • 16636 – Cannot create sync member ‘%ls’ because the maximum number of sync members can be created in a sync group is %d.
  • 16637 – Cannot create or update sync group ‘%ls’ because the maximum count of tables in sync schema is %d.
  • 16638 – Cannot create or update sync group ‘%ls’ because the table ‘%ls’ in sync schema contains no primary key.
  • 16639 – Cannot create or update sync group ‘%ls’ because the sync schema provided contains unsupported column data type.
  • 16640 – Cannot refresh schema of the database ‘%ls’.
  • 16641 – Cannot create sync agent ‘%ls’ under a different SQL Server than the one of sync metadata database.
  • 1735 – Duplicate range-partitioning function specified for the table being created. Remove one of the range-partitioning function specifications and resubmit the request.
  • 1737 – Duplicate distribution clause specified for the table being created. Remove one of the distribution clauses and resubmit the request.
  • 17900 – A network error occurred in the established connection; the connection has been closed.
  • 22119 – Cannot enable change tracking on table ‘%.*ls’. Change tracking requires a primary key constraint on the table to be enabled. Enable the primary key constraint on the table before enabling change tracking.
  • 22120 – Invalid value for cleanup batch size.
  • 22121 – Deleted %ld row(s) per millisecond from %s
  • 22845 – Cannot enable change data capture in this edition of SQL Server.
  • 25748 – The file “%s” contains audit logs. Audit logs can only be accessed by using the fn_get_audit_file function.
  • 27242 – Cannot find the cluster execution job instance ‘%ls’ because it does not exist or you do not have sufficient permissions. (Note from Brent – this range of messages below appears to be related to SSIS scale-out.)
  • 27243 – Cannot find the cluster worker agent ‘%ls’ because it does not exist or you do not have sufficient permissions.
  • 27246 – Cannot find the cluster execution task instance ‘%ls’ because it does not exist or you do not have sufficient permissions.
  • 27251 – Cannot add a worker agent to execute the cluster job instance ‘%ls’ because the job is specified for all worker agents.
  • 27252 – The Integration Services cluster worker agent ‘%ls’ is disabled.
  • 27255 – The job id of the execution is null. Create a job for the execution first and try again.
  • 27256 – The event message does not exist.
  • 27257 – There is no active worker agent.
  • 27259 – Failed to enable worker agent because current SQL Server edition only support limited number of worker agents.
  • 27260 – Only members of sysadmin server roles can perform this action.
  • 27261 – There is no Scale Out Master installed.
  • 31021 – Could not get winfab log directory when performing DTA tuning related task.
  • 31022 – Could not get winfab data package directory when performing DTA tuning related task.
  • 31204 – Operation %ls is not supported on the %ls platform. (Note from Brent: don’t go assuming this means you can’t do it on Linux, ha ha ho ho. Could be the other way around.)
  • 32056 – The SQL Server failed to create full-text FTData directory. This might be because FulltextDefaultPath is invalid or SQL Server service account does not have permission. Full-text may fail until this issue is resolved. Restart SQL Server after the issue is fixed.
  • 3228 – Writing snapshot metadata to backup set for file “%ls” failed due to invalid format.
  • 3259 – Failed to copy blob with name ‘%ls’, to destination ‘%ls’. Error returned ‘%ls’.
  • 33061 – The specified RETENTION_DAYS value is greater than the maximum value allowed. The retenton days value must be less than %d days.
  • 33062 – Password validation failed. The password does not meet SQL Server password policy requirements because it is too short. The password must be at least %d characters.
  • 33063 – Password validation failed. The password does not meet SQL Server password policy requirements because it is too long. The password must be at most %d characters.
  • 33064 – Password validation failed. The password does not meet SQL Server password policy requirements because it is not complex enough. The password must be at least %d characters long and contain characters from three of the following four sets: Uppercase letters, Lowercase letters, Base 10 digits, and Symbols.
  • 33066 – An error occurred while configuring the password policy: NTSTATUS 0x%x, state %d. To skip configuring the password policy, use trace flag -T4634 during startup. This will cause SQL Server to run using a minimal password policy.
  • 33179 – Searching for ‘%.*ls’ only searches “‘%.*ls'” for SQL Server authentication logins.
  • 33180 – Searching for “‘%.*ls'” only searches for Azure Active Directory users. To search for a SQL Server authentication login, add the server name at the end. For example [%.*ls@%.*ls].
  • 33181 – The new owner cannot be Azure Active Directory group.
  • 33182 – The command must be executed on the target database ‘%.*ls’.
  • 33183 – The Azure Key Vault client encountered an error with message ‘%s’.
  • 33184 – An error occurred while obtaining information for the Azure Key Vault client with message ‘%s’.
  • 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 re-create to change the EDS name.
  • 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 file is missing.
  • 3461 – Failed to wait for XTP %ls to complete during recovery.
  • 35248 – The %ls operation is not allowed by the current availability-group configuration. The required_synchronized_secondaries_to_commit %d is greater than the %d possible secondary synchronous-commit availability replicas in availability group ‘%.*ls’. Change one of the existing asynchronous-commit replicas to the synchronous-commit availability mode, and retry the operation.
  • 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 with clustered columnstore index.
  • 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 workload group and resource pool. Please rerun query at a higher resource class, and also consider increasing DWU size. See ‘https://aka.ms/sqldw_columnstore_memory‘ for assistance.
  • 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 persists, consider upgrading to a higher service level objective. (Note from Brent – remember, this is on-premises. Given the number of Azure-specific messages in here, I’m going to stop noting these – they’re probably just getting down to a single set of messages across both the boxed product and Azure SQL DB.)
  • 35388 – The statement failed because column ‘%.*ls’ on table ‘%.*ls’ is a persisted computed column. Adding persisted computed columns to an existing clustered columnstore index is not supported.
  • 35389 – The statement failed because column ‘%.*ls’ on table ‘%.*ls’ is a computed column of a LOB type. Columnstore indexes cannot include computed columns of LOB types.
  • 35390 – Computed columns in columnstore indexes are temporarily disabled. Please rewrite your query to exclude computed columns.
  • 35392 – The statement failed because column ‘%.*ls’ on table ‘%.*ls’ is a computed column. Nonclustered index with computed column as key or included column cannot be created on a table that has a clustered columnstore index.
  • 35504 – server encryption protector
  • 35505 – RESUMABLE
  • 35506 – MAX_DURATION
  • 35507 – Storage
  • 35508 – RESUME
  • 35509 – PAUSE
  • 35510 – ABORT
  • 3643 – The operation elapsed time exceeded the maximum time specified for this operation. The execution has been stopped.
  • 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.
  • 3757 – WAIT_AT_LOW_PRIORITY clause is not permitted without ONLINE = ON option, for drop clustered %S_MSG ‘%.*ls’ on Table ‘%.*ls’.
  • 3758 – Multiple %S_MSG cannot be dropped when WAIT_AT_LOW_PRIORITY clause is specified.
  • 3759 – %.*ls constraint ‘%.*ls’ cannot be dropped when WAIT_AT_LOW_PRIORITY clause is used.
  • 3760 – Cannot drop index ‘%.*ls’ on view ‘%.*ls’ that has SNAPSHOT_MATERIALIZATION.
  • 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.
  • 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 ‘PREDICT’ function is ‘%ls’.
  • 39097 – Input data column #%d is of type ‘%ls’ which is not supported by ‘PREDICT’ function. Unsupported types are binary, varbinary, timestamp, datetime2, datetimeoffset, time, text, ntext, image, hierarchyid, xml, sql_variant and user-defined type.
  • 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.
  • 40555 – ‘%ls’ is not supported for this database. See Books Online for more details on feature support in different service tiers of Windows Azure SQL Database.
  • 40912 – The value for custom backup retention in days must be between %d and %d
  • 40913 – Windows Azure SQL Database supports a maximum of %d Virtual Network firewall rules. (Note from Brent – see what I mean about Azure-specific messages? I really doubt SQL Server is going to get this exact message on-premises. Microsoft’s just shipping one sys.messages table to rule them all.)
  • 40914 – Cannot open server ‘%.*ls’ requested by the login. Client from a Virtual Network with Service Tunneling is not allowed to access the server.
  • 40915 – Secondary server specified in a Failover Group cannot reside in the same region (Note from Brent – this & the below messages are Azure-specific. It’s possible they could bring this functionality down on-premises, though, if we were given a set of tools to manage the geographic locations of servers. Not likely.)
  • 40916 – The Failover Group ‘%.*ls’ already exists on server ‘%.*ls’
  • 40917 – The Failover Group ‘%.*ls’ does not exist on server ‘%.*ls’
  • 40918 – The Failover Group ‘%.*ls’ is busy with another operation and cannot perform ‘%.*ls’ operation. Please try again later
  • 40919 – The server ‘%.*ls’ is currently the primary server in the Failover Group and cannot initate failover
  • 40920 – The database ‘%.*ls’ is already included in another Failover Group
  • 40921 – The operation to add database ‘%.*ls’ to Failover Group is in progress, please wait for this operation to finish
  • 40922 – The operation to remove database ‘%.*ls’ from Failover Group is in progress, please wait for this operation to finish
  • 40923 – The database ‘%.*ls’ is a secondary in an existing geo-replication relationship and cannot be added to the Failover Group
  • 40924 – The operation cannot be performed due to multiple errors: ‘%.*ls’
  • 40925 – Can not connect to the database in its current state.
  • 40926 – The operation cannot be performed because the geo-replication link is part of a Failover Group. You must remove the database from the group in order to individually terminate or failover.
  • 40927 – The endpoint ‘%.*ls’ is already in use. Use a different Failover Group name.
  • 40928 – Create or update Failover Group operation successfully completed; however, some of the databases could not be added to or removed from Failover Group: ‘%.*ls’
  • 40929 – The source database ‘%ls.%ls’ cannot have higher edition than the target database ‘%ls.%ls’. Upgrade the edition on the target before upgrading source.
  • 40930 – The target database ‘%ls.%ls’ cannot have lower edition than the source database ‘%ls.%ls’. Downgrade the edition on the source before downgrading target.
  • 40931 – Failover Group name ‘%.*ls’ cannot be empty or null. It can only be made up of lowercase letters ‘a’-‘z’, the numbers 0-9 and the hyphen. The hyphen may not lead or trail in the name.
  • 40932 – The elastic pool cannot change its service tier since one or more of its databases use memory-optimized objects.
  • 40933 – The edition ‘%.*ls’ does not support the database tempdb max size ‘%.*ls’.
  • 41662 – Database ‘%ls’ (ID %d) of Windows Fabric partition ‘%ls’ (partition ID ‘%ls’) hit exception while running async tasks in Generic Subscriber.
  • 41663 – Failed to parse datawarehouse columnar cache settings during replica manager startup.
  • 41806 – Parameter “%ls” specified for procedure or function “%ls” is not valid.
  • 41838 – Failed to retrieve size for this file due to an internal error. Please try again later.
  • 41840 – Could not perform the operation because the elastic pool has reached its quota for in-memory tables. See ‘http://go.microsoft.com/fwlink/?LinkID=623028’ for more information.
  • 41841 – Found inconsistent boot-page for database ‘%.*ls’.
  • 41842 – Too many rows inserted or updated in this transaction. You can insert or update at most 4,294,967,294 rows in memory-optimized tables in a single transaction.
  • 41843 – Unable to construct segment for segment table.
  • 41844 – Clustered columnstore indexes are not supported on memory optimized tables with computed columns.
  • 41845 – Checksum verification failed for memory optimized checkpoint file %.*ls.
  • 41846 – Memory optimized checkpoint table consistency error detected. Checkpoint %I64d does not have unique recoverLsn. PrevLSN = (%I64d:%hu), CurrLSN = (%I64d:%hu).
  • 41847 – Memory optimized checkpoint table consistency error detected. Checkpoint %I64d does not point to a transaction segment definition record.
  • 41848 – Memory optimized checkpoint table consistency error detected. Checkpoint %I64d does not have ascending recoverLsn. PrevLSN = (%I64d:%hu), CurrLSN = (%I64d:%hu).
  • 41849 – Memory optimized segment table consistency error detected. Segments are not contiguous in logical space. Older Segment CkptId = %I64d, LsnInfo = (%I64d:%hu), TxBegin = %I64d, TxEnd = %I64d. Newer Segment CkptId = %I64d, LsnInfo = (%I64d:%hu), TxBegin = %I64d, TxEnd = %I64d.
  • 41850 – Memory optimized segment table consistency error detected. Segments are not well formed for Segment CkptId = %I64d, LsnInfo = (%I64d:%hu), TxBegin = %I64d, TxEnd = %I64d.
  • 41851 – Memory optimized segment table consistency error detected. Segment definition ordering does not match the (strict) logical ordering. Older Segment CkptId = %I64d, LsnInfo = (%I64d:%hu), TxBegin = %I64d, TxEnd = %I64d. Newer Segment CkptId = %I64d, LsnInfo = (%I64d:%hu), TxBegin = %I64d, TxEnd = %I64d.
  • 41852 – Memory optimized segment table consistency error detected. Segment has a NullHkLsn. CkptId = %I64d, Segment LsnInfo = (%I64d:%hu)
  • 41853 – Memory optimized segment table consistency error detected. Current segment goes backward further than the definition record of the N-2 segment. Older Segment CkptId = %I64d, LsnInfo = (%I64d:%hu), TxBegin = %I64d, TxEnd = %I64d. Newer Segment CkptId = %I64d, LsnInfo = (%I64d:%hu), TxBegin = %I64d, TxEnd = %I64d.
  • 41854 – Memory optimized file consistency error detected. An in use file with FileId %.*ls is referenced by the Checkpoint File Table but is not accounted for in the Storage Interface.
  • 41855 – Memory optimized file consistency error detected. Could not find a file with FileId %.*ls in the File Watermark Table visible by checkpoint ID %u.
  • 41856 – Memory optimized file consistency error detected. A file with FileId %.*ls of size %I64d bytes is smaller than expected %I64d bytes.
  • 41857 – Memory optimized file consistency error detected. A presumably in use file with FileId %.*ls was not found in the Checkpoint File Table.
  • 41858 – Memory optimized file consistency error detected. A presumably in use file with FileId %.*ls was not found in the File Watermark Table.
  • 41859 – Memory optimized file consistency error detected. A presumably in use file with FileId %.*ls of size %I64d bytes is smaller than expected (%I64d bytes)
  • 41860 – Memory optimized file consistency error detected. A presumably unused file with FileId %.*ls was found in the Checkpoint File Table.
  • 41861 – Memory optimized large rows table consistency error detected. File Id is %.*ls. Corresponding LSN range is not ascending. Begin Lsn is (%I64d:%hu), End Lsn is (%I64d:%hu).
  • 41862 – Memory optimized large rows table consistency error detected. Corresponding File %.*ls not found in File Table. Begin Lsn is (%I64d:%hu), End Lsn is (%I64d:%hu).
  • 41863 – Checkpoint %I64d points to a root file %.*ls which was in use by a more recent checkpoint.
  • 41864 – Checkpoint %I64d has a file %.*ls which has a watermark (%I64d) larger than the more recent checkpoints watermark (%I64d).
  • 41865 – File %.*ls does not have a pair file %.*ls
  • 41866 – Unprocessed File %.*ls does not have a pair file which is also unprocessed. Processed pair file is %.*ls.
  • 41867 – Consistency errors detected in the MEMORY_OPTIMIZED_DATA filegroup. See preceding error messages for details. Consult https://go.microsoft.com/fwlink/?linkid=845604 for details on how to recover from the errors.
  • 41868 – Memory optimized filegroup checks could not be completed because of system errors. See errorlog for more details. (Note from Brent – hallelujah, are we finally getting CHECKDB for in-memory OLTP?)
  • 41901 – One or more of the options (%ls) are not supported for this statement in SQL Managed Instance. Review the documentation for supported options.
  • 41902 – Unsupported device type. SQL Managed Instance supports database restore from URI backup device only. (Note from Brent: well, now, that’s interesting to see Managed Instance messages in here given that the product hasn’t officially hit production yet, only preview.)
  • 41903 – CREATE DATABASE failed. Cannot create filename %ls. Local file paths are not supported.
  • 4199 – Argument value %d is invalid for argument %d of %ls function.
  • 42033 – Updating Layered AG Configuration failed.
  • 4221 – Login to read-secondary failed due to long wait on ‘HADR_DATABASE_WAIT_FOR_TRANSITION_TO_VERSIONING’. The replica is not available for login because row versions are missing for transactions that were in-flight when the replica was recycled. The issue can be resolved by rolling back or committing the active transactions on the primary replica. Occurrences of this condition can be minimized by avoiding long write transactions on the primary.
  • 43001 – ‘%.*ls’ is not a valid login name.
  • 43002 – Storage in MB %d exceeds the maximum limit %d.
  • 43003 – More than one firewall rules have the same name ‘%.*ls’.
  • 43004 – ‘%.*ls’ is not a valid firewall rule name because it contains invalid characters.
  • 43005 – ‘%.*ls’ is not a valid database name because it contains invalid characters.
  • 43006 – Database name ‘%.*ls’ is too long.
  • 43007 – ‘%.*ls’ is not a valid database charset.
  • 43008 – ‘%.*ls’ is not a valid database collation.
  • 43009 – Storage in MB %d is below the minimum limit.
  • 43010 – ‘%.*ls’ cannot be updated.
  • 43011 – ‘%.*ls’ is not a valid version.
  • 43012 – The configuration name cannot be empty.
  • 43013 – The value for configuration ‘%.*ls’ cannot be empty.
  • 43014 – The same configuration ‘%.*ls’ cannot be updated more than once.
  • 43015 – The configuration ‘%.*ls’ does not exist for %.*ls server version %.*ls.
  • 43016 – The value ‘%.*ls’ for configuration ‘%.*ls’ is not valid. The allowed values are ‘%.*ls’.
  • 43017 – The configuration names you defined are not consistent.
  • 43018 – The value ‘%.*ls’ for configuration ‘%.*ls’ is not consistent with default value ‘%.*ls’.
  • 43019 – The source ‘%.*ls’ for configuration ‘%.*ls’ is not valid.
  • 45122 – ‘%ls’
  • 45220 – An error occurred while configuring for the SQL Agent: error %d, severity %d, state %d.
  • 45221 – An error occurred while configuring for the SQL Agent: error %d, severity %d, state %d.
  • 4524 – Cannot alter view ‘%.*ls’ because it has snapshot materialization.
  • 4525 – Cannot use hint ‘%ls’ on view ‘%.*ls’ that has snapshot materialization before the view is refreshed.
  • 45309 – The operation could not be completed because database ‘%ls’ on server ‘%ls’ is recovering from a geo-replication role change and is not currently eligible to become a primary or standalone database. Wait until the relationship leaves the ‘SUSPENDED’ replication state and try again.
  • 45310 – Unable to return metrics. Request would return too much data.
  • 45311 – The server key ‘%.*ls’ already exists. Please choose a different server key name.
  • 45312 – The server key URI ‘%.*ls’ already exists as another server key.
  • 45313 – The server key ‘%.*ls’ cannot be deleted because it is currently in use by ‘%.*ls’.
  • 45314 – Server key ‘%.*ls’ does not exist. Make sure that the server key name is entered correctly.
  • 45315 – The operation could not be completed because a service objective assignment is in progress for database ‘%.*ls’ on server ‘%.*ls.’ Wait for the service objective assignment to complete and try again.
  • 45316 – MODIFY FILE failed. Size is greater than MAXSIZE. Please query sys.database_files and use DBCC SHRINKFILE to reduce the file size first.
  • 45317 – Server ‘%.*ls’ does not exist in resource group ‘%.*ls’ in subscription ‘%.*ls’.
  • 45318 – Service Fabric Application Version is not available.
  • 45319 – The service objective assignment for database ‘%.*ls’ on server ‘%.*ls’ could not be completed as the database is too busy. Reduce the workload before initiating another service objective update.
  • 45320 – The operation could not be completed on server ‘%.*ls’ because the Azure Key Vault key ‘%.*ls’ is disabled.
  • 45321 – The operation could not be completed on server ‘%.*ls’ because attempts to connect to Azure Key Vault ‘%.*ls’ have failed
  • 45322 – The operation could not be completed because the Azure Key Vault key ‘%.*ls’ expiration date is invalid.
  • 45323 – Unable to start a copy because the source database ‘%ls’ is being updated.
  • 45324 – The operation could not be completed because the Azure Key Vault Uri is null or empty.
  • 45325 – The operation could not be completed because the Azure Key Vault Key name is null or empty.
  • 45326 – The operation could not be completed because the Azure Key Vault Key name ‘%ls’ does not exist.
  • 45327 – The operation could not be completed because the Azure Key Vault Key name ‘%ls’ is currently set as server encryption protector.
  • 45328 – The server identity is not correctly configured on server ‘%ls’. Please contact support.
  • 45329 – An invalid response from Azure Key Vault. Please use a valid Azure Key Vault URI.
  • 45330 – The server ‘%ls’ requires the following Azure Key Vault permisions: ‘%ls’. Please grant the missing permissions to the service principal with ID ‘%ls’.
  • 45331 – The operation could not be completed because the read scale value specified is not supported for a ‘%ls’ database.
  • 45332 – The operation could not be completed because the read scale value specified is invalid.
  • 45333 – The service request timed out. %ls.
  • 45334 – Server edition ‘%ls’ is invalid.
  • 45335 – Server type ‘%ls’ is invalid.
  • 45336 – The operation could not be completed because ‘%ls’ is an invalid Server Key name. Please provide a key name in the format of ‘vault_key_version’. For example, if the keyId is https://YourVaultName.vault.azure.net/keys/YourKeyName/01234567890123456789012345678901, then the Server Key Name should be formatted as: YourVaultName_YourKeyName_01234567890123456789012345678901.
  • 45337 – The planned failover operation has rolled back because database ‘%ls’ could not be synchronized with its remote partner. This may be due to a service outage, or to a high volume of write traffic. Consider using forced failover.
  • 45338 – The planned failover operation has rolled back because the remote server ‘%ls’ could not be reached. This may be due to a service outage. Consider using forced failover.
  • 45339 – The max size update on the geo-secondary database ‘%ls’ on server ‘%ls’ failed with reason ‘%ls’.
  • 45340 – The operation could not be completed because an Azure Active Directory error was encountered. The error message from Active Directory Authentication library (ADAL) is ‘%ls’.
  • 45341 – The operation could not be completed because an error was encountered when attempting to retrieve Key Vault information for ‘%ls’ from server ‘%ls’. The encountered error message is ‘%ls’.
  • 45342 – The operation could not be completed because an Azure Active Directory error was encountered. Please ensure the server ‘%ls’ and key vault ‘%ls’ belong to the same tenant. The error message from Active Directory Authentication library is ‘%ls’.
  • 45343 – The provided Key Vault uri ‘%ls’ is not valid. Please ensure the uri contains the vault, key, and key version information. An example valid uri looks like ‘https://YourVaultName.vault.azure.net/keys/YourKeyName/01234567890123456789012345678901’. Please ensure the vault belongs to an endpoint from the list of supported endpoints available at ‘%ls’.
  • 4632 – The permission ‘%.*ls’ is not supported in this version of SQL Server. Alternatively, use the %.*ls level ‘%.*ls’ permission.
  • 46527 – Altering the ‘%S_MSG’ property is not permitted for an external data source of type %ls.
  • 46628 – SHARED_MEMORY
  • 46654 – database scoped credential
  • 46723 – Large object column in Global Query is not supported for types other than Nvarchar(MAX), Varchar(MAX), Varbinary(MAX) and Image.
  • 46829 – The proc %.*ls is only supported for external data sources of type SHARD_MAP_MANAGER or RDBMS.
  • 46830 – Internal column references are not supported for external tables.
  • 46917 – An internal error occured while attempting to retrieve the encrypted database-scoped credential secret.
  • 46918 – An internal error occured while attempting to retrieve the encrypted database-scoped credential secret.
  • 46919 – An internal error occured while attempting to retrieve the encrypted database-scoped credential secret.
  • 47049 – Reason: VNET Firewall Rule has rejected the login.
  • 47050 – Reason: Unexpected error while copying the VNET IPv6 address.
  • 47051 – Reason: Unexpected error while parsing the VNET IPv6.
  • 47052 – Reason: Unexpected error while extracting VNET metadata info from the IPv6 (VNET parsing).
  • 47053 – Reason: Unexpected error on VNET firewall rule table lookup.
  • 47054 – Reason: Unexpected error on VNET firewall rule table COUNT lookup.
  • 47055 – Reason: VNET Firewall rejected the login due to a the source of a login being outside a VNET
  • 47056 – Reason: Firewall rejected the login attempt because VNET firewall rules are not database-level, only server-level.
  • 47057 – Reason: Firewall rejected the login because an IPv6 attempt was received when not expected
  • 47058 – Reason: Unexpected error on VNET firewall rule table lookup while looking up the IPv4 Allow All rule.
  • 47100 – The cluster type of availability group ‘%.*ls’ doesn’t match its primary configuration. Verify that the specified availability group cluster type is correct, then retry the operation.
  • 47101 – The cluster type of availability group ‘%.*ls’ only supports MANUAL failover mode. Verify that the specified availability group cluster type is correct, then retry the operation.
  • 47102 – The cluster type of availability group ‘%.*ls’ only supports EXTERNAL failover mode. Verify that the specified availability group cluster type is correct, then retry the operation.
  • 47103 – The cluster type of availability group ‘%.*ls’ only supports AUTOMATIC and MANUAL failover modes. Verify that the specified availability group cluster type is correct, then retry the operation.
  • 47104 – This operation cannot be performed on the availability group ‘%.*ls’ because it has EXTERNAL cluster type. Use the cluster management tools to perform the operation.
  • 47105 – The Always On Availability Groups feature must be enabled for this server instance before you can perform availability group operations. Please enable the feature, then retry the operation.
  • 47106 – Cannot join availability group ‘%.*ls’. Download configuration timeout. Please check primary configuration, network connectivity and firewall setup, then retry the operation.
  • 47107 – The %ls operation is not allowed by the current availability group configuration. The availability group ‘%.*ls’ only supports one relica which has witness availability mode. Verify that the specified availability group availability mode is correct, then retry the operation.
  • 47108 – The %ls operation is not allowed by the current availability group configuration. The availability group ‘%.*ls’ only supports two synchronous mode replicas and required_syncrhonized_secondaries_to_commit is zero when witness mode replica is specified. Verify that the specified availability group availability mode is correct, then retry the operation.
  • 47109 – Availability group ‘%.*ls’ cannot failover to this replica. Witness replica cannot become primary. An attempt to fail over an availability group failed. The replica is a witness and cannot become a primary.
  • 47110 – The ‘%.*ls’ option is not valid for the ‘%.*ls’ replica as it is a witness. Remove this option, then retry the operation
  • 47111 – Local availability replica for availability group ‘%.*ls’ cannot be granted permission to create databases. The replica is a witness and cannot host databases inside the availability group.
  • 4878 – Invalid quote character specified for bulk load. Quote character can be one single byte or Unicode character.
  • 4879 – Bulk load failed due to invalid column value in CSV data file %ls in row %d, column %d.
  • 4898 – Cannot bulk load CSV file. Invalid field parameters are specified for source column number %d in the format file “%s”. All data fields must be either character or Unicode character with terminator when CSV format is specified.
  • 4899 – Cannot bulk load CSV file. Invalid terminator is specified for source column number %d in the format file “%s”. All source column terminators must be the same except the last one when CSV format is specified. Only row terminator should be different.
  • 49401 – Database backup not supported on this database as it has foreign files attached.
  • 49501 – DBCC SHRINKFILE for %.*ls is aborted. Sbs flat files are not supported
  • 49502 – %.*ls: Page %d:%d could not be moved because it is an sbs flat file page or the destination is an sbs flat file page.
  • 49600 – SQL tiered storage table schema is corrupt.
  • 49601 – SBS Flat File Access not fully initialized, when function ‘%ls’ was called.
  • 49602 – Failure waiting for %ls latch in ‘%ls’.
  • 49814 – DynamicActivation is not supported for GeoDR DB: Logical Server ‘%.*ls’, Database ‘%.*ls’, ServiceLevelObjective ‘%.*ls’
  • 49815 – Database cannot be deactivated: Server ‘%.*ls’, Database ‘%.*ls’, ServiceLevelObjective ‘%.*ls’
  • 49816 – Server ‘%.*ls’, Database ‘%.*ls’ cannot be online as BlockingMode is set
  • 49817 – Failed to query CMS for thottling on database ‘%.*ls’, ‘%.*ls’ due to the exception: ‘%.*ls’
  • 49818 – Cannot deactivate a database when it is already getting deactivated, Server ‘%.*ls’, Database ‘%.*ls’
  • 49819 – Deflation Monitor Timer task encountered an error (SQL Error Code: %d). Refer to the xel for more details.
  • 49926 – Server setup is starting
  • 49927 – An error occurred while setting the server administrator (SA) password: error %d, severity %d, state %d.
  • 49928 – An error occurred during server setup. See previous errors for more information.
  • 49929 – Server setup completed successfully.
  • 49930 – Parallel redo is %ls for database ‘%.*ls’ with worker pool size [%d].
  • 49931 – An error occurred while configuring engine telemetry: error %d, severity %d, state %d.
  • 49932 – An error occurred while initializing security. %ls.
  • 49933 – ERROR: The MSSQL_SA_PASSWORD environment variable must be set when using the –reset-sa-password option.
  • 49934 – Error %u occurred while reading the RbIo configuration parameters. Verify that the sqlservr.ini or registry entries exist.
  • 49936 – ERROR: The provided PID [%s] is invalid. The PID must be in the form #####-#####-#####-#####-##### where ‘#’ is a number or letter.
  • 49937 – ERROR: A failure occurred in the licensing subsystem. Error [%d].
  • 49938 – The licensing PID was successfully processed. The new edition is [%s].
  • 49939 – Unable to initialize user-specified certificate configuration. The server is being shut down. Verify that the certificate is correctly configured. Error[%d]. State[%d].
  • 49940 – Unable to open one or more of the user-specified certificate file(s). Verify that the certificate file(s) exist with read permissions for the user and group running SQL Server.
  • 49941 – Unable to load one or more of the user-specified certificate file(s). Verify that the certificate file(s) are of a supported format.
  • 49942 – Internal error occurred initializing user-specified certificate configuration. Error code [%08X].
  • 49943 – The certificate [Certificate File:’%hs’, Private Key File:’%hs’] was successfully loaded for encryption. This will override any self-generated certificate.
  • 49944 – The allowed TLS protocol version list [‘%hs’] is invalid. Verify that the supplied TLS version numbers are supported by SQL Server and separated by spaces in the configuration.
  • 49945 – The allowed TLS cipher list [‘%hs’] is invalid. See docs.microsoft.com for more information on creating a cipher list.
  • 49946 – Internal error occurred initializing the TLS configuration. Error code [%d].
  • 49947 – Unable to initialize the TLS configuration. The server is being shut down. Verify that the allowed TLS protocol and cipher lists are configured correctly. Error state [%d].
  • 49948 – Successfully initialized the TLS configuration. Allowed TLS protocol versions are [‘%hs’]. Allowed TLS ciphers are [‘%hs’].
  • 49949 – ERROR: Unable to set system administrator password: %s.
  • 49950 – The SQL Server End-User License Agreement (EULA) must be accepted before SQL
  • 49951 – Server can start. The license terms for this product can be downloaded from
  • 49952 – http://go.microsoft.com/fwlink/?LinkId=746388.
  • 49953 – You can accept the EULA by specifying the –accept-eula command line option,
  • 49954 – setting the ACCEPT_EULA environment variable, or using the mssql-conf tool.
  • 49955 – Environment Variable Startup Parameters:%.*ls
  • 49956 – The default language (LCID %d) has been set for engine and full-text services.
  • 49957 – The default language (LCID %d) failed to be set for engine and full-text services.
  • 49958 – The server collation cannot be changed with user databases attached. Please detach user databases before changing server collation. (Note from Brent – whoa, wonder if that’s Linux-only.)
  • 49600 – SQL tiered storage table schema is corrupt.
  • 49959 – ERROR: The environment variable MSSQL_COLLATION contains an invalid collation ‘%.*ls’.
  • 5338 – Format option cannot be specified together with SINGLE_BLOB, SINGLE_CLOB or SINGLE_NCLOB option.
  • 5339 – CSV format option is supported for char and widechar datafiletype options.
  • 5545 – FILESTREAM: connected to kernel driver %ls. This is an informational message. No user action is required.
  • 5546 – FILESTREAM: failed to connect to kernel driver %ls.
  • 5576 – FILESTREAM feature is enabled. This is an informational message. No user action is required.
  • 5577 – FILESTREAM access level has been changed to %d. Restart the instance of SQL Server for the settings to fully take effect.
  • 5585 – FILESTREAM file I/O access could not be enabled. The operating system Administrator must enable FILESTREAM file I/O access on the instance using Configuration Manager.
  • 5867 – Changing AFFINITY is not supported when the sql server is running in agnostic affinity mode. (Note from Brent – COME ON, dammit, it’s SQL Server, not sql server.)
  • 694 – Internal error. Unable to create a block blob in azure storage.
  • 695 – Internal error. Unable to delete a block blob in azure storage.
  • 696 – Internal error. Unable to gain access to the tombstone table.
  • 697 – Internal error. Unable to get a blob storage container.
  • 8571 – SQL Server is unable to get outcome from Microsoft Distributed Transaction Coordinator (MS DTC) for the transaction with UOW ‘%ls’ because another resource manager with same RMID already exists.
  • 8716 – Invalid data was detected. An external producer has inserted a value into shared memory table that is not supported by SQL Server.
  • 8734 – Separator parameter for STRING_AGG cannot be large object type such as VARCHAR(MAX) or NVARCHAR(MAX).
  • 8735 – The operation failed because an online index build on the table terminated and caused a temporary inconsistency. Re-run the query.
  • 875 – Resilient buffer pool extension “%.*ls” has been started successfully with size is %I64d MB.
  • 876 – Failed to startup resilient buffer pool extension of size %I64d MB on path “%.*ls”.
  • 877 – Resilient buffer pool extension “%.*ls” has been enabled successfully with size %I64d MB.
  • 878 – Failed to create resilient buffer pool extension of size %I64d MB on path “%.*ls”.
  • 879 – Failed to start resilient buffer pool extension because database %d is not memory optimized.
  • 880 – Failed to find the metadata of resilient buffer pool extension in database %d.
  • 881 – Resilient buffer pool extension is already disabled. No action is necessary.
  • 882 – The schema of a table created by InternalBaseTable is corrupt.
  • 883 – Could not create the Write Page Recorder table: wpr_bucket_table for database %ls.
  • 884 – Could not persist a bucket to the Write Page Recorder table: wpr_bucket_table for database %ls.
  • 885 – An internal error occurred. Error code %X. Context: “%ls::%d”.
  • 886 – Resilient buffer pool extension is already enabled. No action is necessary.
  • 891 – Buffer pool extension is not supported on %ls platform.
  • 9033 – The transaction in database ‘%ls’ has exceeded the max size of %I64u bytes. See ‘http://aka.ms/sqldw_loglimit’ for assistance.
  • 9034 – PERSISTENT_LOG_BUFFER option is already on in database ‘%ls’.
  • 9035 – PERSISTENT_LOG_BUFFER can only be set on the DAX volume.
  • 9036 – The source has PERSISTENT_LOG_BUFFER enabled, but the current device is not DAX volume. PERSISTENT_LOG_BUFFER has been set to OFF.
  • 9037 – The file ‘%.*ls’ on remote block device cannot be initialized. Native error is 0x%08x.
  • 9038 – The VLF %lu could not be registered with the Log Leasing Service with error 0x%08X.
  • 9039 – Could not start lease for VLF %lu for consumer ID %ls with the Log Leasing Service with error 0x%08X.
  • 9040 – Could not end lease for consumer ID %ls with the Log Leasing Service with error 0x%08X.
  • 9828 – The second and third arguments of the TRANSLATE built-in function must contain an equal number of characters.
  • 9829 – STRING_AGG aggregation result exceeded the limit of 8000 bytes. Use LOB types to avoid result truncation.
Previous Post
New Wait Stats and DMV Columns in SQL Server 2017
Next Post
New System Stored Procedures in SQL Server 2017

6 Comments. Leave new

  • Some of the bold 499* messages are Linux Docker image ones (SA password and licensing).

    Reply
  • I can’t find anything about SNAPSHOT_MATERIALIZATION on views, but maaaannnnn does that sound intriguing. Based on message 4525, it sounds like they might be catching up, errmm, I mean adding some Oracle-like refresh options. Here’s hoping that whatever it is, it makes it into the on-prem product, not just Azure.

    Reply
    • Me neither. A few of us are working through it trying to decode what’s going on – Erik’s looking at the Extended Events around snapshot views, another person’s using the debugger. My current guess is that is a data-warehouse-friendly feature – create a snapshot view before your ETL jobs start, let people keep querying the data as of that moment in time while you continue to load the next day’s data.

      Reply
  • ZOUHAIR AJBIRE
    February 7, 2019 12:18 am

    13925 – Cannot drop or disable index or constraint ‘%.*s’ because the last unique index or constraint on ‘%.*s’ cannot be dropped or disabled.

    RESOLUTION SVP

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.

Menu
{"cart_token":"","hash":"","cart_data":""}