SQL Server 2016

  1. Column '%1!s!' is partitioning column of the index '%2!s!'. Partition columns for a unique index must be a subset of the ...
  2. Column '%1!s!' is used in the temporal period '%2!s!' and cannot be explicitly placed in the key list of a constraint where ...
  3. Column '%1!s!' of table '%2!s!' cannot be excluded from a vertical partition because there is a computed column that depends ...
  4. Column '%1!s!.%2!s!' cannot be referenced in the OUTPUT clause because the column definition contains a subquery or references ...
  5. Column '%1!s!.%2!s!' cannot be referenced in the OUTPUT clause because the column definition contains an expression using ...
  6. Column '%1!s!.%2!s!' is encrypted using a randomized encryption type and is therefore not valid for use as a key column in ...
  7. Column '%1!s!.%2!s!' is invalid in the HAVING clause because it is not contained in an aggregate function and there is no ...
  8. Column '%1!s!.%2!s!' is invalid in the HAVING clause because it is not contained in either an aggregate function or the GROUP ...
  9. Column '%1!s!.%2!s!' is invalid in the select list because it is not contained in an aggregate function and there is no GROUP ...
  10. Column '%1!s!.%2!s!' is invalid in the select list because it is not contained in either an aggregate function or the GROUP ...
  11. Column '%1!s!.%2!s!' is not the same length or scale as referencing column '%3!s!.%4!s!' in foreign key '%5!s!'. Columns ...
  12. Column '%{ColId/}' count of segments is different from partition segments count. Possible cause for this issue is table metadata ...
  13. Column '%{column/}' in table '%{table/}' does not have its source pipeline rowset column specified. Either provide out-of-line ...
  14. Column '%{column/}' in table '%{table/}' has the InferredName set, only columns from a calculated table can have inferred ...
  15. Column '%{IMBIColumnId/}' in Table '%{IMBITableId/}' contains a duplicate value '%{value/}' and this is not allowed for columns ...
  16. Column '%{IMBIColumnId/}' in Table '%{IMBITableId/}' contains blank values and this is not allowed for columns on the one ...
  17. Column '%{IWColumnName/}' in Table '%{IWTableName/}' contains a duplicate value '%{value/}' and this is not allowed for columns ...
  18. Column '%{IWColumnName/}' in Table '%{IWTableName/}' contains blank values and this is not allowed for columns on the one ...
  19. Column '%{IWColumnName/}' of table '%{IWTableName/}' has a RowNumberBinding, but the type of the attribute is not RowNumber. ...
  20. column '{1}' is of user-defined data type {2} which is of type {3}]. Type {3} is not supported in the target database version, ...
  21. Column encryption keys are used to encrypt sensitive data stored in database columns. All values in the selected columns ...
  22. Column encryption keys are used to encrypt sensitive data stored in database columns. All values in the selected columns ...
  23. Column encryption keys protect your data, and column master keys protect your column encryption keys. This lets you manage ...
  24. Column expressions and data sources without names or aliases cannot be formatted as JSON text using FOR JSON clause. Add ...
  25. column in table {1} is part of a primary key or unique key index. Unique keys and primary keys can only be enforced on the ...
  26. Column information for column %1!d! of table '%2' was not found at the subscriber. The subscription table at the subscriber ...
  27. Column information for column '%1' of table '%2' was not found at the subscriber. The subscription table at the subscriber ...
  28. Column information for the source and the destination data could not be retrieved, or the data types of source columns were ...
  29. Column master key rotation is a process that changes which master key is protecting a set of column encryption keys. This ...
  30. Column master keys are protecting keys used to encrypt column encryption keys. Column master keys must be stored in a trusted ...
  31. Column master keys are protecting keys used to encrypt column encryption keys. Column master keys must be stored in a trusted ...
  32. Column name "%1!s!" on output "%2!s!" cannot be used because it conflicts with a column of the same name on synchronous input ...
  33. Column name "{0}" in output "{1}" cannot be used because it conflicts with a column of the same name on synchronous input ...
  34. Column name missing for column defintion. Column will be deleted. To correct, choose cancel and specify the name of the column. ...
  35. Column name: {0} Data type: {1} Length: {2} Scale: {3} Precision: {4} Code page: {5} Sort Key Position: {6} Source Component: ...
  36. Column names in each view or function must be unique. Column name '%1!s!' in view or function '%2!s!' is specified more than ...
  37. Column or parameter #%1!s!: Invalid fractional second precision %2!s! specified for %3!s! data type. The maximum fractional ...
  38. Column or parameter '%1!s!' has type '%2!s!' and collation '%3!s!'. The legacy LOB types do not support Unicode supplementary ...
  39. Column reference to '%{column/}' in table '%{table/}' cannot be used with a variation '%{variationColumn/}' because it does ...
  40. Column segment data size is incorrect for table '%{IMBITableId/}'. Either the partition file '%{strPartFileName/}' is corrupt ...
  41. Column segment data size is incorrect for table '%{IWTableName/}'. Either the partition file '%{strPartFileName/}' is corrupt ...
  42. Column store index '%1!s!' on table '%2!s!' has erroneous content in its Delete Bitmap with rowgroup_id %3!s! and tuple_id ...
  43. Column {0} is used in a Not Null condition but it is mapped to a property {1} which is nullable. Consider making this property ...
  44. Column {0} of a table-valued parameter is computed or default and has ordering or uniqueness set. This is only allowed for ...
  45. Column {0} of table {1} is a computed column with constraint of type {2}. This constraint is not supported on computed columns ...
  46. column/} is not a valid reference to a column in a table. Please provide a table name in front of the column name or fix ...
  47. Column: {0} is not one of the supported custom date/time columns (date, datetime, datetime2, smalldatetime, datetimeoffset) ...
  48. ColumnName descriptor in the descriptor file on path {0} is invalid. The schema table does not contain a column with the ...
  49. ColumnName/}' in table '%{TableName/}' is a calculated column and cannot be used in model with DirectQuery mode enabled. ...
  50. Columns in this expression have incompatibale collations. The generation of the collate clause would be incompatibe with ...
  51. Columns of Binary type cannot be used in user defined hierarchies. The column '%{IWColumnName/}' in the table '%{IWTableName/}' ...
  52. Columns of type Binary cannot be used in user-defined hierarchies. The column '%{column/}' in table '%{table/}' is defined ...
  53. Columns specified in the captured column list could not be mapped to columns in source table '%1!s!.%2!s!'. Verify that the ...
  54. Columns used to uniquely identify a row for net change tracking must be included in the list of captured columns. Add either ...
  55. Columns with Column Usage set to DAX Usage cannot be used in the Where, Order By or Distinct clauses when Query mode is set ...
  56. Columns with lineage IDs %1!d! and %2!d! have mismatched metadata. The input column that is mapped to an output column does ...
  57. Columns with lineage IDs %1!d! and %2!d! have mismatched metadata. The input column that is mapped to an output column for ...
  58. Columnstore index '%1!s!' cannot be created, because table '%2!s!' has columns stored off-row. Columnstore indexes can only ...
  59. Columnstore index '%1!s!' on table '%2!s!' has metadata mismatch on column id %3!s! and rowgroup id %4!s!. If this is a nonclustered ...
  60. Columnstore index has one or more data values that are inconsistent with data values within the metadata. Please run DBCC ...
  61. Columnstore index has one or more data values that do not match data values in a dictionary. Please run DBCC CHECKDB for ...
  62. columnstore indexes are not supported in the current SQL Server edition. See SQL Server Books Online for supported editions ...
  63. Combine data from an external worksheet into the {0} entity. To do this, map the entity's columns with columns from the external ...
  64. Combine two sorted data flows into one using the FULL, LEFT, or INNER join. We recommend this transformation when data flows ...
  65. Combines rows from multiple data flows without sorting. For example, add rows back to a data flow after correction of errors. ...
  66. Combines rows from multiple sorted data flows into one sorted data flow. Unlike the Merge Join, all rows flow to the output. ...
  67. Command InternalProcessPartitions is supported only by server running in VertiPaq mode and AzureMode with ScaleOut enabled. ...
  68. Command was executed to reposition to the start of the rowset. Either the order of the columns changed, or columns were added ...
  69. Commit operation cannot be executed since it is attempting to materialize cell writebacks and modify the contents of the ...
  70. Common language runtime (CLR) execution is not supported under lightweight pooling. Disable one of two options: "clr enabled" ...
  71. Common language runtime (CLR) integration enables you to write stored procedures, triggers, user-defined types and user-defined ...
  72. Common reasons for this problem include that the server is not installed, the service is not started or the server is upgrading ...
  73. Communication involving configuration manager and agent cannot be initialized due to error %1!s!, state %2!s!, severity %3!s!. ...
  74. Communication involving configuration manager and agent is ignoring stale message from brick to brick due to '%3!s!' mismatch. ...
  75. Communication involving configuration manager and agent is unable to send message from brick to brick due to error %3!s!, ...