SQL Server 2016
- Automatic checkpointing is disabled in database '%1!s!' because the log is out of space. Automatic checkpointing will be ...
- Automatic feature selection has been applied to model, '%{modelname/}' due to the large number of attributes. Set MAXIMUM_INPUT_ATTRIBUTES ...
- Automatic seeding of availability database '%1!s!' in availability group '%2!s!' failed with a transient error. The operation ...
- Automatic seeding of availability database '%1!s!' in availability group '%2!s!' failed with an unrecoverable error. Correct ...
- Automatic soft-NUMA was enabled because SQL Server has detected hardware NUMA nodes with greater than %1!s! logical processors. ...
- Automatic soft-NUMA was not enabled, because 'NodeConfiguration' key was detected in the registry at path '%1!s!'. Disable ...
- Automatically cleanup the change tracking information by using the specified retention period. If off, change tracking information ...
- Availability database '%1!s!', which is in the secondary role, is being restarted to resynchronize with the current primary ...
- Availability group '%1!s!' cannot process an ALTER AVAILABILITY GROUP command at this time. The availability group is being ...
- Availability group '%1!s!' cannot process an ALTER AVAILABILITY GROUP command at this time. The availability group is still ...
- Availability group '%1!s!' cannot process the ALTER AVAILABILITY GROUP command, because the local availability replica is ...
- Availability group '%1!s!' failed to create necessary events for the WSFC Lease mechanism. Windows returned error code (%2!s!) ...
- Availability group '%1!s!' failed to process %2!s!-%3!s! command. The local availability replica is not in a state that could ...
- Availability group '%1!s!' failed to process %2!s!-%3!s! command. The operation encountered SQL Server error %4!s! before ...
- Availability group '%1!s!' failed to process the %2!s!-%3!s! command. The availability group configuration has been updated. ...
- Availability group '%1!s!' failed to process the WSFC lease-renewal command. The local availability replica lease is no longer ...
- Availability group name to ID map entry for availability group '%1!s!' cannot be found in the Windows Server Failover Clustering ...
- Availability replica '%1!s!' cannot be added to availability group '%2!s!'. The availability group already contains an availability ...
- Availability replica '%1!s!' cannot be removed from availability group '%2!s!', because this replica is on the local instance ...
- Availability replica '%1!s!' cannot be removed from availability group '%2!s!'. The availability group does not contain an ...
- Availability replica '%1!s!' of availability group '%2!s!' cannot be brought online on this SQL Server instance. Another ...
- Availability-group DDL operations are permitted only when you are using the master database. Run the USE MASTER command, ...
- Average duration of all completed executions of this query (see "sys.dm_exec_query_stats.total_elapsed_time" and "sys.dm ...
- Average latency in microseconds between log blocks entering the Direct Log Consumer and being retrieved by the XTP controller, ...
- Avoid creating linked dimensions to a source that contains UnaryOperatorColumns, CustomRollupColumns, or CustomRollupPropertiesColumns ...
- Avoid defining many-to-many relationships when either the intermediate measure group or any of the intermediate dimensions ...
- Avoid redundant attribute relationships because these relationships may prevent data from being aggregated when the granularity ...
- Avoid specifying ROLAP storage mode or enabling proactive caching with the OnlineMode property set to Immediate for dimensions ...
- Avoid specifying ROLAP storage mode or enabling proactive caching with the OnlineMode property set to Immediate on remote ...
- AWE is currently enabled on a 32-bit instance of SQL Server. This feature is no longer supported. You must disable AWE before ...
- Axis object - Negative or zero values cannot be plotted correctly on logarithmic charts. Only positive values can be interpreted ...
- Azeri-Cyrillic-100, case-insensitive, accent-insensitive, kanatype-insensitive, width-insensitive, supplementary characters ...
- Azeri-Cyrillic-100, case-insensitive, accent-insensitive, kanatype-insensitive, width-sensitive, supplementary characters ...
- Azeri-Cyrillic-100, case-insensitive, accent-insensitive, kanatype-sensitive, width-insensitive, supplementary characters ...
- Azeri-Cyrillic-100, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive, supplementary characters ...
- Azeri-Cyrillic-100, case-sensitive, accent-insensitive, kanatype-insensitive, width-insensitive, supplementary characters ...
- Azure Key Vault safeguards cryptographic keys and other secrets in the Azure cloud. Keys stored in Azure Key Vault can be ...
- Azure Replica does not match the requirement for number of disks : Required number of disk: {0}, Azure Replica Size: {1}, ...
- Azure Sql Server has a lower version than the build of the on-premise sql server: Primary SQL Server Major Version {0},Primary ...
- Background processing failed for the '%{name/}' %{typename/}. Processing will be retried according to LazyProcessing\MaxRetries ...
- Backup destination "%1!s!" supports a FILESTREAM filegroup. This filegroup cannot be used as a backup destination. Rerun ...
- Backup device '%1!s!' does not exist. To view existing backup devices, use the sys.backup_devices catalog view. To create ...
- Backup file of version 10.50 contains ReadOnlyExclusive DB that can be restored only on servers supporting backups of versions ...
- Backup folder name {0} does not match the backup name in backup.xml located under the backup folder {0} on the backup node. ...
- BACKUP LOG cannot modify the database because the database is read-only. The backup will continue, although subsequent backups ...
- BACKUP LOG is not possible because bulk logged changes exist in the database and one or more filegroups are unavailable. ...
- BACKUP LOG was unable to log updates for for database '%1!s!'. Subsequent log backups will be required to advance the backup ...
- Backup mirroring is not available in this edition of SQL Server. See Books Online for more details on feature support in ...
- Backup of file '%1!s!' is not permitted because it contains pages subject to an online restore sequence. Complete the restore ...
- Backup to mirrored media sets requires all mirrors to append. Provide all members of the set, or reformat a new media set. ...
- Backup to URL device is not supported on server version {0}. Backup to URL device can be used on server version {1} or later. ...
- BACKUP WITH CONTINUE_AFTER_ERROR successfully generated a backup of the damaged database. Refer to the SQL Server error log ...
- Backup, file manipulation operations (such as ALTER DATABASE ADD FILE) and encryption changes on a database must be serialized. ...
- Bad habits to kick : ORDER BY ordinal DISCLAIMER: Third-party link provided as-is and Microsoft does not offer any guarantees ...
- Bad input case encountered with multiple consecutive sequence node occurrences while processing data for mining model, '%{modelname/}'. ...
- Bad input case encountered. Sequence node data is not found where expected in the input case while processing data for mining ...
- Based on article settings, table %1!s! should have an identity column, but it does not have one. Verify article settings ...
- Based on detected settings, the SQL Server instance is clustered, but no clustered features could be found. SQL Server Setup ...
- Batch processing is in progress. The current batch consists of %1!d! commands and %2!d! transactions. The last transaction ...
- Batches that have "set fmtonly" statements are required to have the first statement to be "set fmtonly on" and last statement ...
- Batches that have "set fmtonly" statements are required to have the first statement to be "set fmtonly on" and last statement ...
- BCP Thread Statistics Article : {0} Reader Exec Time (seconds) : {1:0.000} Writer Exec Time (seconds) : {2:0.000} Total Rows ...
- Be sure that the path you specify is correct. The wizard cannot validate it because the accounts used to access the folder ...
- Because the replication agents that synchronize subscriptions run unattended, you should configure SQL Server Agent to start ...
- Because the underlying provider had overridden DbProviderManifest.SupportsEscapingLikeArgument to return true, the DbPro ...
- Because this publication allows transformable subscriptions using DTS, it requires autogenerated stored procedures and parameterized ...
- Because this publication does not allow updatable subscriptions, when IDENTITY columns are transferred to the Subscriber, ...
- Before SQL Server Management Studio can resume mirroring, it must verify whether a FORCE_SERVICE_ALLOW_DATA_LOSS command ...
- Before the dialog can configure SSIS to enable support AlwaysOn on the new added secondary replicas, you must connect to ...
- Before the wizard can configure existing endpoints to grant them appropriate permissions, you must connect to all the existing ...
- Before you can upgrade, you have to manually remove SSISDB from the AlwaysOn availability group. After you upgrade, you have ...
- Before you change the database compatibility mode to 90 or later, modify statements that use constant expressions in the ...
- Binary type attributes are not supported as key columns. The attribute '%{IMBIColumnId/}' is defined as Binary and cannot ...
- Binary type attributes are not supported as key columns. The attribute '%{IMBIColumnId/}' is defined as Binary, in dimension ...
- Binary type columns cannot be used in relationships. The column '%{IWColumnName/}' is defined as Binary and cannot be used ...