SQL Server 2012

  1. Terminating immediate updating or queued updating DELETE trigger because it is not the first trigger to fire. Use sp_settriggerorder ...
  2. Terminating immediate updating or queued updating INSERT trigger because it is not the first trigger to fire. Use sp_settriggerorder ...
  3. Terminating immediate updating or queued updating UPDATE trigger because it is not the first trigger to fire. Use sp_settriggerorder ...
  4. Test Case Execution screen Click Start to initiate test case execution. Progress indicators on this screen will display the ...
  5. Testing the registered server failed. Verify the server name, login credentials, and database, and then click Test again. ...
  6. Text File associated with the connection is not found. You can edit the connection to choose a new file to continue importing. ...
  7. Text, image, or ntext column was too large to send to the remote data source due to the storage interface used by the provider. ...
  8. Thank you for participating in our product improvement process. Microsoft treats all customer data as confidential and anonymous ...
  9. that modify what feature usage data is collected. Such updates may be automatically downloaded and installed on your machine ...
  10. The "%1!s!" cannot have a ComparisonFlags property set to non-zero because its SortKeyPosition is set to zero. An output ...
  11. The "%1!s!" cannot have a SortKeyPosition property set to non-zero because "%2!s!" is not a source output. The output column ...
  12. The "%1!s!" cannot have its IsSorted property set to TRUE because it is not a source output. A source output has a SynchronousInputID ...
  13. The "%1!s!" collection cannot be modified during package validation or execution. "%2!s!" cannot be added to the collection. ...
  14. The "%1!s!" custom property for "%2!s!" cannot be set to true. The column data type must be one of the following: DT_I1, ...
  15. The "%1!s!" failed because error code 2!8.8X! occurred, and the error row disposition on "%3!s!" at "%4!s!" specifies failure ...
  16. The "%1!s!" failed because truncation occurred, and the truncation row disposition on "%2!s!" at "%3!s!" specifies failure ...
  17. The "%1!s!" failed because truncation occurred, and the truncation row disposition on "%2!s!" specifies failure on truncation. ...
  18. The "%1!s!" has a value set for length, precision, scale, or code page that is a value other than zero, but the data type ...
  19. The "%1!s!" has IsSorted set to TRUE, but the SortKeyPosition on all output columns are zero. Either change the IsSorted ...
  20. The "%1!s!" has the ExpectBOM property set to TRUE for %2!s!, but the column is not NT_NTEXT. The ExpectBOM specifies that ...
  21. The "%1!s!" has the HasSideEffects property set to TRUE, but "%1!s!" is synchronous and cannot have side effects. Set the ...
  22. The "%1!s!" in the connection manager collection, Connections, of "%2!s!" does not have a value for the ID property. Verify ...
  23. The "%1!s!" is unable to make the column with lineage ID %2!d! read/write because that usage type is not allowed on this ...
  24. The "%1!s!" node cannot be found in custom default persistence. This error occurs if the default saved XML of an extensible ...
  25. The "%1!s!" on "%2!s!" has usage type READONLY, but is not referenced by an expression. Remove the column from the list of ...
  26. 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 ...
  27. The "%1!s!" references column ID %2!d!, and that column is not found on the input. A reference points to a nonexistent column. ...
  28. The "%1!s!" was unable to make the requested change to the input column with lineage ID %2!d!. The request failed with error ...
  29. The "%1!s!" XML element (in the "%2!s!" namespace) in the "%3!s!" element (in the "%4!s!" namespace) of the SOAP request ...
  30. The "%1!s!" XML element (in the "%2!s!" namespace) was expected in the "%3!s!" element (in the "%4!s!" namespace) of the ...
  31. 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 ...
  32. The "%3!s!" property is required on input column "%1!s!" (%2!d!), but is not found. The missing property should be added. ...
  33. The "context" argument for the CHANGE_TRACKING_CONTEXT WITH clause must be of type varbinary data type with a maximum length ...
  34. The "date part" parameter specified for a date function is not valid. "Date part" parameters must be static strings, and ...
  35. The "LogID" variable was not found in the scope of component: %s, logging at the collection set level. Original message: ...
  36. The "SSPROP_COL_UDT_NAME" property was not set for column %1!Iu!. This property must be set for user-defined types. InMemory ...
  37. The "table" or "DBTYPE_TABLE" type specified for column %1!Iu! is only supported as type of a command parameter. InMemory ...
  38. The "{0}" account validation failed. This can be because of any of the following reasons: remote server is down, incorrect ...
  39. The %1 extension failed to read its configuration settings from the %2 configuration file. The extension is not available ...
  40. The %1 extension failed to read its configuration settings from the %2 configuration file. The extension is not available ...
  41. The %1 thread pool could not be created because its GroupAffinity configuration setting resulted in no processors being assigned ...
  42. The %1 thread pool now has %2 minimum threads, %3 maximum threads, and a concurrency of %4. Its thread pool affinity mask ...
  43. The %1!s! '%2!s!' could not be created or rebuilt. A compressed index is not supported on table that contains sparse columns ...
  44. The %1!s! '%2!s!' does not have a login associated with it. Create a login and credential for this key to automatically access ...
  45. The %1!s! '%2!s!' is dependent on %3!s!. The database collation cannot be changed if a schema-bound object depends on it. ...
  46. 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!. ...
  47. 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 ...
  48. The %1!s! agent for Publisher (%2!s!), database (%3!s!), publication (%4!s!) cannnot be found. Create the agent with the ...
  49. 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 ...
  50. The %1!s! database "%2!s!" is changing roles from "%3!s!" to "%4!s!" because the mirroring session or availability group ...
  51. The %1!s! does not exist in the database. It may have been removed or renamed. Use Advanced Editor to refresh the available ...
  52. The %1!s! encountered duplicate reference key values when caching reference data. This error occurs in Full Cache mode only. ...
  53. The %1!s! has a private key that is protected by a user defined password. That password needs to be provided to enable the ...
  54. 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. ...
  55. The %1!s! has been out of synchronization with the database column. The latest column has %2!s!. Use advanced editor to refresh ...
  56. The %1!s! has performed the following operations: processed %2!I64u! rows, issued %3!I64u! database commands to the reference ...
  57. The %1!s! has performed the following operations: processed %2!I64u! rows, issued %3!I64u! database commands to the reference ...
  58. The %1!s! is mapped to an external metadata column with the id %2!d!. Input columns should not be mapped to external metadata ...
  59. The %1!s! is read/write and is required to have custom property "%2!s!". Add the property, or make remove the read/write ...
  60. The %1!s! must be read/write to have custom property "%2!s!". The input or output column has the specified custom property, ...
  61. The %1!s! operation failed for availability replica '%2!s!', because the backup priority value is outside the valid range. ...
  62. The %1!s! operation failed for availability replica '%2!s!'. The minimum value for session timeout is %3!s!. Retry the operation ...
  63. The %1!s! operation is not allowed by the current availability-group configuration. This operation would exceed the maximum ...
  64. The %1!s! operation is not allowed by the current availability-group configuration. This operation would exceed the maximum ...
  65. The %1!s! operation is not allowed on availability replica '%2!s!', because automatic failover mode is an invalid configuration ...
  66. The %1!s! operation is not allowed. The operation attempted to change the configuration of availability replica '%2!s!' to ...
  67. The %1!s! parameter(s) have been deprecated from this procedure. The value(s) should now be specified when calling '%2!s!'. ...
  68. The %1!s! parameters have been deprecated and should no longer be used. For more information, see the '%2!s!' documentation. ...
  69. 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. ...
  70. 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 ...
  71. The %1!s! range that specifies %2!s! %3!s! to %4!s! includes at least one %5!s! that is not available to the current instance. ...
  72. 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 ...
  73. The %1!s! references column ID %2!d!, but that column is already referenced by %3!s!. Remove one of the two reference to ...
  74. 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 ...
  75. 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!. ...