SQL Server 2016

  1. Always On: Availability group '%1!s!' was removed while the availability replica on this instance of SQL Server was offline. ...
  2. Always On: Explicitly transitioning the state of the Windows Server Failover Clustering (WSFC) resource that corresponds ...
  3. Always On: The availability replica manager is going offline because %1!s!. This is an informational message only. No user ...
  4. Always On: The availability replica manager is starting. This is an informational message only. No user action is required. ...
  5. Always On: The availability replica manager is waiting for the instance of SQL Server to allow client connections. This is ...
  6. Always On: The local replica of availability group '%1!s!' is being removed. The instance of SQL Server failed to validate ...
  7. Always On: The local replica of availability group '%1!s!' is going offline because either the lease expired or lease renewal ...
  8. Always On: The local replica of availability group '%1!s!' is going offline because the corresponding resource in the Windows ...
  9. Always On: The local replica of availability group '%1!s!' is going offline. This replica failed to read the persisted configuration ...
  10. Always On: The local replica of availability group '%1!s!' is going offline. This replica failed to read the persisted configuration, ...
  11. Always On: The local replica of availability group '%1!s!' is preparing to transition to the primary role in response to ...
  12. Always On: The local replica of availability group '%1!s!' is preparing to transition to the resolving role in response to ...
  13. Always On: The local replica of availability group '%1!s!' is restarting because the existing primary replica restarted or ...
  14. Always On: The local replica of availability group '%1!s!' is restarting, because it failed to read the persisted configuration. ...
  15. Always On: The local replica of availability group '%1!s!' is starting. This is an informational message only. No user action ...
  16. Always On: The local replica of availability group '%1!s!' is stopping. This is an informational message only. No user action ...
  17. Always On: The Windows Server Failover Clustering (WSFC) service was started using /forcequorum. This is an informational ...
  18. Always On: WSFC AG integrity check failed to find AG name to ID map entry with matching group ID for AG '%1!s!' (expected: ...
  19. Always On: WSFC AG integrity check failed to find AG name to ID map entry with matching resource ID for AG '%1!s!' (expected: ...
  20. Amount of memory the server has reserved for future usage. This counter shows current unused amount of the initial grant ...
  21. Amount of memory the server has reserved for future usage. This value shows current unused amount of the initial grant shown ...
  22. Amount of time (stored as PFDateTime format with 100-ns granularity, actual precision depends on specific API) taken by the ...
  23. Amount of time (stored as PFDateTime format with 100-ns granularity, actual precision depends on specific API) taken for ...
  24. Amount of time (stored as PFDateTime format with 100-ns granularity, actual precision depends on specific API) that engine ...
  25. Amount of time taken by the event. Although the server measures duration in microseconds, SQL Server Profiler can display ...
  26. An '%1!s!' statement was executed on database '%2!s!', table '%3!s!' by hostname '%4!s!', host process ID %5!s! using the ...
  27. An '%1!s!' statement was executed on object '%2!s!' by hostname '%3!s!', host process ID %4!s! using the WAIT_AT_LOW_PRIORITY ...
  28. An 'Import' of the file '{1}' was found in the project file '{0}'. This file is not registered as a safe file to import, ...
  29. An 'Import' of the file '{1}' was found in the user project file '{0}'. All imports in user project files are considered ...
  30. An ABORT_AFTER_WAIT = BLOCKERS lock request was issued on database_id = %1!s!, object_id = %2!s!. All blocking user sessions ...
  31. An active relationship already exists between {0} and {1}. Deactivate or delete the existing relationship to create another ...
  32. An aggregate cannot appear in an ON clause unless it is in a subquery contained in a HAVING clause or select list, and the ...
  33. An aggregate function is not allowed in the %1!s! clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or ...
  34. An aggregate may not appear in the WHERE clause unless it is in a subquery contained in a HAVING clause or a select list, ...
  35. An aggregated expression containing an outer reference must be contained in either the select list, or a HAVING clause subquery ...
  36. An ALTER FULLTEXT INDEX statement cannot remove the 'STATISTICAL_SEMANTICS' option from the last column in the index that ...
  37. An ALTER TABLE SWITCH statement was executed on database '%1!s!', table '%2!s!' by hostname '%3!s!', host process ID %4!s! ...
  38. An ambiguous input column name was specified. The column must be qualified as Component Name].[Column Name or referenced ...
  39. An ambiguous variable name was specified. The desired variable must be qualifed as @[Namespace::Variable]. This error occurs ...
  40. An Analysis Services instance that runs in SharePoint integrated mode uses health rules to detect problems in configuration, ...
  41. An APPEND clause in the SHAPE query has more than one column that references the same '%{col1/}' key column in the top level ...
  42. An application pool will be created for the Master Data Services web application. Type an application pool name and user ...
  43. An argument exception has occurred while data provider tried to insert data to destination. The returned message is : %1!s! ...
  44. An argument of a function has the wrong data type or the result is too large or too small. If the argument is expected to ...
  45. An argument of function '%{name/}' has the wrong data type or the result is too large or too small. If the argument is expected ...
  46. An argument of function '%{name/}' has the wrong data type or the result is too large or too small. If the argument is expected ...
  47. An arithmetic overflow error occurred while resolving the column values. This error can occur when using the Microsoft SQL ...
  48. An article already exists for table "%1!s!" with a different value for the @delete_tracking property. The value must be the ...
  49. An article cannot use @partition_options 2 or 3 (nonoverlapping partitions) and be a part of a logical record relationship ...
  50. An association End mapping has a 'to' Role {0} with multiplicity greater than one. A maximum multiplicity of one is supported. ...
  51. An attempt change to a read-only attribute on variable "%1" occurred. This error happens when a read-only attribute for a ...
  52. An attempt has been made to use a data extension '{0}' that is either not registered for this report server or is not supported ...
  53. An attempt has been made to use a semantic query extension associated with the data extension '{0}' that is not registered ...
  54. An attempt has been made to use an unregistered data extension, '{0}'. To use this data extension, it must be registered ...
  55. An attempt to add or join a system database, '%1!s!', to an availability group failed. Specify only user databases for this ...
  56. An attempt to attach an auto-named database for file %1!s! failed. A database with the same name exists, or specified file ...
  57. An attempt to create a distributed transaction export token failed with this error: %1!s!. Contact your Microsoft Distributed ...
  58. An attempt to fail over or create an availability group failed. This operation is not supported when Always On Availability ...
  59. An attempt to switch Always On Availability Groups to the local Windows Server Failover Clustering (WSFC) cluster context ...
  60. An attempt to switch the Windows Server Failover Clustering (WSFC) cluster context of Always On Availability Groups to a ...
  61. An attempt to switch the Windows Server Failover Clustering (WSFC) cluster context of Always On Availability Groups to the ...
  62. An attempt was made to add an asynchronous target to a session with a maximum memory of 0. For asynchronous targets to be ...
  63. An attempt was made to change the RoleID of the '%{strPermID/}' permission from '%{strRoleID/}' to '%{strNewRoleID/}'. The ...
  64. An attempt was made to create a Cluster Resource '{0}' on a non-cluster machine. Please make sure that your windows-cluster ...
  65. An attempt was made to create a Cluster Resource Type '{0}' on a non-cluster machine. Please make sure that your windows-cluster ...
  66. An attempt was made to set credentials for a data source '{0}' associated with the report. Report data source settings are ...
  67. An attribute relationship is not valid between an attribute whose IsAggregatable property is set to false and an attribute ...
  68. An attribute value is outside the range of values %{start/},%{end/}]. This is not supported by the data mining algorithm. ...
  69. An availability group replica already exists on the Windows Server Failover Clustering (WSFC) node '%1!s!'. Each WSFC node ...
  70. An availability replica '%1!s!' that is specified in the READ_ONLY_ROUTING_LIST for availability replica '%2!s!' does not ...
  71. An element of the enumerator returned by the ForEach Enumerator does not implement IEnumerator, contradicting the CollectionEnumerator ...
  72. An endpoint already exists with the bindings specified. Only one endpoint supported for a specific binding. Use ALTER ENDPOINT ...
  73. An endpoint of the requested type already exists. Only one endpoint of this type is supported. Use ALTER ENDPOINT or DROP ...
  74. An endpoint's transport or content cannot be changed through the ALTER ENDPOINT statement. Use DROP ENDPOINT and execute ...
  75. An entity from one EntitySet is mapped to a row that is also mapped to an entity from another EntitySet with possibly different ...