SQL Server 2016

  1. Communications to the remote server instance '%1!s!' failed before database mirroring was fully started. The ALTER DATABASE ...
  2. Communications to the remote server instance '%1!s!' failed to complete before its timeout. The ALTER DATABASE command may ...
  3. Compacts an input data flow by pivoting it on a column value, making it less normalized. The input data should be sorted ...
  4. Compares the value of a numeric expression in one period to a previous period, as a percentage of the previous period's value. ...
  5. Comparison, sorting, and manipulation of character strings that do not use a *_BIN2 collation is not supported with %1!s!. ...
  6. complete for pool . {2} Delete for {2} blobs attempted, {3} blobs were deleted. {4} blobs were not found in the blob store. ...
  7. Complete metadata information for the data source column "%1!s!" is not available. Make sure the column is correctly defined ...
  8. Complete: implements extensive change tracking at the Publisher to support data transformations and advanced row filtering ...
  9. Component "%1!s!" (%2!d!) has been removed from the Data Flow task because its output is not used and its inputs either have ...
  10. Component "%1!s!" could not be created and returned error code 2!8.8X! "%3!s!". Make sure that the component is registered ...
  11. Component %1!s! from brick %2!s! reported that the component %3!s! in brick %4!s! is in a suspicious state because of the ...
  12. Component %1!s! reported that the component %2!s! in brick %3!s! is in a suspicious state because of the error: %4!s!, severity: ...
  13. Component '%1!s!' is outside of allowed range. Maximum for 'fractionDigits' is 10 and maximum number of digits for non fractional ...
  14. Component Services (COM+ 1.0) are not installed on this computer. This installation requires Component Services in order ...
  15. Component with name "{0}" and class ID "{1}" could not be created because a module it uses could not be found. Verify that ...
  16. Component with name "{0}" and class ID "{1}" could not be created because an error was encountered during its upgrade to ...
  17. Component with name "{0}" and class ID "{1}" could not be created because it was built with a version newer than the one ...
  18. Component {0} has no inputs, or all of its inputs are already connected to other outputs. You may be able to edit the component ...
  19. Compressed history target could not add package '%I32u' to the package occurrence list. Events from this package will not ...
  20. Compressed history target could not add package '%ws' to the package occurrence list. Events from this package will not be ...
  21. Compressing segment %d{segment/} of column '%{IMBIColumnId/}' for the '%{IMBITableId/}' table '%{IMBIPartitionId/}' partition ...
  22. Compressing tables with sparse columns or column sets is not supported by the stored procedure sp_estimate_data_compression_savings. ...
  23. Compression for the segment '%d{segment/}' of the '%{IMBITableId/}' table '%{IMBIPartitionId/}' partition completed in '%d{steps/}' ...
  24. Compression for the segment '%d{segment/}' of the '%{IMBITableId/}' table '%{IMBIPartitionId/}' partition completed in '%d{steps/}' ...
  25. Compression for the segment '%d{segment/}' of the '%{IMBITableId/}' table completed in '%d{steps/}' steps with '%d{clusters/}' ...
  26. Compression for the segment '%d{segment/}' of the '%{IMBITableId/}' table completed in '%d{steps/}' steps with '%d{clusters/}' ...
  27. Computed column '%1!s!' cannot be used as full-text type column for image or varbinary(MAX) column. This computed column ...
  28. Computed column '%1!s!' cannot be used for full-text search because it is nondeterministic or imprecise nonpersisted computed ...
  29. Computed column '%1!s!' in table '%2!s!' cannot be persisted because the column type, '%3!s!', is a non-byte-ordered CLR ...
  30. Computed column cannot be used as a partition key if it is not persisted. Partition key column '%1!s!' in table '%2!s!' is ...
  31. Computed column is defined with a user-defined function which is not allowed with system-versioned table '%1!s!' because ...
  32. Computed columns and CLR types cannot be checked for object ID %1!s! (object "%2!s!") because the internal expression evaluator ...
  33. Computing the expression "%1!s!" failed with error code 2!8.8X!. The expression may have errors, such as divide by zero, ...
  34. Com[mandFile filespec Optional. Loads a text file that contains additional dtexec command options, prior to package execution. ...
  35. Condition cannot be specified for Column member '{0}' because it is marked with a 'Computed' or 'Identity' StoreGeneratedPattern. ...
  36. Condition member '{0}' with a condition other than 'IsNull=False' is mapped. Either remove the condition on {0} or remove ...
  37. Configuration block version %1!s! is not a valid version number. SQL Server is exiting. Restore the master database or reinstall. ...
  38. Configuration data for the availability group with Windows Server Failover Clustering (WSFC) resource ID '%1!s!' is not found ...
  39. Configuration failure. This is a generic warning for all configuration types. Other warnings should precede this with more ...
  40. Configuration manager agent cannot '%1!s!' '%2!s!' due to invalid state '%3!s!'. This is a fatal error affecting system functionality ...
  41. Configuration manager agent cannot '%1!s!' '%2!s!'. Examine previous logged messages to determine cause of this error. This ...
  42. Configuration manager agent cannot send reported error to configuration manager due to error %1!s!, state %2!s!, severity ...
  43. Configuration manager agent encountered error %1!s!, state %2!s!, severity %3!s! while updating brick incarnation to %5!s!. ...
  44. Configuration manager agent encountered error %1!s!, state %2!s!, severity %3!s! while updating state information. Examine ...
  45. Configuration manager agent enlistment encountered error %1!s!, state %2!s!, severity %3!s! and is shutting down. This is ...
  46. Configuration manager agent enlistment failed due to different enlistment protocol versions between manager and agent. Version ...
  47. Configuration manager agent initialization failed. See previous errors in error log. This is a serious error condition and ...
  48. Configuration manager agent is ignoring stale message from manager brick %1!s! due to '%2!s!' mismatch. Expected %3!s! but ...
  49. Configuration manager agent thread encountered fatal exception (error: %1!s! severity: %2!s! state: %3!s!). This is a serious ...
  50. Configuration manager cannot '%1!s!' '%2!s!'. Examine previous logged messages to determine cause of this error. This is ...
  51. Configuration manager cannot initialize communication object. Examine previous logged messages to determine cause of this ...
  52. Configuration manager cannot perform action %1!s! on other bricks in the matrix due to error %2!s!, state %3!s!, severity ...
  53. Configuration manager could not write the WMI offline configuration file during the execution of stored procedure '%1!s!'. ...
  54. Configuration manager enlistment denied join of brick . Machine architecture mismatch. Agent machine architecture , manager ...
  55. Configuration manager enlistment denied join of brick . Server default collation mismatch. Agent collation , manager collation ...
  56. Configuration manager enlistment denied join of brick . SQL version or build number mismatch. Agent version , manager version ...
  57. Configuration manager enlistment denied join of brick . Supported number of bricks mismatch. Agent supported number of bricks ...
  58. Configuration manager enlistment encountered error %1!s!, state %2!s!, severity %3!s! and is shutting down. This is a serious ...
  59. Configuration manager enlistment encountered error %1!s!, state %2!s!, severity %3!s! while sending enlistment reply to brick ...
  60. Configuration manager enlistment encountered error %1!s!, state %2!s!, severity %3!s! while updating brick incarnation to ...
  61. Configuration manager enlistment is ignoring message from brick . Enlistment protocol version mismatch. Agent version , manager ...
  62. Configuration manager enlistment is ignoring stale message from brick %1!s! due to '%2!s!' mismatch. Expected %3!s! but received ...
  63. Configuration manager enlistment is queuing a failure request for brick due to receiving new enlistment request from this ...
  64. Configuration manager error handler initialization failed due to error %1!s!, state %2!s!, severity %3!s!. This is a serious ...
  65. Configuration manager is evicting brick from which it did not receive expected reply during communication. This also includes ...
  66. Configuration manager thread encountered fatal exception (error: %1!s! state: %2!s! severity: %3!s!). This is a serious error ...
  67. Configuration registry key "%1!s!" was not found. A configuration entry specifies a registry key that is not available. Check ...
  68. Configure a URL to access Web Portal. Click Advanced to define multiple URLs, or to specify additional parameters on the ...
  69. Configure a URL used to access the Report Server. Click Advanced to define multiple URLs for a single Report Server instance, ...
  70. Configure an account to be used by subscriptions to access file shares. Use an account with as minimum permissions as possible ...
  71. Configure Database Mail for the Master Data Services database. After a profile is created, you must use SQL Server Management ...
  72. Configure parameter bindings for the child package. Note: Parameters from externally referenced child packages are ignored. ...
  73. Configure peer nodes and peer connections. To specify configuration options, right-click a node, a connection, or the design ...
  74. Configure the file connection properties to reference a group of files and directories that exist or are created at run time. ...
  75. Configure the properties required to perform file system operations, such as creating, moving, or deleting files or directories. ...