SQL Server 2016

  1. The aggregation design with an ID of '%{aggdesignid/}', of the '%{partition/}' partition, does not correspond to an existing ...
  2. The aggregation function of the %{operand/} left operand of the measure expression of the %{measure/} measure must be sum, ...
  3. The aggregation function of the %{operand/} right operand of the measure expression of the %{measure/} measure must be sum, ...
  4. The aggregation function of the '%{measure/}' measure must be sum, count, min, or max because the function has a measure ...
  5. The aggregation should not include both the '{0}' and '{1}' attributes, because there is a relationship from '{0}' to '{1}'. ...
  6. The AggregationUsage property should be set to 'Full' because either the attribute or the parent attribute (if the dimension ...
  7. The alert engine failed to register notification-callback with the eventlog process. Alert processing will now occur via ...
  8. The alert for 'oldest unsent transaction' has been raised. The current value of '%1!s!' surpasses the threshold '%2!s!'. ...
  9. The algorithm provider for the '%{AlgoName/}' data mining algorithm cannot be created; its ProgID is missing in the server ...
  10. The algorithm provider for the '%{AlgoName/}' data mining algorithm does not expose a mandatory interface for custom functions. ...
  11. The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the ...
  12. The ALL permission will be removed in a future version of SQL Server. Avoid using this permission in new development work ...
  13. The ALTER AVAILABILITY GROUP command failed because it contained multiple MODIFY REPLICA options: %1!s!. Enter a separate ...
  14. The alter database '%1!s!' failed to initiate because there are operations pending on the database. After the pending operations ...
  15. The ALTER DATABASE command could not be sent to the remote server instance '%1!s!'. The database mirroring configuration ...
  16. The ALTER DATABASE command is in process. Please wait at least five minutes before logging into database '%1!s!', in order ...
  17. The alter database for this partner config values may only be initiated on the current principal server for database "%1!s!". ...
  18. The ALTER DATABASE SET HADR SUSPEND (or SET HADR RESUME) statement failed on database '%1!s!' of availability group '%2!s!'. ...
  19. The ALTER DATABASE statement failed because the database collation %1!s! is not recognized by older client drivers. Try upgrading ...
  20. The ALTER SERVER CONFIGURATION SET HADR CLUSTER CONTEXT = '%1!s!' command failed because the local Windows Server Failover ...
  21. The ALTER SERVER CONFIGURATION SET HADR CLUSTER CONTEXT = '%1!s!' command failed. The current Windows Server Failover Clustering ...
  22. The ALTER TABLE SWITCH statement failed for table '%1!s!'. It is not possible to switch the partition of a table that has ...
  23. The alternate snapshot folder path generated by replication has been truncated. Reconfigure the publication to use a shorter ...
  24. The Always On Availability Groups feature is enabled on this instance of SQL Server and it is not supported in the edition ...
  25. The AlwaysInstallElevated registry key is set to 1 in either the HKCU or HKLM registry hive. If this installation is not ...
  26. The AlwaysOn Availability Groups feature must be enabled for server instance '{0}' before you can create an availability ...
  27. The AlwaysOn Availability Groups feature requires the x86(non-Wow) or x64 Enterprise Edition of SQL Server 2012 (or later ...
  28. The AlwaysOn feature must be enabled for the server instance {0}' before you can create an availability group on this instance. ...
  29. The amount of available system memory has been exceeded. If using a 32-bit version of the product, consider upgrading to ...
  30. The amount of compressed data exceeded the system limit of %1!d! bytes, retry the operation again with a smaller data set ...
  31. The amount of data you are trying to load exceeds the warning size set in the Settings dialog box. {0} members will be loaded. ...
  32. The amount of free disk space on the drive where the Analysis Services backup folder is located has dropped below {0}%. This ...
  33. The amount of time (in seconds) that the message has been alive. When this value is greater than or equal to the time_to_live, ...
  34. The amount of wait time that accumulated in a typical second during the last sample interval. A rate of 5000 ms/sec would ...
  35. The Analysis Server on '{0}' cannot be debugged. Make sure the server is started and that you are authorized to debug processes ...
  36. The Analysis Service account has been changed to {0}. If you wish to change it something else, use SQL Configuration Manager. ...
  37. The Analysis Service could not be started due to logon failure. Please use SQL Configuration Manager to set the user name ...
  38. The Analysis Service is in disabled state. Please change the start up mode to manual or automatic before starting the process. ...
  39. The Analysis Service was not found and so we have created config file on the path {0}. If you require to change the Configuration ...
  40. The Analysis Services OLE DB Provider can be used to create client applications that browse metadata and query data stored ...
  41. The Analysis Services OLE DB Provider can be used to create client applications that browse metadata and query data stored ...
  42. The Analysis Services OLE DB Provider can be used to create client applications that browse metadata and query data stored ...
  43. The Analysis Services service could not be started due to a logon failure. Use the SQL Configuration Manager to set the username ...
  44. The application cannot find one of its required files, possibly because it was unable to create it in the folder. Please ...
  45. The application domain %1 will be restarted because of memory pressure on the system. (Application: %2, CorrelationId: %3) ...
  46. The application has detected that another process is attempting a malicious action on the shared {0} object. The application ...
  47. The application is not valid. The only valid applications are ReportServerWebService, ReportManager and ReportServerWebApp. ...
  48. The application lock request '%1!s!' needed to modify Change Data Capture metadata was not granted. The value returned from ...
  49. The application monitor for queue {0} has been disabled because corresponding executable cannot be launched. No application ...
  50. The application name, version, and description are displayed in SQL Server Management Studio after the DAC has been deployed. ...
  51. The application pool specified is not valid. Make sure the specified name is not too long and doesn't contain illegal characters. ...
  52. The application pool specified is not valid. Make sure the specified name is not too long and doesn't contain illegal characters. ...
  53. The application pool user account "{0}" is not recognized on the database server "{1}". Change the application pool to run ...
  54. The appropriate constructor for the '{0}' type cannot be located: {1}. Make sure that the product is installed properly. ...
  55. The appropriate intermediate attributes cannot be found. The intermediate attributes should have the same number of key columns ...
  56. The ArchitectureCondition element cannot be the root element of a document, it can only be used as the child of a Condition ...
  57. The area chart displays data contiguously, so it is commonly used to represent data that occurs over a continuous period ...
  58. The argument data type '%1!s!' specified for the full-text query is not valid. Allowed data types are char, varchar, nchar, ...
  59. The argument specified for the "%1!s!" parameter of stored procedure sp_db_vardecimal_storage_format is not valid. Valid ...
  60. The argument specified for the '%1!s!' parameter of stored procedure '%2!s!' is not valid. Valid arguments are 'ON', 'OFF', ...
  61. The arguments for the connection resource identifier are not formatted or escaped correctly. Each argument should begin and ...
  62. The article %1!s! in the publication %2!s! does not have a valid conflict table entry in the system table sysarticleupdates. ...
  63. The article '%1!s!' contains the destination owner '%2!s!'. Non-SQL Server Subscribers require articles to have the destination ...
  64. The article '%1!s!' is already published in another publication, and is set to use nonoverlapping partitions with multiple ...
  65. The article '%1!s!' should enable column tracking to use the '%2!s!' resolver. The default resolver will be used to resolve ...
  66. The article cannot be created on table '%1!s!' because it has more than %2!s! columns and column-level tracking is being ...
  67. The article order specified in the @processing_order parameter of sp_addmergearticle does not reflect the primary key-foreign ...
  68. The article property 'status' cannot include bit 64, 'DTS horizontal partitions' because the publication does not allow data ...
  69. The article was dropped at the Distributor, but information at the Publisher '%1!s!' was not dropped. No action is required; ...
  70. The assembly module '%s' cannot be re-deployed because it was created outside of Visual Studio. Drop the module from the ...
  71. The assignment expression for the loop is not valid and needs to be modified. There should be additional error messages. ...
  72. The associated partition function '%1!s!' generates more partitions than there are file groups mentioned in the scheme '%2!s!'. ...
  73. The association: {0} value could not be generated because the record in the B_INDEX_LEXICON table with ID: {1} could not ...
  74. The attempt by the provider to pass remote stored procedure parameters to remote server '%1!s!' failed. Verify that the number ...
  75. The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible ...