SQL Server 2016

  1. The "%1!s!" node cannot be found in custom default persistence. This error occurs if the default saved XML of an extensible ...
  2. The "%1!s!" on "%2!s!" has usage type READONLY, but is not referenced by an expression. Remove the column from the list of ...
  3. The "%1!s!" references "%2!s!", and that column is not the correct type. It must be DT_TEXT, DT_NTEXT, or DT_IMAGE. A reference ...
  4. The "%1!s!" references column ID %2!d!, and that column is not found on the input. A reference points to a nonexistent column. ...
  5. The "%1!s!" was unable to make the requested change to the input column with lineage ID %2!d!. The request failed with error ...
  6. The "%1!s!" XML element (in the "%2!s!" namespace) in the "%3!s!" element (in the "%4!s!" namespace) of the SOAP request ...
  7. The "%1!s!" XML element (in the "%2!s!" namespace) was expected in the "%3!s!" element (in the "%4!s!" namespace) of the ...
  8. The "%1" property was attempted to be set for column %2!Iu!. The column was either of type bit or a blob type for which this ...
  9. The "%3!s!" property is required on input column "%1!s!" (%2!d!), but is not found. The missing property should be added. ...
  10. The "context" argument for the CHANGE_TRACKING_CONTEXT WITH clause must be of type varbinary data type with a maximum length ...
  11. The "date part" parameter specified for a date function is not valid. "Date part" parameters must be static strings, and ...
  12. The "LogID" variable was not found in the scope of component: %s, logging at the collection set level. Original message: ...
  13. The "SSPROP_COL_UDT_NAME" property was not set for column %1!Iu!. This property must be set for user-defined types. InMemory ...
  14. The "table" or "DBTYPE_TABLE" type specified for column %1!Iu! is only supported as type of a command parameter. InMemory ...
  15. The "{0}" account validation failed. This can be because of any of the following reasons: remote server is down, incorrect ...
  16. The %1 extension failed to read its configuration settings from the %2 configuration file. The extension is not available ...
  17. The %1 extension failed to read its configuration settings from the %2 configuration file. The extension is not available ...
  18. The %1 thread pool could not be created because its GroupAffinity configuration setting resulted in no processors being assigned ...
  19. The %1 thread pool now has %2 minimum threads, %3 maximum threads, and a concurrency of %4. Its thread pool affinity mask ...
  20. The %1!s! '%2!s!' could not be created or rebuilt. A compressed index is not supported on table that contains sparse columns ...
  21. The %1!s! '%2!s!' does not have a login associated with it. Create a login and credential for this key to automatically access ...
  22. The %1!s! '%2!s!' is dependent on %3!s!. The database collation cannot be changed if a schema-bound object depends on it. ...
  23. The %1!s! '%2!s!' on table '%3!s!' has %4!s! columns in the key list. The maximum limit for %5!s! key column list is %6!s!. ...
  24. The %1!s! '%2!s!' specified for the clustered index '%3!s!' was used for table '%4!s!' even though %5!s! '%6!s!' is specified ...
  25. The %1!s! agent for Publisher (%2!s!), database (%3!s!), publication (%4!s!) cannnot be found. Create the agent with the ...
  26. The %1!s! count for object "%2!s!", index ID %3!s!, partition ID %4!s!, alloc unit ID %5!s! (type %6!s!) is incorrect. Run ...
  27. The %1!s! database "%2!s!" is changing roles from "%3!s!" to "%4!s!" because the mirroring session or availability group ...
  28. The %1!s! does not exist in the database. It may have been removed or renamed. Use Advanced Editor to refresh the available ...
  29. The %1!s! encountered duplicate reference key values when caching reference data. This error occurs in Full Cache mode only. ...
  30. The %1!s! function resulted in an overflow. The number of dateparts separating two date/time instances is too large. Try ...
  31. The %1!s! has a private key that is protected by a user defined password. That password needs to be provided to enable the ...
  32. The %1!s! has an invalid data type. Columns with data types DT_IMAGE, DT_TEXT and DT_NTEXT cannot be written to raw files. ...
  33. The %1!s! has been out of synchronization with the database column. The latest column has %2!s!. Use advanced editor to refresh ...
  34. The %1!s! has performed the following operations: processed %2!I64u! rows, issued %3!I64u! database commands to the reference ...
  35. The %1!s! has performed the following operations: processed %2!I64u! rows, issued %3!I64u! database commands to the reference ...
  36. The %1!s! is mapped to an external metadata column with the id %2!d!. Input columns should not be mapped to external metadata ...
  37. The %1!s! is read/write and is required to have custom property "%2!s!". Add the property, or make remove the read/write ...
  38. The %1!s! must be read/write to have custom property "%2!s!". The input or output column has the specified custom property, ...
  39. The %1!s! operation failed for availability replica '%2!s!', because the backup priority value is outside the valid range. ...
  40. The %1!s! operation failed for availability replica '%2!s!'. The minimum value for session timeout is %3!s!. Retry the operation ...
  41. The %1!s! operation is not allowed by the current availability-group configuration. This operation would exceed the maximum ...
  42. The %1!s! operation is not allowed by the current availability-group configuration. This operation would exceed the maximum ...
  43. The %1!s! operation is not allowed on availability replica '%2!s!', because automatic failover mode is an invalid configuration ...
  44. The %1!s! operation is not allowed. The operation attempted to change the configuration of availability replica '%2!s!' to ...
  45. The %1!s! option was specified more than once for the table, or for at least one of its partitions if the table is partitioned. ...
  46. The %1!s! parameter(s) have been deprecated from this procedure. The value(s) should now be specified when calling '%2!s!'. ...
  47. The %1!s! parameters have been deprecated and should no longer be used. For more information, see the '%2!s!' documentation. ...
  48. The %1!s! processed %2!u! rows in the cache. The processing time was %3!s! seconds. The cache used %4!I64u! bytes of memory. ...
  49. The %1!s! range that specifies %2!s! %3!s! includes at least one %4!s! that is not available to the current instance. The ...
  50. The %1!s! references an external data type that cannot be mapped to a Data Flow task data type. The Data Flow task data type ...
  51. The %1!s! references column ID %2!d!, but that column is already referenced by %3!s!. Remove one of the two reference to ...
  52. The %1!s! references external data type %2!s!, which cannot be mapped to a SSIS Data Flow Task data type. The SSIS Data Flow ...
  53. The %1!s! statement conflicted with the %2!s! constraint "%3!s!". The conflict occurred in database "%4!s!", table "%5!s!"%6!s!%7!s!%8!s!. ...
  54. The %1!s! that is specified for conversation priority '%2!s!' is not valid. The value must be between 1 and %3!s! characters ...
  55. The %1!s! was found, but it does not support a required Integration Services interface (IDTSRuntimeComponent100). Obtain ...
  56. The %1!s!, "%2!s!", encountered a configuration error during initialization. Object cannot be added to the event session. ...
  57. The %1!s!, "%2!s!", encountered a configuration error during initialization. The customizable attribute %3!s! is used internally ...
  58. The %{attribute/} attribute of the %{dimension/} dimension has zero values. The server cannot design aggregations for this ...
  59. The %{cartfile/} cartridge contains a provider name that is not valid in the mssqlcrt:provider element. Only a single XML ...
  60. The %{collation/} collation of the key column of the %{property/} attribute is either not valid or is not supported by the ...
  61. The %{datasourceid/} data source of the %{partition/} partition does not correspond to an existing data source in the database. ...
  62. The %{defaulthierarchy/} default hierarchy of the %{dimension/} dimension does not correspond to an existing hierarchy in ...
  63. The %{detailproperty/} granularity attribute in the %{detaildimension/} measure group dimension is not valid because it is ...
  64. The %{func/} function expects a column reference expression for argument '%d{arg/}', but a dimension expression was used. ...
  65. The %{func/} function expects a column reference expression for argument '%d{arg/}', but a Forecast Model expression was ...
  66. The %{func/} function expects a column reference expression for argument '%d{arg/}', but a Forecast Model reference expression ...
  67. The %{func/} function expects a column reference expression for argument '%d{arg/}', but a hierarchy expression was used. ...
  68. The %{func/} function expects a column reference expression for argument '%d{arg/}', but a table reference expression was ...
  69. The %{func/} function expects a dimension expression for argument '%d{arg/}', but a column reference expression was used. ...
  70. The %{func/} function expects a dimension expression for the %d{arg/} argument. A Forecast Model reference expression was ...
  71. The %{func/} function expects a hierarchy expression for argument '%d{arg/}', but a column reference expression was used. ...
  72. The %{func/} function expects a hierarchy expression for the %d{arg/} argument. A Forecast Model reference expression was ...
  73. The %{func/} function expects a level expression for the %d{arg/} argument. A Forecast Model reference expression was used. ...
  74. The %{func/} function expects a member expression for the %d{arg/} argument. A Forecast Model reference expression was used. ...
  75. The %{func/} function expects a member or set of a single hierarchy for the %d{arg/} argument. A set of multiple hierarchies ...