SQL Server 2008

  1. The service {0} cannot be located. Contact your system administrator to verify that the report designer has been correctly ...
  2. The session keys for this conversation could not be created or accessed. The database master key is required for this operation. ...
  3. The session was enlisted in an active user transaction while trying to bind to a new transaction. The session has defected ...
  4. The session with SPID %1!s! was found to be invalid during termination, possibly because of corruption in the session structure. ...
  5. The set of tuning options (-fa, -fp, -fk) that you have supplied is invalid. This combination is not supported for indexed ...
  6. The set of tuning options (-fa, -fp, -fk) that you have supplied is invalid. This combination is not supported for nonclustered ...
  7. The set of tuning options (-fa, -fp, -fk) that you have supplied is invalid. When -fk option is ALIGNED, -fp option must ...
  8. The set of tuning options (-fa, -fp, -fk) that you have supplied is invalid. When -fp option is ALIGNED, -fk option cannot ...
  9. The set of tuning options (-fx, -fk) that you have supplied is invalid. When -fx option is used, -fk option cannot be set ...
  10. The set of tuning options that you have selected is invalid. When Keep Aligned Partitioning is selected, the Aligned Partitioning ...
  11. The set of tuning options that you have selected is not valid. The option Evaluate Utilization of Existing PDS Only cannot ...
  12. The set of tuning options that you have selected is not valid. The options Keep All Existing PDS or Keep Indexes Only or ...
  13. The SetQualifier method cannot be called on a connection manager during package execution. This method is used at design-time ...
  14. The settings for a cached ROLAP object must exactly match those corresponding to Real-Time ROLAP. Uncheck and check the Enable ...
  15. The Setup language is different than the language of existing SQL Server features. To continue, use SQL Server Setup installation ...
  16. The Setup language is different than the language of the SQL Server features you are upgrading. To continue, use SQL Server ...
  17. The Setup Wizard allows you to change the way ProductName features are installed on your computer or to remove it from your ...
  18. The Setup Wizard will complete the installation of ProductName on your computer. Click Install to continue or Cancel to exit ...
  19. The severity level of the '%1!s!' version of this message must be the same as the severity level (%2!s!) of the us_english ...
  20. The shared directory (or command line option {0}) value for a cluster installation cannot be a directory on a shared disk. ...
  21. The Shopping Basket Analysis tool facilitates cross-selling analysis. It can be applied on a table containing transactions. ...
  22. The Show method can be called only once on an ExceptionMessageBox object. To display a new message, you must create a new ...
  23. The Shrink Database task reduces the disk space consumed by the database and log files by removing empty data and log pages. ...
  24. The size of a database is reduced by collectively shrinking the database files, releasing unused space. To shrink individual ...
  25. The size of the database is reduced by shrinking individual files to release unallocated space. To shrink all database files, ...
  26. The size of the file '%1' has exceeded the limit of %2!d! bytes imposed by the compression mechanism, retry the operation ...
  27. The size of the gauge inside the gauge container. The coordinates are measured as a percentage of the container's width and ...
  28. The size of the gauge inside the gauge container. The coordinates are measured as a percentage of the container's width/height. ...
  29. The size of the recovery log record is incorrect. The log may be corrupt. The expected length was {0}, the actual length ...
  30. The size of the state indicator inside the gauge container. The coordinates are measured as a percentage of the container's ...
  31. The skipped levels column of the %{property/} attribute is not valid because either the attribute is not a parent attribute ...
  32. The slot count, %1!s!, exceeds the maximum slot count size of %2!s!. Reduce the slot count value and try your command again. ...
  33. The snapshot agent can only retrieve publisher information if the distributor login is a member of the 'db_owner' role at ...
  34. The snapshot agent could not continue generating a snapshot because SMO\DMO extended procedures were disabled at the SQL ...
  35. The snapshot agent encountered a critical error when it tried to determine whether there are any unsynchronized subscriptions. ...
  36. The snapshot agent failed to create snapshot folder under the alternate snapshot folder '{0}' configured for the publication ...
  37. The snapshot agent failed to create snapshot folder under the working directory '{0}' configured for the Publisher '{1}', ...
  38. The Snapshot Agent failed to determine how much data to include in the initial snapshot. A failure may have occurred in an ...
  39. The Snapshot Agent failed to determine the partition to which a parameterized snapshot belongs. Verify that the correct parameterized ...
  40. The snapshot agent had retrieved an invalid synchronization method value of '{0}' for the publication '{1}', reconfigure ...
  41. The snapshot compression option can be enabled only for a publication having an alternate snapshot generation folder defined. ...
  42. The snapshot could not be generated because a required application lock could not be obtained. This lock is needed to ensure ...
  43. The snapshot folder '{0}' retrieved from the Publisher's sysmergeschemachange table does not appear to be a snapshot folder ...
  44. The snapshot for this publication has become obsolete. The snapshot agent needs to be run again before the subscription can ...
  45. The SOAP endpoint can be in either a started, stopped or disabled state. Returns TRUE if at least one SOAP endpoint is responding ...
  46. The SOAP headers on the request have exceeded the size limits established for this endpoint. The endpoint owner may increase ...
  47. The SOAPAction value is not valid. The expected format is "SOAPAction=method-uri#method-name" or "SOAPAction=method-uri/method-name". ...
  48. The sort expressions for the {2} {3}' of the {0} {1}' are different from the group expressions. In area charts with scalar ...
  49. The sort failed due to a stack overflow while sorting an incoming buffer. Please reduce the DefaultBufferMaxRows property ...
  50. The sort string for type concept "{0}" in type "{1}" is invalid or contains references to non-existent identifier parts or ...
  51. The Sort transformation cannot create an event to communicate with its worker threads. Not enough system handles are available ...
  52. The sorting applied to the {2} of the {0} {1}' is different from the grouping expression. Since the chart type is a line ...
  53. The source attribute for the classified '%{structureCol/}' OLAP mining structure column is not part of a natural hierarchy ...
  54. The source attribute of a non-key OLAP mining structure column must be related to the source attribute of the key column ...
  55. The source connection "%1!s!" must specify a SQL Server instance with a version earlier than or the same as the destination ...
  56. The source database collation ({0}) does not match the target database collation ({1}). This mismatch can cause errors when ...
  57. The source database you have selected contains no visible tables or views. Please go back to the Choose a Data Source page ...
  58. The source file is not valid. The source file is returning a count of more than 131,072 columns. This usually occurs when ...
  59. The source installation package for the product 2 is out of sync with the client package. Try the installation again using ...
  60. The source lineage id '%1!d!' specified for property '%2!s!' on output column '%3!s!' was not found in the input column collection. ...
  61. 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, ...
  62. The source or the destination component contains multiple inputs or outputs. Select an input and an output to connect the ...
  63. The source Windows domain login {0} cannot be transferred across domains as {1} using the attach method since the database ...
  64. The source Windows local login {0} cannot be transferred across instances as {1} using the attach method since the database ...
  65. The source Windows local login {0} cannot be transferred across machines as {1} using the attach method since the database ...
  66. The spatial index '{0}.{1}.{2}' will not be scripted for article '{3}' because it references the unpublished column '{4}'. ...
  67. The spatial index '{0}.{1}.{2}' will not be scripted for article '{3}' because the primary key of the base table will not ...
  68. The spatial index '{0}.{1}.{2}' will not be scripted for article '{3}' because the primary key of the base table will only ...
  69. The spatial index '{0}.{1}.{2}' will not be scripted for article '{3}' because the spatial type columns of the base table ...
  70. The spatial index, XML index or indexed view '%1!s!' (object ID %2!s!) contains rows that were not produced by the view definition. ...
  71. The spatial index, XML index or indexed view '%1!s!' (object ID %2!s!) does not contain all rows that the view definition ...
  72. The spatial reference identifier (SRID) is not valid. The specified SRID must match one of the supported SRIDs displayed ...
  73. The specified @job_type, %1!s!, is not supported. The value specified for the parameter @job_type must be N'capture' to indicate ...
  74. The specified algorithm cannot handle columns of the mining model, %{modelname/}, with content of type 'Probability'. Column=%{ColumnName/}]. ...
  75. The specified algorithm cannot handle columns of the mining model, %{modelname/}, with content of type 'ProbabilityStddev'. ...