SQL Server 2016

  1. Cleaning up after a column master key rotation will delete all key values already encrypted with a second master key. Ensure ...
  2. Cleanup of merge meta data at republisher '%1!s!'.'%2!s!' could not be performed because merge processes are propagating ...
  3. Cleanup of merge meta data cannot be performed because some republishers have not quiesced their changes. Cleanup will proceed ...
  4. Cleanup of merge meta data cannot be performed while merge processes are running. Cleanup will proceed after the merge processes ...
  5. Cleanup of merge meta data cannot be performed while merge processes are running. Retry this operation after the merge processes ...
  6. Clear auto-assigned synonyms from the selected table. At least one table must exist before you can clear auto-assigned synonyms. ...
  7. Clear the check boxes of the model items that you do not want to appear in this perspective. By default, an entity's identifying ...
  8. cleared in one minute. This will empty the results pane, discard unsaved changes, and free the resources on the database ...
  9. Click OK to dismiss this particular instance of a warning. To globally dismiss one or more warnings, use the Warnings tab ...
  10. Click Remove to remove ProductShortName from your computer. After removal, this program will no longer be available for use. ...
  11. Click the button to save the T-SQL script that will be used to upgrade the database. Pre-Deployment and Post-Deployment scripts ...
  12. Click the SQL Server Feature Installation option to individually select which feature components to install, or click a feature ...
  13. Click Yes to commit your changes to database anyway. Click No to discard your change and retrieve the current data for this ...
  14. Click Yes to exit the SQL Server setup installation wizard. If you exit the setup, you must undo your last SQL Server setup ...
  15. Click Yes to save your changes and update the database. Click No to discard your changes and refresh the Results pane. Click ...
  16. Client (ID %1!s!) failed to submit work to asynchronous operations administrator. The client has not registered with the ...
  17. Client certificate is missing. This error occurs when the server is expecting an SSL client certificate and the user has ...
  18. Client Network Utility could not be located on this computer. Re-run Setup and make sure it is installed properly before ...
  19. Client sent an invalid token when server was expecting federated authentication token. And it was not a disconnect event. ...
  20. Client subscriptions and anonymous subscriptions cannot republish data. To republish data from this database, the subscription ...
  21. Client unable to establish connection because an error was encountered during handshakes before login. Common causes include ...
  22. ClientRequest has already existing session and is trying to get another session object. This is acceptable only for pipeline ...
  23. CLR type '%1!s!'.'%2!s!' is disabled because the on disk format for this CLR type has been changed. Use DROP TYPE to remove ...
  24. CLR types cannot be used as column types in OPENJSON function with explicit schema. CLR types are not supported in WITH clause. ...
  25. Cluster group '{0}' did not come online after move to node '{1}'. To continue, investigate logs for cluster events, system ...
  26. Cluster group '{0}' failed after move to node '{1}'. To continue, investigate logs for cluster events, system events, and ...
  27. Cluster resource DLLs may be updated, resulting in restart of one or more other clustered SQL Server instances active on ...
  28. Cluster resource DLLs will be updated, resulting in restart of one or more other clustered SQL Server instances active on ...
  29. CLUSTERDISTANCE=3=[ ]=The ClusterDistance function returns the distance of the input case from the specified (or most likely) ...
  30. Clustered columnstore index '%1!s!' column '%2!s!' rowgroup id %3!s! on table '%4!s!' has one or more data values that are ...
  31. Clustered columnstore index '%1!s!' column '%2!s!' rowgroup id %3!s! on table '%4!s!' has one or more data values that do ...
  32. Clustered columnstore index '%1!s!' on table '%2!s!' has a missing column segment on column id %3!s! and rowgroup id %4!s!. ...
  33. Clustered columnstore index '%1!s!' on table '%2!s!' has a missing dictionary on column id %3!s! and rowgroup id %4!s!. Restore ...
  34. Clustered columnstore index '%1!s!' on table '%2!s!', column '%3!s!' has one or more values out of range for data type '%4!s!'. ...
  35. Clustered indexes, which are the default for primary keys, are not supported with %1!s!. Specify a NONCLUSTERED index instead. ...
  36. CLUSTERPROBABILITY=3=[ClusterID expression]=The ClusterProbability function returns the probability of the input case belonging ...
  37. Code-based security in managed code was not set because of the following error: %1[%{exception/}%]%[;%{exceptioninner/}%]. ...
  38. Collation '%1!s!' is supported on Unicode data types only. Unicode-only collations cannot be used to specify partition function ...
  39. Collation '%1!s!' will be removed in a future version of SQL Server. Avoid using this collation in new development work, ...
  40. Collation cannot be specified when adding a brick to a matrix. Remove the command prompt parameter {0}, and then rerun Setup. ...
  41. Collation Compatible and Collation Name are mutually exclusive options. If you select Collation Compatible, the Collation ...
  42. Collation Name and Collation Compatible are mutually exclusive options. If you select a Collation Name, the Collation Compatible ...
  43. Collation of partition column '%1!s!' does not match collation of corresponding parameter in partition function '%2!s!'. ...
  44. Collect query hash. Use this to identify queries with similar logic. You can use the query hash to determine the aggregate ...
  45. Collect query plan hash. Use this to identify similar query execution plans. You can use query plan hash to find the cumulative ...
  46. Collection of event classes that are produced by the execution of MS DTC or SQL transactions or by writing to the transaction ...
  47. Collection of event classes that are produced when a SQL Server error or warning occurs (for example, an error during the ...
  48. Collection of showplan event classes and event classes that are produced from the execution of SQL data manipulation language ...
  49. Collects all ExecStatusChanged events since the trace was started, such as one generated for prior to execution of tasks, ...
  50. Collects all new connection events since the trace was started, such as when a client requests a connection to a server running ...
  51. Collects all PostValidate events since the trace was started, such as one generated for prior to execution of tasks, etc. ...
  52. Collects all VariableValueChanged events since the trace was started, such as one generated for prior to execution of tasks, ...
  53. Collects query statistics, T-SQL text, and query plans of most of the statements that affect performance. Enables analysis ...
  54. Collects top-level performance indicators for the computer and the Database Engine. Enables analysis of resource use, resource ...
  55. Column "%1!s!.%2!s!" is invalid in the ORDER BY clause because it is not contained in an aggregate function and there is ...
  56. Column "%1!s!.%2!s!" is invalid in the ORDER BY clause because it is not contained in either an aggregate function or the ...
  57. Column "{0}" has precision {1}, and this adapter supports a maximum precison of 29. Decrease the precison of the input column ...
  58. Column "{0}" is already mapped. Please consider using duplicate column transform if you want to map the same source column ...
  59. Column %1!s! cannot be published because it uses an unsupported data type %2!s!]. View supported data types by querying msdb.dbo.sysdatatypemappings. ...
  60. Column %1!u! of the Table-Valued Parameter Rowset was marked as ordered. However the ordering type specified %2!u! was neither ...
  61. Column %{name/} is part of composite key, but not all columns of the composite key are included in the expression or its ...
  62. Column ' ' is used to enforce the full-text key on table ' ' and must be bytes or less. This change will disable full-text ...
  63. Column ' ' participates in full-text indexing on table ' '. After this change, the column will no longer participate in the ...
  64. Column '%1!s!' cannot be added or modified in article '%2!s!' of publication '%3!s!'. The DDL operatoin on hierarchyid and ...
  65. Column '%1!s!' cannot be altered online to an XML type that has a schema collection. The operation must be performed offline. ...
  66. Column '%1!s!' cannot be excluded from a vertical partition because it is neither nullable nor defined with a default value. ...
  67. Column '%1!s!' cannot be included in a vertical partition because it is neither nullable nor defined with a default value. ...
  68. Column '%1!s!' cannot be part of the distribution key of the index '%2!s!' because the column is not part of the unique index ...
  69. Column '%1!s!' cannot be passed as a parameter for a BLOCK security predicate because the column definition contains an expression ...
  70. Column '%1!s!' cannot be passed as a parameter for an AFTER UPDATE or AFTER INSERT BLOCK security predicate for this view ...
  71. Column '%1!s!' cannot be used as full-text type column for image column. It must be a character-based column with a size ...
  72. Column '%1!s!' cannot be used for full-text search because it is not a character-based, XML, image or varbinary(max) type ...
  73. Column '%1!s!' in %2!s! '%3!s!' cannot be used in an index or statistics or as a partition key because it depends on a non-schemabound ...
  74. Column '%1!s!' in %2!s! '%3!s!' cannot be used in an index or statistics or as a partition key because it does user or system ...
  75. Column '%1!s!' in %2!s! '%3!s!' cannot be used in an index or statistics or as a partition key because it is non-deterministic. ...