SQL Server 2008 R2
- Collects all VariableValueChanged events since the trace was started, such as one generated for prior to execution of tasks, ...
- Collects query statistics, T-SQL text, and query plans of most of the statements that affect performance. Enables analysis ...
- Collects top-level performance indicators for the computer and the Database Engine. Enables analysis of resource use, resource ...
- Column "%1!s!.%2!s!" is invalid in the ORDER BY clause because it is not contained in an aggregate function and there is ...
- Column "%1!s!.%2!s!" is invalid in the ORDER BY clause because it is not contained in either an aggregate function or the ...
- Column %1!s! cannot be published because it uses an unsupported data type %2!s!]. View supported data types by querying msdb.dbo.sysdatatypemappings. ...
- Column %1!u! of the Table-Valued Parameter Rowset was marked as ordered. However the ordering type specified %2!u! was neither ...
- Column ' ' is used to enforce the full-text key on table ' ' and must be bytes or less. This change will disable full-text ...
- Column ' ' participates in full-text indexing on table ' '. After this change, the column will no longer participate in the ...
- Column '%1!s!' cannot be added or modified in article '%2!s!' of publication '%3!s!'. The DDL operatoin on hierarchyid and ...
- Column '%1!s!' cannot be excluded from a vertical partition because it is neither nullable nor defined with a default value. ...
- Column '%1!s!' cannot be included in a vertical partition because it is neither nullable nor defined with a default value. ...
- Column '%1!s!' cannot be used as full-text type column for image column. It must be a character-based column with a size ...
- Column '%1!s!' cannot be used for full-text search because it is not a character-based, XML, image or varbinary(max) type ...
- 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 ...
- 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 ...
- 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. ...
- Column '%1!s!' is partitioning column of the index '%2!s!'. Partition columns for a unique index must be a subset of the ...
- Column '%1!s!' of table '%2!s!' cannot be excluded from a vertical partition because there is a computed column that depends ...
- Column '%1!s!.%2!s!' cannot be referenced in the OUTPUT clause because the column definition contains a subquery or references ...
- Column '%1!s!.%2!s!' is invalid in the HAVING clause because it is not contained in an aggregate function and there is no ...
- Column '%1!s!.%2!s!' is invalid in the HAVING clause because it is not contained in either an aggregate function or the GROUP ...
- 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 ...
- Column '%1!s!.%2!s!' is invalid in the select list because it is not contained in either an aggregate function or the GROUP ...
- 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 ...
- Column '%{ColId/}' count of segments is different from partition segments count. Possible cause for this issue is table matadata ...
- Column '%{IWColumnName/}' of table '%{IWTableName/}' has a RowNumberBinding, but the type of the attribute is not RowNumber. ...
- Column '{0}' in the returned table is of type 'geography', 'geometry', or 'hierarchyid', which are not supported in a data-tier ...
- column '{1}' is of user-defined data type {2} which is of type {3}]. Type {3} is not supported in the target database version, ...
- Column information for column %1!d! of table '%2' was not found at the subscriber. The subscription table at the subscriber ...
- Column information for column '%1' of table '%2' was not found at the subscriber. The subscription table at the subscriber ...
- Column information for the source and the destination data could not be retrieved, or the data types of source columns were ...
- Column name "%1!s!" on output "%2!s!" cannot be used because it conflicts with a column of the same name on synchronous input ...
- Column name "{0}" in output "{1}" cannot be used because it conflicts with a column of the same name on synchronous input ...
- Column name missing for column defintion. Column will be deleted. To correct, choose cancel and specify the name of the column. ...
- Column name: {0} Data type: {1} Length: {2} Scale: {3} Precision: {4} Code page: {5} Sort Key Position: {6} Source Component: ...
- Column names in each view or function must be unique. Column name '%1!s!' in view or function '%2!s!' is specified more than ...
- Column or parameter #%1!s!: Invalid fractional second precision %2!s! specified for %3!s! data type. The maximum fractional ...
- Column segment data size is incorrect for table '%{IMBITableId/}'. Either the partition file '%{strPartFileName/}' is corrupt ...
- Column segment data size is incorrect for table '%{IWTableName/}'. Either the partition file '%{strPartFileName/}' is corrupt ...
- Column {0} of a table-valued parameter is computed or default and has ordering or uniqueness set. This is only allowed for ...
- Column {0} of table {1} is a computed column with constraint of type {2}. This constraint is not supported on computed columns ...
- ColumnName descriptor in the descriptor file on path {0} is invalid. The schema table does not contain a column with the ...
- Columns in this expression have incompatibale collations. The generation of the collate clause would be incompatibe with ...
- Columns specified in the captured column list could not be mapped to columns in source table '%1!s!.%2!s!'. Verify that the ...
- Columns used to uniquely identify a row for net change tracking must be included in the list of captured columns. Add either ...
- Columns with lineage IDs %1!d! and %2!d! have mismatched metadata. The input column that is mapped to an output column does ...
- Columns with lineage IDs %1!d! and %2!d! have mismatched metadata. The input column that is mapped to an output column for ...
- Command was executed to reposition to the start of the rowset. Either the order of the columns changed, or columns were added ...
- Commit operation cannot be executed since it is attempting to materialize cell writebacks and modify the contents of the ...
- Common language runtime (CLR) execution is not supported under lightweight pooling. Disable one of two options: "clr enabled" ...
- Common language runtime (CLR) integration enables you to write stored procedures, triggers, user-defined types and user-defined ...
- Common reasons for this problem include that the server is not installed, the service is not started or the server is upgrading ...
- Communications to the remote server instance '%1!s!' failed before database mirroring was fully started. The ALTER DATABASE ...
- Communications to the remote server instance '%1!s!' failed to complete before its timeout. The ALTER DATABASE command may ...
- Compares the value of a numeric expression in one period to a previous period, as a percentage of the previous period's value. ...
- complete for pool . {2} Delete for {2} blobs attempted, {3} blobs were deleted. {4} blobs were not found in the blob store. ...
- Complete metadata information for the data source column "%1!s!" is not available. Make sure the column is correctly defined ...
- Complete: implements extensive change tracking at the Publisher to support data transformations and advanced row filtering ...
- Component "%1!s!" (%2!d!) has been removed from the Data Flow task because its output is not used and its inputs either have ...
- Component "%1!s!" could not be created and returned error code 2!8.8X!. Make sure that the component is registered correctly. ...
- Component '%1!s!' is outside of allowed range. Maximum for 'fractionDigits' is 10 and maximum number of digits for non fractional ...
- Component ID {0} is not valid. Valid components include Database Engine, Analysis Services, DTS, Reporting Services and Integration ...
- Component Services (COM+ 1.0) are not installed on this computer. This installation requires Component Services in order ...
- Component with name "{0}" and class ID "{1}" could not be created because a module it uses could not be found. Verify that ...
- Component with name "{0}" and class ID "{1}" could not be created because an error was encountered during its upgrade to ...
- Component with name "{0}" and class ID "{1}" could not be created because it was built with a version newer than the one ...
- Compressing tables with sparse columns or column sets is not supported by the stored procedure sp_estimate_data_compression_savings. ...
- Compression for the '%{IMBITableId/}' table completed in '%d{steps/}' steps with '%d{clusters/}' clusters computed in total. ...
- Compression for the '%{IMBITableId/}' table completed in '%d{steps/}' steps with '%d{clusters/}' clusters computed in total. ...
- Computed column '%1!s!' cannot be used as full-text type column for image or varbinary(MAX) column. This computed column ...
- Computed column '%1!s!' cannot be used for full-text search because it is nondeterministic or imprecise nonpersisted computed ...
- Computed column '%1!s!' in table '%2!s!' cannot be persisted because the column type, '%3!s!', is a non-byte-ordered CLR ...
- Computed column cannot be used as a partition key if it is not persisted. Partition key column '%1!s!' in table '%2!s!' is ...
- Computed columns and CLR types cannot be checked for object ID %1!s! (object "%2!s!") because the internal expression evaluator ...