SQL Server 2016

  1. The snapshot agent encountered a critical error when it tried to determine whether there are any unsynchronized subscriptions. ...
  2. The snapshot agent failed to create snapshot folder under the alternate snapshot folder '{0}' configured for the publication ...
  3. The snapshot agent failed to create snapshot folder under the working directory '{0}' configured for the Publisher '{1}', ...
  4. The Snapshot Agent failed to determine how much data to include in the initial snapshot. A failure may have occurred in an ...
  5. The Snapshot Agent failed to determine the partition to which a parameterized snapshot belongs. Verify that the correct parameterized ...
  6. The snapshot agent had retrieved an invalid synchronization method value of '{0}' for the publication '{1}', reconfigure ...
  7. The snapshot compression option can be enabled only for a publication having an alternate snapshot generation folder defined. ...
  8. The snapshot could not be generated because a required application lock could not be obtained. This lock is needed to ensure ...
  9. The snapshot folder '{0}' retrieved from the Publisher's sysmergeschemachange table does not appear to be a snapshot folder ...
  10. The snapshot for this publication has become obsolete. The snapshot agent needs to be run again before the subscription can ...
  11. The SOAP endpoint can be in either a started, stopped or disabled state. Returns TRUE if at least one SOAP endpoint is responding ...
  12. The SOAP headers on the request have exceeded the size limits established for this endpoint. The endpoint owner may increase ...
  13. The SOAPAction value is not valid. The expected format is "SOAPAction=method-uri#method-name" or "SOAPAction=method-uri/method-name". ...
  14. The sort expressions for the {2} {3}' of the {0} {1}' are different from the group expressions. In area charts with scalar ...
  15. The sort failed due to a stack overflow while sorting an incoming buffer. Please reduce the DefaultBufferMaxRows property ...
  16. The sort key position or comparison flag values for the "%1!s!" column in the appended data do not match the corresponding ...
  17. The sort operation exceeded the buffer limit. The stored procedure execution was aborted. Consult SQL Server Books Online ...
  18. The sort string for type concept "{0}" in type "{1}" is invalid or contains references to non-existent identifier parts or ...
  19. The Sort transformation cannot create an event to communicate with its worker threads. Not enough system handles are available ...
  20. The SortDescriptions added are not valid. The probable solutions are to set the CanUserSort on the Column to false, or to ...
  21. The sorting applied to the {2} of the {0} {1}' is different from the grouping expression. Since the chart type is a line ...
  22. The source attribute for the classified '%{structureCol/}' OLAP mining structure column is not part of a natural hierarchy ...
  23. The source attribute of a non-key OLAP mining structure column must be related to the source attribute of the key column ...
  24. The source connection "%1!s!" must specify a SQL Server instance with a version earlier than or the same as the destination ...
  25. The source database '%1!s!'.'%2!s!' cannot have higher performance level than the target database '%3!s!'.'%4!s!'. Upgrade ...
  26. The source database collation ({0}) does not match the target database collation ({1}). This mismatch can cause errors when ...
  27. The source database you have selected contains no visible tables or views. Please go back to the Choose a Data Source page ...
  28. The source file is not valid. The source file is returning a count of more than 131,072 columns. This usually occurs when ...
  29. The source for the binary attribute contains value that is larger than the maximum size specified in the DataSize property ...
  30. The source installation package for the product 2 is out of sync with the client package. Try the installation again using ...
  31. The source lineage id '%1!d!' specified for property '%2!s!' on output column '%3!s!' was not found in the input column collection. ...
  32. The source object %1!s!].[%2!s! on the non-SQL Server Publisher was either not found or is not supported. If the object exists, ...
  33. The source of the Binary data type column is larger than the size that was specified in the DataSize property when the column ...
  34. The source of the Binary data type column is larger than the size that was specified in the DataSize property when the column ...
  35. The source or the destination component contains multiple inputs or outputs. Select an input and an output to connect the ...
  36. The source partition '%{SourcePartitionName/}' from table '%{SourceTableName/}' must be in the same table as the target partition: ...
  37. The source project has failed validation. Click Previous to select another Integration Services project or click Cancel to ...
  38. The source query for this EntityCollection or EntityReference cannot be returned when the related object is in either an ...
  39. The source table '%1!s!' specified in the SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE or SEMANTICSIMILARITYDETAILSTABLE ...
  40. The source Windows domain login {0} cannot be transferred across domains as {1} using the attach method since the database ...
  41. The source Windows local login {0} cannot be transferred across instances as {1} using the attach method since the database ...
  42. The source Windows local login {0} cannot be transferred across machines as {1} using the attach method since the database ...
  43. The spatial data for layer '{2}' in the {0} '{1}' is not valid. Specify spatial data that is data type SqlGeometry or SqlGeography. ...
  44. The spatial data in the specified map layer does not have any non-spatial data field that can be joined with analytical data. ...
  45. The spatial index '{0}.{1}.{2}' will not be scripted for article '{3}' because it references the unpublished column '{4}'. ...
  46. The spatial index '{0}.{1}.{2}' will not be scripted for article '{3}' because the primary key of the base table will not ...
  47. The spatial index '{0}.{1}.{2}' will not be scripted for article '{3}' because the primary key of the base table will only ...
  48. The spatial index '{0}.{1}.{2}' will not be scripted for article '{3}' because the spatial type columns of the base table ...
  49. The spatial index, XML index or indexed view '%1!s!' (object ID %2!s!) contains rows that were not produced by the view definition. ...
  50. The spatial index, XML index or indexed view '%1!s!' (object ID %2!s!) does not contain all rows that the view definition ...
  51. The spatial reference identifier (SRID) is not valid. The specified SRID must match one of the supported SRIDs displayed ...
  52. The specified '%1!s!' cannot use commas (,) to separate addresses: '%2!s!'. To continue, use semicolons (;) to separate addresses. ...
  53. The specified @job_type, %1!s!, is not supported. The value specified for the parameter @job_type must be N'capture' to indicate ...
  54. The specified account '{0}' for setting '{1}' is not a user account. Group or other identities cannot be used for the service ...
  55. The specified account for {0} service is not allowed because you have chosen to either install this instance as part of a ...
  56. The specified account for {0} service is not the same as the account specified for the active node in this SQL Server Failover ...
  57. The specified algorithm cannot handle columns of the mining model, '%{modelname/}', with content of type 'Probability'. Column=%{ColumnName/}]. ...
  58. The specified algorithm cannot handle columns of the mining model, '%{modelname/}', with content of type 'ProbabilityStddev'. ...
  59. The specified algorithm cannot handle columns of the mining model, '%{modelname/}', with content of type 'ProbabilityVariance'. ...
  60. The specified algorithm cannot handle columns of the mining model, '%{modelname/}', with content of type 'Stddev'. Column=%{ColumnName/}]. ...
  61. The specified algorithm cannot handle columns of the mining model, '%{modelname/}', with content of type 'Support'. Column=%{ColumnName/}]. ...
  62. The specified algorithm cannot handle columns of the mining model, '%{modelname/}', with content of type 'Variance'. Column=%{ColumnName/}]. ...
  63. The specified breakpoint ID already exists. This error occurs when a task calls CreateBreakpoint with the same ID multiple ...
  64. The specified ciphertext's encryption algorithm version '%1!s!' does not match the expected encryption algorithm version ...
  65. The specified clustered upgrade is not currently supported. This cluster upgrade will be supported by the final release of ...
  66. The specified column set value causes the estimated row size to be at least %1!s! bytes. This exceeds the maximum allowed ...
  67. The specified command is invalid because the Always On Availability Groups %1!s! feature is not supported by this edition ...
  68. The specified COMPRESSION_DELAY option value %1!s! is invalid. The valid range for disk-based table is between (0, 10080) ...
  69. The specified COMPRESSION_DELAY option value '{0}' is invalid. The valid range for disk-based table is between ({1}, {2}) ...
  70. The specified COMPRESSION_DELAY option value {0} is invalid. The valid range for disk-based table is AUTO or between (0, ...
  71. The specified computer name is either an empty string or is longer than %1!s! Unicode characters. Reenter the command specifying ...
  72. The specified connection "%1!s!" is either not valid, or points to an invalid object. To continue, specify a valid connection. ...
  73. The specified connection string is not valid. Do you want to reset the connection string? If you click OK, the existing connection ...
  74. The specified connection string uses SQL Server Authentication. The FILESTREAM Provider requires Windows Authentication (Integrated ...
  75. The specified credentials for the SQL Server service are not valid. To continue, provide a valid account and password for ...