SQL Server 2016

  1. All merge articles must contain a uniqueidentifier column with a unique index and the ROWGUIDCOL property. SQL Server adds ...
  2. All objects in the EntitySet '{0}' must have unique primary keys. However, an instance of type '{1}' and an instance of type ...
  3. All objects specified in InternalProcessPartitions command should belong the same database specified by DatabaseId='%{DatabaseId/}'. ...
  4. All of the configuration settings that are flagged as valid in the tool will be applied to the SharePoint farm. Do you want ...
  5. All partitions based on a Sample DataView must use the Import query mode to get data. Partition '%{partition/}' in Table ...
  6. All prerequisites for cleaning up merge meta data have been completed. Execute sp_mergecompletecleanup to initiate the final ...
  7. All queries combined using a UNION, INTERSECT or EXCEPT operator must have an equal number of expressions in their target ...
  8. All queries combined using a UNION, INTERSECT or EXCEPT operator must have an equal number of expressions in their target ...
  9. All records for the entity are not included. If you update the attribute type now, data may be lost. Do you want to continue? ...
  10. All related columns between table '{0}' and table '{1}' must be specified within the same row. Relate columns within the ...
  11. All roles and members will be copied to the destination database. Any existing role and membership data will be replaced. ...
  12. All schedulers on Node %1!s! appear deadlocked due to a large number of worker threads waiting on %2!s!. Process Utilization ...
  13. All SSDL artifacts must target the same provider. The Provider '{0}' is different from '{1}' that was encountered earlier. ...
  14. All SSDL artifacts must target the same provider. The ProviderManifestToken '{0}' is different from '{1}' that was encountered ...
  15. All stored connection strings, credentials, and encrypted values in a subscription will be deleted. After you delete this ...
  16. All the available inputs on the target component are connected to outputs. Edit this component to define new inputs before ...
  17. All the events in the workload were ignored due to syntax errors.The most common reason for this error is that the database ...
  18. All three server instances did not remain interconnected for the duration of the ALTER DATABASE SET WITNESS command. There ...
  19. All updategram/diffgrams nodes with siblings must have ids, either user specified ones or mapping schema based key field ...
  20. All users are going to be disconnected. It is advised to backup the databases before upgrading. Would you like to continue? ...
  21. Allocation failure %1[: %{External/}%]%[, %{External/}%]. If using a 32-bit version of the product, consider upgrading to ...
  22. Allow Reporting Services to access SQL Server Agent. Access to SQL Server Agent is required to use subscription, schedule, ...
  23. Allows access to all members currently in the dimension, and allows access to members that are added to the topmost level ...
  24. Allows to track creation and deletion of internal parameter tables. Those tables are used to store information about active ...
  25. Allows to track when a new subscription request falls into an already existing class of (Match) or a new class (Create). ...
  26. ALLSELECTED function without parameters cannot be used as a table expression. It can appear only as a filter in CALCULATE. ...
  27. ALTER ASSEMBLY failed because assembly '%1!s!' has more than one file associated with it. Use ALTER ASSEMBLY DROP FILE to ...
  28. ALTER ASSEMBLY failed because it is referenced by object '%1!s!'. Assemblies that are referenced by SQL objects cannot be ...
  29. ALTER ASSEMBLY failed because required property '%1!s!' in type '%2!s!' was not found with the same signature in the updated ...
  30. ALTER ASSEMBLY failed because serialization data of type '%1!s!' would change in the updated assembly. Persisted types are ...
  31. ALTER ASSEMBLY failed because serialization layout of type '%1!s!' would change as a result of a change in type '%2!s!' in ...
  32. ALTER ASSEMBLY failed because table, view or constraint '%1!s!' depends on this assembly. Use WITH UNCHECKED DATA to skip ...
  33. ALTER ASSEMBLY failed because the function '%1!s!' of type '%2!s!' no longer satisfies indexability requirements, and is ...
  34. ALTER ASSEMBLY failed because the function '%1!s!' of type '%2!s!' no longer satisfies indexability requirements, and is ...
  35. ALTER ASSEMBLY failed because the identity of referenced assembly '%1!s!' has changed. Make sure the version, name, and public ...
  36. ALTER ASSEMBLY failed because the IsFixedLen attribute of type '%1!s!' would change in the updated assembly. Persisted types ...
  37. ALTER ASSEMBLY failed because the MaxLen attribute of type '%1!s!' would change in the updated assembly. Persisted types ...
  38. ALTER ASSEMBLY failed because the mutator attribute of method '%1!s!' in type '%2!s!' would change in the updated assembly, ...
  39. ALTER ASSEMBLY failed because the referenced assemblies would change. The referenced assembly list must remain the same. ...
  40. ALTER ASSEMBLY failed because the required field "%1!s!" in type "%2!s!" was not found with the same signature in the updated ...
  41. ALTER ASSEMBLY failed because the required method "%1!s!" in type "%2!s!" was not found with the same signature in the updated ...
  42. ALTER ASSEMBLY failed because the serialization format of type '%1!s!' would change in the updated assembly. Persisted types ...
  43. ALTER ASSEMBLY failed because the user-defined aggregate "%1!s!" does not exist or is not correctly defined in the updated ...
  44. ALTER ASSEMBLY has marked data as unchecked in one or more objects in database "%1!s!". Refer to column "has_unchecked_assembly_data" ...
  45. ALTER AVAILABILITY GROUP MODIFY AVAILABILITY GROUP' command failed. Participant availability replica '%1!s!' not found in ...
  46. ALTER DATABASE "%1!s!" command cannot be executed until both partner server instances are up, running, and connected. Start ...
  47. Alter database command failed because SQL Server was started with one or more undocumented trace flags that prevent enabling/disabling ...
  48. ALTER DATABASE CURRENT failed because '%1!s!' is a system database. System databases cannot be altered by using the CURRENT ...
  49. ALTER DATABASE failed because the distribution policy is invalid. The database distribution policy must be set to either ...
  50. ALTER DATABASE statement failed. The containment option of the database '%1!s!' could not be altered because compilation ...
  51. ALTER FEDERATION SPLIT operation failed due to an internal error. This request has been assigned a tracing ID of '%1!s!'. ...
  52. ALTER FEDERATION SPLIT operation failed. Specified boundary value already exists for federation distribution %1!s! and federation ...
  53. ALTER FEDERATION SPLIT operation has been aborted. The %1!s! federation was dropped while the split was still in progress. ...
  54. ALTER FEDERATION SWITCH IN failed. %1!s! of the federation key in %2!s! doesn't match with the correponding property of federation ...
  55. ALTER INDEX REBUILD statement failed because specifying %1!s! is not allowed when rebuilding a columnstore index. Rebuild ...
  56. ALTER INDEX REBUILD statement failed because the %1!s! option is not allowed when rebuilding a columnstore index. Rebuild ...
  57. ALTER INDEX REORGANIZE statement failed on a clustered columnstore index with error %1!s!. See previous error messages for ...
  58. Alter partition function statement failed. Cannot repartition table '%1!s!' by altering partition function '%2!s!' because ...
  59. Alter schema collection cannot be performed because the current schema has a lax wildcard or an element of type xs:anyType. ...
  60. ALTER SCHEMA COLLECTION failed because path '%1!s!' indexed with selective XML index '%2!s!' on table '%3!s!' would be invalidated. ...
  61. ALTER SCHEMA COLLECTION failed. It cannot be performed on a schema collection that allows laxly validated content and is ...
  62. ALTER SCHEMA COLLECTION failed. Revalidation of XML columns in table '%1!s!' did not succeed due to the following reason: ...
  63. Alter table '%1!s!' failed because the added fixed column might cause existing data to go beyond the maximum allowable table ...
  64. ALTER TABLE ALTER COLUMN ADD ROWGUIDCOL failed because a column already exists in table '%1!s!' with ROWGUIDCOL property. ...
  65. ALTER TABLE ALTER COLUMN DROP ROWGUIDCOL failed because a column does not exist in table '%1!s!' with ROWGUIDCOL property. ...
  66. ALTER TABLE DROP COLUMN failed because '%1!s!' is the only data column in table '%2!s!'. A table must have at least one data ...
  67. ALTER TABLE failed because the table has %1!s! variable length columns (including columns that have been dropped but require ...
  68. ALTER TABLE only allows columns to be added that can contain nulls, or have a DEFAULT definition specified, or the column ...
  69. ALTER TABLE SWITCH statement failed because column '%1!s!' at ordinal %2!s! in table '%3!s!' has a different name than the ...
  70. ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same ANSI trimming semantics in tables '%2!s!' ...
  71. ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same CLR type in tables '%2!s!' and '%3!s!'. ...
  72. ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same collation in tables '%2!s!' and '%3!s!'. ...
  73. ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same column set property in tables '%2!s!' and ...
  74. ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same FILESTREAM storage attribute in tables ...
  75. ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same nullability attribute in tables '%2!s!' ...