SQL Server 2016

  1. Aggregation for measure '%{name/}' in measure group '%{mgname/}' is not supported in VertiPaq mode. Supported aggregations ...
  2. Aggregation function %{aggfunc/} specified for mapping account type %{accounttype/} is not supported for ByAccount semiadditive ...
  3. Aggregations should not be created below the granularity attribute. This aggregation includes the '{0}' attribute which is ...
  4. Alert Replacement flag enables replacement of alert tokens. Applies only to SQL Server 2005 Service Pack 1 and later versions. ...
  5. All application instances External Activator had launched in its previous run for queue {0} have exited or aborted. A dummy ...
  6. All arguments within an ALLEXCEPT function must be related to (or contained by) the table which is used as the first argument. ...
  7. All articles in a publication allowing updatable subscriptions contain a uniqueidentifier column named 'MSrepl_tran_version' ...
  8. All articles in the publication have been marked for data validation (rowcount and checksum). The validation will be performed ...
  9. All articles in the publication have been marked for data validation (rowcount-only). The validation will be performed when ...
  10. All Column.ColumnEncryptionKeyName, Column.EncryptionAlgorithm and Column.EncryptionType must be set to enable Encryption ...
  11. All columns must be published in a merge publication from a Publisher on SQL Server version 7.0. Column filtering is not ...
  12. All columns of a CDC unique index must be defined as NOT NULL. Index '%1!s!' selected as the CDC unique index for source ...
  13. All events in the workload were not analysed. DTA assumes a default time of 8 hours. Consider providing a time bound using ...
  14. All events in the workload were not evaluated. Consider increasing time bound using (1) Limit tuning time in Tuning Options ...
  15. All events in the workload were not evaluated. DTA assumes a default time of 8 hours. Consider providing time bound using ...
  16. All events in the workload were not tuned. Consider increasing time bound using (1) Limit tuning time in Tuning Options screen ...
  17. All events in the workload were not tuned. DTA assumes a default time of 8 hours. Consider providing time bound using (1) ...
  18. All file attributes for the Set Attributes operation have been configured as No Change. At least one file attribute must ...
  19. All index columns must be mapped to input columns when the Lookup transformation is configured to use a Cache connection ...
  20. All merge articles must contain a uniqueidentifier column with a unique index and the ROWGUIDCOL property. SQL Server adds ...
  21. All objects in the EntitySet '{0}' must have unique primary keys. However, an instance of type '{1}' and an instance of type ...
  22. All objects specified in InternalProcessPartitions command should belong the same database specified by DatabaseId='%{DatabaseId/}'. ...
  23. All of the configuration settings that are flagged as valid in the tool will be applied to the SharePoint farm. Do you want ...
  24. All partitions based on a Sample DataView must use the Import query mode to get data. Partition '%{partition/}' in Table ...
  25. All prerequisites for cleaning up merge meta data have been completed. Execute sp_mergecompletecleanup to initiate the final ...
  26. All queries combined using a UNION, INTERSECT or EXCEPT operator must have an equal number of expressions in their target ...
  27. All queries combined using a UNION, INTERSECT or EXCEPT operator must have an equal number of expressions in their target ...
  28. All records for the entity are not included. If you update the attribute type now, data may be lost. Do you want to continue? ...
  29. All related columns between table '{0}' and table '{1}' must be specified within the same row. Relate columns within the ...
  30. All roles and members will be copied to the destination database. Any existing role and membership data will be replaced. ...
  31. All schedulers on Node %1!s! appear deadlocked due to a large number of worker threads waiting on %2!s!. Process Utilization ...
  32. All SSDL artifacts must target the same provider. The Provider '{0}' is different from '{1}' that was encountered earlier. ...
  33. All SSDL artifacts must target the same provider. The ProviderManifestToken '{0}' is different from '{1}' that was encountered ...
  34. All stored connection strings, credentials, and encrypted values in a subscription will be deleted. After you delete this ...
  35. All the available inputs on the target component are connected to outputs. Edit this component to define new inputs before ...
  36. All the events in the workload were ignored due to syntax errors.The most common reason for this error is that the database ...
  37. All three server instances did not remain interconnected for the duration of the ALTER DATABASE SET WITNESS command. There ...
  38. All updategram/diffgrams nodes with siblings must have ids, either user specified ones or mapping schema based key field ...
  39. All users are going to be disconnected. It is advised to backup the databases before upgrading. Would you like to continue? ...
  40. Allocation failure %1[: %{External/}%]%[, %{External/}%]. If using a 32-bit version of the product, consider upgrading to ...
  41. Allow Reporting Services to access SQL Server Agent. Access to SQL Server Agent is required to use subscription, schedule, ...
  42. Allows access to all members currently in the dimension, and allows access to members that are added to the topmost level ...
  43. Allows to track creation and deletion of internal parameter tables. Those tables are used to store information about active ...
  44. Allows to track when a new subscription request falls into an already existing class of (Match) or a new class (Create). ...
  45. ALLSELECTED function without parameters cannot be used as a table expression. It can appear only as a filter in CALCULATE. ...
  46. ALTER ASSEMBLY failed because assembly '%1!s!' has more than one file associated with it. Use ALTER ASSEMBLY DROP FILE to ...
  47. ALTER ASSEMBLY failed because it is referenced by object '%1!s!'. Assemblies that are referenced by SQL objects cannot be ...
  48. ALTER ASSEMBLY failed because required property '%1!s!' in type '%2!s!' was not found with the same signature in the updated ...
  49. ALTER ASSEMBLY failed because required type '%1!s!' does not exist or is not correctly defined in the updated assembly.
  50. ALTER ASSEMBLY failed because serialization data of type '%1!s!' would change in the updated assembly. Persisted types are ...
  51. ALTER ASSEMBLY failed because serialization layout of type '%1!s!' would change as a result of a change in type '%2!s!' in ...
  52. ALTER ASSEMBLY failed because table, view or constraint '%1!s!' depends on this assembly. Use WITH UNCHECKED DATA to skip ...
  53. ALTER ASSEMBLY failed because the function '%1!s!' of type '%2!s!' no longer satisfies indexability requirements, and is ...
  54. ALTER ASSEMBLY failed because the function '%1!s!' of type '%2!s!' no longer satisfies indexability requirements, and is ...
  55. ALTER ASSEMBLY failed because the identity of referenced assembly '%1!s!' has changed. Make sure the version, name, and public ...
  56. ALTER ASSEMBLY failed because the IsFixedLen attribute of type '%1!s!' would change in the updated assembly. Persisted types ...
  57. ALTER ASSEMBLY failed because the MaxLen attribute of type '%1!s!' would change in the updated assembly. Persisted types ...
  58. ALTER ASSEMBLY failed because the mutator attribute of method '%1!s!' in type '%2!s!' would change in the updated assembly, ...
  59. ALTER ASSEMBLY failed because the referenced assemblies would change. The referenced assembly list must remain the same. ...
  60. ALTER ASSEMBLY failed because the required field "%1!s!" in type "%2!s!" was not found with the same signature in the updated ...
  61. ALTER ASSEMBLY failed because the required method "%1!s!" in type "%2!s!" was not found with the same signature in the updated ...
  62. ALTER ASSEMBLY failed because the serialization format of type '%1!s!' would change in the updated assembly. Persisted types ...
  63. ALTER ASSEMBLY failed because the user-defined aggregate "%1!s!" does not exist or is not correctly defined in the updated ...
  64. ALTER ASSEMBLY has marked data as unchecked in one or more objects in database "%1!s!". Refer to column "has_unchecked_assembly_data" ...
  65. ALTER AVAILABILITY GROUP MODIFY AVAILABILITY GROUP' command failed. Participant availability replica '%1!s!' not found in ...
  66. ALTER DATABASE "%1!s!" command cannot be executed until both partner server instances are up, running, and connected. Start ...
  67. Alter database command failed because SQL Server was started with one or more undocumented trace flags that prevent enabling/disabling ...
  68. ALTER DATABASE CURRENT failed because '%1!s!' is a system database. System databases cannot be altered by using the CURRENT ...
  69. ALTER DATABASE failed because the distribution policy is invalid. The database distribution policy must be set to either ...
  70. ALTER DATABASE statement failed. The containment option of the database '%1!s!' could not be altered because compilation ...
  71. ALTER FEDERATION SPLIT operation failed due to an internal error. This request has been assigned a tracing ID of '%1!s!'. ...
  72. ALTER FEDERATION SPLIT operation failed. Specified boundary value already exists for federation distribution %1!s! and federation ...
  73. ALTER FEDERATION SPLIT operation has been aborted. The %1!s! federation was dropped while the split was still in progress. ...
  74. ALTER FEDERATION SWITCH IN failed. %1!s! of the federation key in %2!s! doesn't match with the correponding property of federation ...
  75. ALTER INDEX REBUILD statement failed because specifying %1!s! is not allowed when rebuilding a columnstore index. Rebuild ...