SQL Server 2008

  1. Column '%1!s!' of table '%2!s!' cannot be excluded from a vertical partition because there is a computed column that depends ...
  2. Column '%1!s!.%2!s!' cannot be referenced in the OUTPUT clause because the column definition contains a subquery or references ...
  3. Column '%1!s!.%2!s!' is invalid in the HAVING clause because it is not contained in an aggregate function and there is no ...
  4. Column '%1!s!.%2!s!' is invalid in the HAVING clause because it is not contained in either an aggregate function or the GROUP ...
  5. 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 ...
  6. Column '%1!s!.%2!s!' is invalid in the select list because it is not contained in either an aggregate function or the GROUP ...
  7. 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 ...
  8. column '{1}' is of user-defined data type {2} which is of type {3}]. Type {3} is not supported in the target database version, ...
  9. Column information for column %1!d! of table '%2' was not found at the subscriber. The subscription table at the subscriber ...
  10. Column information for column '%1' of table '%2' was not found at the subscriber. The subscription table at the subscriber ...
  11. Column information for the source and the destination data could not be retrieved, or the data types of source columns were ...
  12. Column name "%1!s!" on output "%2!s!" cannot be used because it conflicts with a column of the same name on synchronous input ...
  13. Column name "{0}" in output "{1}" cannot be used because it conflicts with a column of the same name on synchronous input ...
  14. Column name missing for column defintion. Column will be deleted. To correct, choose cancel and specify the name of the column. ...
  15. Column name: {0} Data type: {1} Length: {2} Scale: {3} Precision: {4} Code page: {5} Sort Key Position: {6} Source Component: ...
  16. Column names in each view or function must be unique. Column name '%1!s!' in view or function '%2!s!' is specified more than ...
  17. Column or parameter #%1!s!: Invalid fractional second precision %2!s! specified for %3!s! data type. The maximum fractional ...
  18. Column {0} of a table-valued parameter is computed or default and has ordering or uniqueness set. This is only allowed for ...
  19. Column {0} of table {1} is a computed column with constraint of type {2}. This constraint is not supported on computed columns ...
  20. ColumnName descriptor in the descriptor file on path {0} is invalid. The schema table does not contain a column with the ...
  21. Columns in this expression have incompatibale collations. The generation of the collate clause would be incompatibe with ...
  22. Columns specified in the captured column list could not be mapped to columns in source table '%1!s!.%2!s!'. Verify that the ...
  23. Columns used to uniquely identify a row for net change tracking must be included in the list of captured columns. Add either ...
  24. Columns with lineage IDs %1!d! and %2!d! have mismatched metadata. The input column that is mapped to an output column does ...
  25. Columns with lineage IDs %1!d! and %2!d! have mismatched metadata. The input column that is mapped to an output column for ...
  26. Command was executed to reposition to the start of the rowset. Either the order of the columns changed, or columns were added ...
  27. Common language runtime (CLR) execution is not supported under lightweight pooling. Disable one of two options: "clr enabled" ...
  28. Common language runtime (CLR) integration enables you to write stored procedures, triggers, user-defined types and user-defined ...
  29. Common reasons for this problem include that the server is not installed, the service is not started or the server is upgrading ...
  30. Communications to the remote server instance '%1!s!' failed before database mirroring was fully started. The ALTER DATABASE ...
  31. Communications to the remote server instance '%1!s!' failed to complete before its timeout. The ALTER DATABASE command may ...
  32. Compares the value of a numeric expression in one period to a previous period, as a percentage of the previous period's value. ...
  33. complete for pool . {2} Delete for {2} blobs attempted, {3} blobs were deleted. {4} blobs were not found in the blob store. ...
  34. Complete metadata information for the data source column "%1!s!" is not available. Make sure the column is correctly defined ...
  35. Complete: implements extensive change tracking at the Publisher to support data transformations and advanced row filtering ...
  36. Component "%1!s!" (%2!d!) has been removed from the Data Flow task because its output is not used and its inputs either have ...
  37. Component "%1!s!" could not be created and returned error code 2!8.8X!. Make sure that the component is registered correctly. ...
  38. Component '%1!s!' is outside of allowed range. Maximum for 'fractionDigits' is 10 and maximum number of digits for non fractional ...
  39. Component ID {0} is not valid. Valid components include Database Engine, Analysis Services, DTS, Reporting Services and Integration ...
  40. Component Services (COM+ 1.0) are not installed on this computer. This installation requires Component Services in order ...
  41. Component with name "{0}" and class ID "{1}" could not be created because a module it uses could not be found. Verify that ...
  42. Component with name "{0}" and class ID "{1}" could not be created because an error was encountered during its upgrade to ...
  43. Component with name "{0}" and class ID "{1}" could not be created because it was built with a version newer than the one ...
  44. Compressing tables with sparse columns or column sets is not supported by the stored procedure sp_estimate_data_compression_savings. ...
  45. Computed column '%1!s!' cannot be used as full-text type column for image or varbinary(MAX) column. This computed column ...
  46. Computed column '%1!s!' cannot be used for full-text search because it is nondeterministic or imprecise nonpersisted computed ...
  47. Computed column '%1!s!' in table '%2!s!' cannot be persisted because the column type, '%3!s!', is a non-byte-ordered CLR ...
  48. Computed column cannot be used as a partition key if it is not persisted. Partition key column '%1!s!' in table '%2!s!' is ...
  49. Computed columns and CLR types cannot be checked for object ID %1!s! (object "%2!s!") because the internal expression evaluator ...
  50. Computer {0} does not exist on the network, or the computer cannot be configured remotely. Verify that the remote computer ...
  51. Computing the expression "%1!s!" failed with error code 2!8.8X!. The expression may have errors, such as divide by zero, ...
  52. Com[mandFile filespec Optional. Loads a text file that contains additional dtexec command options, prior to package execution. ...
  53. Configuration block version %1!s! is not a valid version number. SQL Server is exiting. Restore the master database or reinstall. ...
  54. Configuration failure. This is a generic warning for all configuration types. Other warnings should precede this with more ...
  55. Configuration registry key "%1!s!" was not found. A configuration entry specifies a registry key that is not available. Check ...
  56. Configure a URL to access Report Manager. Click Advanced to define multiple URLs, or to specify additional parameters on ...
  57. Configure a URL used to access the Report Server. Click Advanced to define multiple URLs for a single Report Server instance, ...
  58. Configure peer nodes and peer connections. To specify configuration options, right-click a node, a connection, or the design ...
  59. Configure the file connection properties to reference a group of files and directories that exist or are created at run time. ...
  60. Configure the properties required to perform file system operations, such as creating, moving, or deleting files or directories. ...
  61. Configure the properties that identify the DDL statements to use and the Analysis Services connection used to submit those ...
  62. Configure the properties to divide the transformation input into a sample and a leftovers output, using a percentage to specify ...
  63. Configure the properties to train data mining models by passing the data that the destination receives to data mining model ...
  64. Configure the properties used run to a WMI Query Language (WQL) query that returns Windows Management Instrumentation (WMI) ...
  65. Configure the properties used to apply string operations to columns with character data. Place the operation result in a ...
  66. Configure the properties used to convert the data type of an input column to a different data type. Depending on the data ...
  67. Configure the properties used to divide the transformation input into a sample and a leftovers output, using a number to ...
  68. Configure the properties used to extract terms from an input column by identifying nouns and noun phrases that appear in ...
  69. Configure the properties used to import text files into a SQL Server table. You cannot validate, clean, or transform data ...
  70. Configure the properties used to join two sources of sorted data. Select the join type and then specify the columns to be ...
  71. Configure the properties used to look up values in a reference table and learn the frequency that terms appear in a dataset. ...
  72. Configure the properties used to perform a lookup operation between an input dataset and a reference dataset using a best-match ...
  73. Configure the properties used to perform group by operations and to calculate aggregate values. Optionally, apply comparison ...
  74. Configure the properties used to send and receive files from an FTP server and to manage directories and files on local and ...
  75. Configure the properties used to send or receive string, variable, and data file messages when executing an SSIS package. ...