SQL Server 2008

  1. The query cannot be executed because some files are either missing or not registered. Run setup again to make sure the required ...
  2. The query contains a grouping based on the expression "{0}" which returns a large value type. Expressions which return large ...
  3. The query contains secure information '{0}' or '{1}'. It may create security threat to the product. Do you want to continue? ...
  4. The query could not be generated because the same column (TableId='%{table/}', ColumnId='%{column/}') is being ordered more ...
  5. The query designer could not be loaded. Verify your connection string and query string or enter a valid query to continue. ...
  6. The query has been canceled because the estimated cost of this query (%1!s!) exceeds the configured threshold of %2!s!. Contact ...
  7. The query has exceeded the maximum number of result sets that can be displayed in the results grid. Only the first {0} result ...
  8. The query must have at least one axis. The first axis of the query should not have multiple hierarchies, nor should it reference ...
  9. The query processor could not produce a query plan because a USE PLAN hint was used for a query that modifies data while ...
  10. The query processor could not produce a query plan because a worktable is required, and its minimum row size exceeds the ...
  11. The query processor could not produce a query plan because a worktable is required, and its minimum row size exceeds the ...
  12. The query processor could not produce a query plan because distributed query does not support materializing intermediate ...
  13. The query processor could not produce a query plan because there is a subquery in the predicate of the full outer join. This ...
  14. The query processor could not produce a query plan for a query with a spatial index hint. Reason: %1!s!. Try removing the ...
  15. The query processor is unable to produce a plan for the table or view '%1!s!' because the table resides in a filegroup which ...
  16. The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected ...
  17. The query results are still being transmitted from the server to your computer. This operation might take a long time due ...
  18. The query results cannot be displayed because they require more display memory than SQL Server Management Studio allows. ...
  19. The query uses an aggregate function on a large value type expression. Large value type expressions can not be aggregated. ...
  20. The query uses non-ANSI outer join operators ("*=" or "=*"). To run this query without modification, please set the compatibility ...
  21. The queue '%1!s!' has been enabled for activation, but the MAX_QUEUE_READERS is zero. No procedures will be activated. Consider ...
  22. The queue for this subscription with queue_id = '%1!s!' is not empty. Run the Queue Reader Agent to make sure the queue is ...
  23. The Queue Reader Agent has encountered the error '%3' when connecting to '%2' on '%1'. Ensure that the publication and subscription ...
  24. The Queue Reader Agent was started with an invalid parameter (%1). Restart the agent using only the supported parameters. ...
  25. The Queue Reader Agent was unable to find any active queued updating subscriptions. Ensure that queued updating subscriptions ...
  26. The range for the counters in the registry does not match the expected range of the counters for the instance. Please reload ...
  27. The RangeMax function returns either the upper bound of a continuous column or the specified bucket of a discretized column. ...
  28. The RangeMid function returns either the midpoint of a continuous column or the specified bucket of a discretized column. ...
  29. The RangeMin function returns either the lower bound of a continuous column or the specified bucket of a discretized column. ...
  30. The RANU instance is terminating in response to its internal time out. This is an informational message only. No user action ...
  31. The raw adapter attempted to read %1!d! bytes in the input file for column "%2!s!" with lineage ID %3!d!, but there was an ...
  32. The raw adapter attempted to skip %1!d! bytes in the input file for unreferenced column "%2!s!" with lineage ID %3!d!, but ...
  33. The raw certificate data cannot be obtained from the supplied certificate object (error: %1!s!). This occurs when CPackage::put_CertificateObject ...
  34. The raw source adapter opened a file, but the file contains no columns. The adapter will not produce data. This could indicate ...
  35. The read operation for the notification polling process against the '%{datasource/}' data source failed, because the result ...
  36. The READPAST lock hint is only allowed on target tables of UPDATE and DELETE and on tables specified in an explicit FROM ...
  37. The Rebuild Index task reorganizes data on the data and index pages by rebuilding indexes. This improves performance of index ...
  38. The Rebuild task reorganizes data on the data and index pages by rebuilding indexes. This improves performance of index scans ...
  39. The reconciler process was stopped because the Subscriber that initiated the synchronization is no longer connected. If this ...
  40. The record was skipped because a null attribute key was encountered. Attribute: %{Property/} of Dimension: %{Dimension/} ...
  41. The record was skipped because the attribute key is a duplicate. Attribute: %{Property/} of Dimension: %{Dimension/} from ...
  42. The record was skipped because the attribute key was not found. Attribute: %{Property/} of Dimension: %{Dimension/} from ...
  43. The recovery model cannot be changed to SIMPLE when any files are subject to a RESTORE PAGE operation. Complete the restore ...
  44. The reference column "%1!s!" may be a SQL timestamp column. When the fuzzy match index is built, and a copy of the reference ...
  45. The reference parameter given to XMLDT method '%1!s!' was generated from a different XML instance than the one it is being ...
  46. The reference table '%1!s!' contains a non-integer type identity column which is not supported. Use a view of the table without ...
  47. The reference table '%1!s!' does not have a clustered index on an integer identity column, which is required if the property ...
  48. The reference table name "%1!s!" is not a valid SQL identifier. This error occurs if the table name cannot be parsed from ...
  49. The reference table specified has too many rows. Fuzzy Lookup only works with reference tables having less than 1 billion ...
  50. The reference to column "%1!s!" is not allowed in the argument of the TOP clause. Only references to columns at an outer ...
  51. The referenced report model file has an embedded DataSourceView, but {0} already exists. Are you sure you want to overwrite ...
  52. The referenced table does not exist or has not been created by SQL Server Profiler. Only tables created by SQL Profiler can ...
  53. The refresh of Oracle publisher '%1!s!' by sp_refresh_heterogeneous_publisher was not successful. The Oracle publisher meta ...
  54. The registry key '{0}' is missing so the SQL Support files cannot run properly. To resolve this problem reinstall SQL Support. ...
  55. The registry settings for SNI protocol configuration are incorrect. The server cannot accept connection requests. Error: ...
  56. The registry value '{0}' is missing so the SQL Support files cannot run properly. To resolve this problem reinstall SQL Support. ...
  57. The regular snapshot for this publication has become obsolete or expired. The regular snapshot needs to be regenerated before ...
  58. The related table, {0}, was not included in the new dimension as a lookup table because it contains either a self-join or ...
  59. The RelatedRoleID property for the {0} is a self-reference. The RelatedRoleID property of a Role must refer to a Role other ...
  60. The RelatedRoleID property for the {0} refers to the {2}, but the RelatedRoleID for "{3}" does not refer to "{1}". The RelatedRoleID ...
  61. The Relation property of the {0} references the {1} end of the {2}. This property must reference a Relation end that refers ...
  62. The Relation property of the {0} references the {2} end of the {3}, but the Relation property of the RelatedRole "{1}" also ...
  63. The Relation property of the {0} references the {2}, but the Relation property of the RelatedRole "{1}" references the {3}. ...
  64. The Relation property of the {0} refers to the {1} end of the {2}, which is not bound to a set of uniquely constrained columns ...
  65. The relationship has been identified as damaged. You can try to edit it, but editing might fail. The safest way to fix the ...
  66. The relationship is currently between a primary key column and a non-primary key column. If this is incorrect, click Reverse. ...
  67. The remote copy of database "%1!s!" cannot be opened. Check the database name and ensure that it is in the restoring state, ...
  68. The remote copy of database "%1!s!" has not been rolled forward to a point in time that is encompassed in the local copy ...
  69. The remote copy of database "%1!s!" has not had enough log backups applied to roll forward all of its files to a common point ...
  70. The remote server "%1!s!" does not exist, or has not been designated as a valid Publisher, or you may not have permission ...
  71. The remote server '%1!s!' is not defined as a subscription server. Ensure you specify the server name rather than a network ...
  72. The remote server cannot be accessed. Either the server is not running, you do not have sufficient permissions to access ...
  73. The remote server cannot be accessed. Either the server is not running, you do not have sufficient permissions to access ...
  74. The remote server cannot be accessed. This may be because the server is not running, you do not have sufficient permissions ...
  75. The remote service has sent a message body of type '%1!s!' that does not match the message body encoding format. This occurred ...