SQL Server 2008 R2

  1. All articles in a publication allowing updatable subscriptions contain a uniqueidentifier column named 'MSrepl_tran_version' ...
  2. All articles in the publication have been marked for data validation (rowcount and checksum). The validation will be performed ...
  3. All articles in the publication have been marked for data validation (rowcount-only). The validation will be performed when ...
  4. All columns must be published in a merge publication from a Publisher on SQL Server version 7.0. Column filtering is not ...
  5. All columns of a CDC unique index must be defined as NOT NULL. Index '%1!s!' selected as the CDC unique index for source ...
  6. All events in the workload were not analysed. DTA assumes a default time of 8 hours. Consider providing a time bound using ...
  7. All events in the workload were not evaluated. Consider increasing time bound using (1) Limit tuning time in Tuning Options ...
  8. All events in the workload were not evaluated. DTA assumes a default time of 8 hours. Consider providing time bound using ...
  9. All events in the workload were not tuned. Consider increasing time bound using (1) Limit tuning time in Tuning Options screen ...
  10. All events in the workload were not tuned. DTA assumes a default time of 8 hours. Consider providing time bound using (1) ...
  11. All index columns must be mapped to input columns when the Lookup transformation is configured to use a Cache connection ...
  12. All merge articles must contain a uniqueidentifier column with a unique index and the ROWGUIDCOL property. SQL Server adds ...
  13. All prerequisites for cleaning up merge meta data have been completed. Execute sp_mergecompletecleanup to initiate the final ...
  14. All queries combined using a UNION, INTERSECT or EXCEPT operator must have an equal number of expressions in their target ...
  15. All related columns between table '{0}' and table '{1}' must be specified within the same row. Relate columns within the ...
  16. All roles and members will be copied to the destination database. Any existing role and membership data will be replaced. ...
  17. All schedulers on Node %1!s! appear deadlocked due to a large number of worker threads waiting on %2!s!. Process Utilization ...
  18. All stored connection strings, credentials, and encrypted values in a subscription will be deleted. After you delete this ...
  19. All the available inputs on the target component are connected to outputs. Edit this component to define new inputs before ...
  20. All the events in the workload were ignored due to syntax errors.The most common reason for this error is that the database ...
  21. All three server instances did not remain interconnected for the duration of the ALTER DATABASE SET WITNESS command. There ...
  22. All updategram/diffgrams nodes with siblings must have ids, either user specified ones or mapping schema based key field ...
  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. ALTER ASSEMBLY failed because assembly '%1!s!' has more than one file associated with it. Use ALTER ASSEMBLY DROP FILE to ...
  27. ALTER ASSEMBLY failed because it is referenced by object '%1!s!'. Assemblies that are referenced by SQL objects cannot be ...
  28. ALTER ASSEMBLY failed because required property '%1!s!' in type '%2!s!' was not found with the same signature in the updated ...
  29. ALTER ASSEMBLY failed because serialization data of type '%1!s!' would change in the updated assembly. Persisted types are ...
  30. ALTER ASSEMBLY failed because serialization layout of type '%1!s!' would change as a result of a change in type '%2!s!' in ...
  31. ALTER ASSEMBLY failed because table, view or constraint '%1!s!' depends on this assembly. Use WITH UNCHECKED DATA to skip ...
  32. ALTER ASSEMBLY failed because the function '%1!s!' of type '%2!s!' no longer satisfies indexability requirements, and is ...
  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 identity of referenced assembly '%1!s!' has changed. Make sure the version, name, and public ...
  35. ALTER ASSEMBLY failed because the IsFixedLen attribute of type '%1!s!' would change in the updated assembly. Persisted types ...
  36. ALTER ASSEMBLY failed because the MaxLen attribute of type '%1!s!' would change in the updated assembly. Persisted types ...
  37. ALTER ASSEMBLY failed because the mutator attribute of method '%1!s!' in type '%2!s!' would change in the updated assembly, ...
  38. ALTER ASSEMBLY failed because the referenced assemblies would change. The referenced assembly list must remain the same. ...
  39. ALTER ASSEMBLY failed because the required field "%1!s!" in type "%2!s!" was not found with the same signature in the updated ...
  40. ALTER ASSEMBLY failed because the required method "%1!s!" in type "%2!s!" was not found with the same signature in the updated ...
  41. ALTER ASSEMBLY failed because the serialization format of type '%1!s!' would change in the updated assembly. Persisted types ...
  42. ALTER ASSEMBLY failed because the user-defined aggregate "%1!s!" does not exist or is not correctly defined in the updated ...
  43. ALTER ASSEMBLY has marked data as unchecked in one or more objects in database "%1!s!". Refer to column "has_unchecked_assembly_data" ...
  44. ALTER DATABASE "%1!s!" command cannot be executed until both partner server instances are up, running, and connected. Start ...
  45. Alter database command failed because SQL Server was started with one or more undocumented trace flags that prevent enabling/disabling ...
  46. Alter partition function statement failed. Cannot repartition table '%1!s!' by altering partition function '%2!s!' because ...
  47. Alter schema collection cannot be performed because the current schema has a lax wildcard or an element of type xs:anyType. ...
  48. ALTER SCHEMA COLLECTION failed. It cannot be performed on a schema collection that allows laxly validated content and is ...
  49. ALTER SCHEMA COLLECTION failed. Revalidation of XML columns in table '%1!s!' did not succeed due to the following reason: ...
  50. ALTER TABLE ALTER COLUMN ADD ROWGUIDCOL failed because a column already exists in table '%1!s!' with ROWGUIDCOL property. ...
  51. ALTER TABLE ALTER COLUMN DROP ROWGUIDCOL failed because a column does not exist in table '%1!s!' with ROWGUIDCOL property. ...
  52. 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 ...
  53. ALTER TABLE only allows columns to be added that can contain nulls, or have a DEFAULT definition specified, or the column ...
  54. ALTER TABLE SWITCH statement failed because column '%1!s!' at ordinal %2!s! in table '%3!s!' has a different name than the ...
  55. ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same ANSI trimming semantics in tables '%2!s!' ...
  56. ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same CLR type in tables '%2!s!' and '%3!s!'. ...
  57. ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same collation in tables '%2!s!' and '%3!s!'. ...
  58. ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same column set property in tables '%2!s!' and ...
  59. ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same FILESTREAM storage attribute in tables ...
  60. ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same nullability attribute in tables '%2!s!' ...
  61. ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same persistent attribute in tables '%2!s!' ...
  62. ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same ROWGUIDCOL property in tables '%2!s!' and ...
  63. ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same sparse storage attribute in tables '%2!s!' ...
  64. ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same XML Schema Collection in tables '%2!s!' ...
  65. ALTER TABLE SWITCH statement failed because column '%1!s!' has data type %2!s! in source table '%3!s!' which is different ...
  66. ALTER TABLE SWITCH statement failed because the partitioned destination table is enabled for Change Data Capture and does ...
  67. ALTER TABLE SWITCH statement failed because the partitioned source table is enabled for Change Data Capture and does not ...
  68. ALTER TABLE SWITCH statement failed. %1!s! '%2!s!' is in filegroup '%3!s!' and partition %4!s! of %5!s! '%6!s!' is in filegroup ...
  69. ALTER TABLE SWITCH statement failed. Check constraint '%1!s!' in source table '%2!s!' and check constraint '%3!s!' in target ...
  70. ALTER TABLE SWITCH statement failed. Check constraint '%1!s!' in source table '%2!s!' is NOCHECK constraint but the matching ...
  71. ALTER TABLE SWITCH statement failed. Check constraints of source table '%1!s!' allow values that are not allowed by range ...
  72. ALTER TABLE SWITCH statement failed. Check constraints or partition function of source table '%1!s!' allows values that are ...
  73. ALTER TABLE SWITCH statement failed. Column '%1!s!' in table '%2!s!' is computed column but the same column in '%3!s!' is ...
  74. ALTER TABLE SWITCH statement failed. Computed column '%1!s!' defined as '%2!s!' in table '%3!s!' is different from the same ...
  75. ALTER TABLE SWITCH statement failed. Foreign key constraint '%1!s!' is disabled in source table '%2!s!' and the corresponding ...