SQL Server 2016

  1. ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same XML Schema Collection in tables '%2!s!' ...
  2. ALTER TABLE SWITCH statement failed because column '%1!s!' has data type %2!s! in source table '%3!s!' which is different ...
  3. ALTER TABLE SWITCH statement failed because the partitioned destination table is enabled for Change Data Capture and does ...
  4. ALTER TABLE SWITCH statement failed because the partitioned source table is enabled for Change Data Capture and does not ...
  5. ALTER TABLE SWITCH statement failed on table '%1!s!' because column '%2!s!' does not have the same GENERATED ALWAYS attribute ...
  6. ALTER TABLE SWITCH statement failed on table '%1!s!' because target and source tables have different SYSTEM_TIME PERIOD definitions. ...
  7. ALTER TABLE SWITCH statement failed on table '%1!s!' because target table has SYSTEM_TIME PERIOD while source table does ...
  8. 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 ...
  9. ALTER TABLE SWITCH statement failed. Check constraint '%1!s!' in source table '%2!s!' and check constraint '%3!s!' in target ...
  10. ALTER TABLE SWITCH statement failed. Check constraint '%1!s!' in source table '%2!s!' is NOCHECK constraint but the matching ...
  11. ALTER TABLE SWITCH statement failed. Check constraints of source table '%1!s!' allow values that are not allowed by range ...
  12. ALTER TABLE SWITCH statement failed. Check constraints or partition function of source table '%1!s!' allows values that are ...
  13. ALTER TABLE SWITCH statement failed. Column '%1!s!' in table '%2!s!' is computed column but the same column in '%3!s!' is ...
  14. ALTER TABLE SWITCH statement failed. Computed column '%1!s!' defined as '%2!s!' in table '%3!s!' is different from the same ...
  15. ALTER TABLE SWITCH statement failed. Foreign key constraint '%1!s!' is disabled in source table '%2!s!' and the corresponding ...
  16. ALTER TABLE SWITCH statement failed. Foreign key constraint '%1!s!' is NOCHECK in source table '%2!s!' and the corresponding ...
  17. ALTER TABLE SWITCH statement failed. Index '%1!s!' on indexed view '%2!s!' uses partition function '%3!s!', but table '%4!s!' ...
  18. ALTER TABLE SWITCH statement failed. Indexed view '%1!s!' is not aligned with table '%2!s!'. The partitioning column '%3!s!' ...
  19. ALTER TABLE SWITCH statement failed. Indexed view '%1!s!' references an object that does not participate in the ALTER TABLE ...
  20. ALTER TABLE SWITCH statement failed. Partition %1!s! of %2!s! '%3!s!' has TEXT filegroup '%4!s!' and partition %5!s! of %6!s! ...
  21. ALTER TABLE SWITCH statement failed. Partition %1!s! of %2!s! '%3!s!' is in filegroup '%4!s!' and partition %5!s! of %6!s! ...
  22. ALTER TABLE SWITCH statement failed. Range defined by partition %1!s! in table '%2!s!' is not a subset of range defined by ...
  23. ALTER TABLE SWITCH statement failed. Source and target partitions have different values for the DATA_COMPRESSION option. ...
  24. ALTER TABLE SWITCH statement failed. SWITCH is not allowed because source table '%1!s!' contains primary key for constraint ...
  25. ALTER TABLE SWITCH statement failed. Table '%1!s!' has a column level check constraint '%2!s!' on column '%3!s!' that is ...
  26. ALTER TABLE SWITCH statement failed. Table '%1!s!' has RULE constraint '%2!s!'. SWITCH is not allowed on tables with RULE ...
  27. ALTER TABLE SWITCH statement failed. Table '%1!s!' is not aligned with the index '%2!s!' on indexed view '%3!s!'. The table ...
  28. ALTER TABLE SWITCH statement failed. Target table '%1!s!' and source table '%2!s!' have different vardecimal storage format ...
  29. ALTER TABLE SWITCH statement failed. Target table '%1!s!' has a check constraint '%2!s!' on a CLR type column, but the source ...
  30. ALTER TABLE SWITCH statement failed. Target table '%1!s!' has a check constraint '%2!s!' on an XML column, but the source ...
  31. ALTER TABLE SWITCH statement failed. Target table '%1!s!' has a column level check constraint '%2!s!' but the source table ...
  32. ALTER TABLE SWITCH statement failed. Target table '%1!s!' has a table level check constraint '%2!s!' but the source table ...
  33. ALTER TABLE SWITCH statement failed. Target table '%1!s!' has an XML or spatial index '%2!s!' on it. Only source table can ...
  34. ALTER TABLE SWITCH statement failed. Target table '%1!s!' has foreign key for constraint '%2!s!' but source table '%3!s!' ...
  35. ALTER TABLE SWITCH statement failed. Target table '%1!s!' is referenced by %2!s! indexed view(s), but source table '%3!s!' ...
  36. ALTER TABLE SWITCH statement failed. Target table '%1!s!' is referenced by %2!s! indexed view(s), but source table '%3!s!' ...
  37. ALTER TABLE SWITCH statement failed. The columns set used to partition the table '%1!s!' is different from the column set ...
  38. ALTER TABLE SWITCH statement failed. The lobdata of partition %1!s! in table '%2!s!' resides in a readonly filegroup '%3!s!'. ...
  39. ALTER TABLE SWITCH statement failed. The source table '%1!s!' is in database '%2!s!' while the target table '%3!s!' is in ...
  40. ALTER TABLE SWITCH statement failed. The statement is not allowed because one or more of the tables in this statement is ...
  41. ALTER TABLE SWITCH statement failed. The table '%1!s!' belongs to a publication which does not allow switching of partitions ...
  42. ALTER TABLE SWITCH statement failed. The table '%1!s!' has clustered index '%2!s!' while the table '%3!s!' does not have ...
  43. ALTER TABLE SWITCH statement failed. The table '%1!s!' has different setting for Large Value Types Out Of Row table option ...
  44. ALTER TABLE SWITCH statement failed. The table '%1!s!' has inline limit of %2!s! for text in row data which is different ...
  45. ALTER TABLE SWITCH statement failed. The table '{0}' has a clustered columnstore index '{1}' while the table '{2}' does not ...
  46. ALTER TABLE SWITCH statement failed. There is no identical index in source table '%1!s!' for the index '%2!s!' in target ...
  47. Altering existing schema components is not allowed. There was an attempt to modify an existing XML Schema component, component ...
  48. Altering table '%1!s!' failed because the row size using vardecimal storage format exceeds the maximum allowed table row ...
  49. Altering the name of a Windows principal is not supported through this form of execution. For more information about this, ...
  50. Alternate snapshot folder and dynamic snapshot location are incompatible parameters, at most one of them can be specified ...
  51. Although the digital signature is valid, the certification authority is not trusted and authenticity cannot be guaranteed. ...
  52. Although the trace definition was downloaded successfully, there was a problem loading trace description file %s, which may ...
  53. Although validation of the package returned DTSER_SUCCESS (0), there were warnings, and those warnings will be treated as ...
  54. Always Encrypted is designed to protect sensitive information - such as credit card numbers - stored in SQL Server databases. ...
  55. Always On Availability Groups connection with %1!s! database established for %2!s! database '%3!s!' on the availability replica ...
  56. Always On Availability Groups connection with %1!s! database terminated for %2!s! database '%3!s!' on the availability replica ...
  57. Always On Availability Groups data movement for database '%1!s!' has been resumed. This is an informational message only. ...
  58. Always On Availability Groups data movement for database '%1!s!' has been suspended for the following reason: "%2!s!" (Source ...
  59. Always On Availability Groups log apply for availability database "%1!s!" has received an out-of-order log block. The expected ...
  60. Always On Availability Groups Send Error (Error code 1!s!, "NOT OK") was returned when sending a message for database ID ...
  61. Always On Availability Groups startup has been cancelled, because SQL Server is shutting down. This is an informational message ...
  62. Always On Availability Groups transport for availability database "%1!s!" failed to decompress the log block whose LSN is ...
  63. Always On Availability Groups transport for availability database "%1!s!" has hit flow control boundary with log block whose ...
  64. Always On Availability Groups transport has detected a missing log block for availability database "%1!s!". LSN of last applied ...
  65. Always On Availability Groups was not started because %1!s!. This is an informational message. No user action is required. ...
  66. Always On Availability Groups: Local Windows Server Failover Clustering node is no longer online. This is an informational ...
  67. Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message ...
  68. Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. ...
  69. Always On Availability Groups: Local Windows Server Failover Clustering service has become unavailable. This is an informational ...
  70. Always On Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message ...
  71. Always On Availability Groups: Waiting for local Windows Server Failover Clustering node to come online. This is an informational ...
  72. Always On Availability Groups: Waiting for local Windows Server Failover Clustering node to start. This is an informational ...
  73. Always On Availability Groups: Waiting for local Windows Server Failover Clustering service to start. This is an informational ...
  74. Always On: A failure %1!s! was encountered while waiting for LSN %2!s! to be hardened on the Commit Manager %3!s! for database ...
  75. Always On: Availability group '%1!s!' is going offline because it is being removed. This is an informational message only. ...