SQL Server 2008 R2

  1. The protection level, ServerStorage, cannot be used when saving to this destination. The system could not verify that the ...
  2. The provider library does not contain a required feature for the database configuration. Upgrade the provider library or ...
  3. The provider used by the '%{datasource_name/}' data source referenced in the OPENQUERY clause cannot be used by this instance. ...
  4. The publication "%1!s!" cannot allow multiple subscriptions per partition if it contains articles using @partition_options ...
  5. The publication '%1!s!' could not be added because non-SQL Server Publishers only support the @sync_method parameter values ...
  6. The publication '%1' contains logical record relationships. Logical records are not supported when using Web synchronization ...
  7. The publication '{0}' contains filtered articles and can not be configured via the Peer-To-Peer Topology wizard. This type ...
  8. The publication cannot use precomputed partitions because there is at least one circular reference in the join filters specified ...
  9. The publication does not support stand-alone Distribution Agents and cannot accept subscriptions created using Active X controls. ...
  10. The publication does not support this type of subscribers. Only publications in character bcp mode support heterogeneous ...
  11. The publication must support Subscriber-requested partitioned snapshot generation because one or more articles use subscription-based ...
  12. The publication property '%1!s!' cannot be modified because the peer-to-peer publication '%2!s!' is not enabled for conflict ...
  13. The publication uses parameterized filtering which has been configured to have only one subscriber per partition. Another ...
  14. The Publish Database Wizard enables you to publish database and objects in a database to remote instances of SQL Server by ...
  15. The published object {0} ({1}) is dependent on the unpublished object {2} ({3}), creation of the published object at the ...
  16. The published stream adapters are not available. This is an indication that the server metadata is corrupted. If the metadata ...
  17. The Publisher and Subscribers can update the published data independently after the Subscribers receive an initial snapshot ...
  18. The Publisher cannot be assigned a new range of identity values, because the values for the identity column's data type have ...
  19. The Publisher failed to allocate a new set of identity ranges for the subscription. This can occur when a Publisher or a ...
  20. The publisher login must be a member of the 'db_owner' role at the publisher database when generating a regular snapshot. ...
  21. The publisher login of the snapshot agent must be granted permission to create databases in order to generate a replication ...
  22. The Publisher must use this password when it automatically connects to the Distributor to perform replication administrative ...
  23. The publisher name of the contacted Oracle instance does not match the configured name for the publisher at this distributor. ...
  24. The Publisher or Distributor is not configured properly for replication, or you do not have permission to retrieve information ...
  25. The Publisher streams transactions to SQL Server Subscribers after they receive an initial snapshot of the published data. ...
  26. The Publisher to which you connected, '{0}', is a database mirroring partner of the original Publisher, '{1}'. The subscription ...
  27. The Publisher was dropped at the Distributor, but information on the Publisher '%1!s!' was not dropped. Connect to the Oracle ...
  28. The pull subscription to publication '%1' has not been configured correctly. Create an entry for this subscription at the ...
  29. The qualifier cannot be an empty string. If line break suppression is required, the qualifier cannot contain the newline ...
  30. The qualifier has not been set on this instance of the connection manager. Setting the qualifier is required to complete ...
  31. The query '{0}' (query template '{1}') is not started and the diagnostic settings of its operators and streams cannot be ...
  32. The query '{0}' (query template '{1}') is not started and the diagnostic settings of its operators and streams cannot be ...
  33. The query '{0}' (query template '{1}') is not started and the diagnostic settings of its operators and streams cannot be ...
  34. The query '{0}' (query template '{1}') is not started and the diagnostic views of its operators and streams cannot be retrieved. ...
  35. The query against the '%{Name/}' model cannot be performed because the Standard Edition of Analysis Services does not support ...
  36. The query application must be specified explicitly because none of query inputs are bound to queries. Use an overload that ...
  37. The query application must be specified explicitly because the query inputs are bound to published streams in different applications. ...
  38. The query cannot be executed because some files are either missing or not registered. Run setup again to make sure the required ...
  39. The query contains a grouping based on the expression "{0}" which returns a large value type. Expressions which return large ...
  40. The query contains secure information '{0}' or '{1}'. It may create security threat to the product. Do you want to continue? ...
  41. The query could not be generated because the same column (TableId='%{table/}', ColumnId='%{column/}') is being ordered more ...
  42. The query designer could not be loaded. Verify your connection string and query string or enter a valid query to continue. ...
  43. The query has been canceled because the estimated cost of this query (%1!s!) exceeds the configured threshold of %2!s!. Contact ...
  44. The query has exceeded the maximum number of result sets that can be displayed in the results grid. Only the first {0} result ...
  45. The query must have at least one axis. The first axis of the query should not have multiple hierarchies, nor should it reference ...
  46. The query processor could not produce a query plan because a USE PLAN hint was used for a query that modifies data while ...
  47. The query processor could not produce a query plan because a worktable is required, and its minimum row size exceeds the ...
  48. The query processor could not produce a query plan because a worktable is required, and its minimum row size exceeds the ...
  49. The query processor could not produce a query plan because distributed query does not support materializing intermediate ...
  50. The query processor could not produce a query plan because there is a subquery in the predicate of the full outer join. This ...
  51. The query processor could not produce a query plan for a query with a spatial index hint. Reason: %1!s!. Try removing the ...
  52. The query processor is unable to produce a plan for the table or view '%1!s!' because the table resides in a filegroup which ...
  53. The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected ...
  54. The query referenced calculated column '%{table/}'[%{column/} which does not hold any data because evaluation of one of the ...
  55. The query referenced calculated column '%{table/}'[%{column/} which does not hold any data because there is an error in its ...
  56. The query referenced column '%{table/}'[%{column/} which depends on another column, relationship or measure that is not in ...
  57. The query referenced column '%{table/}'[%{column/} which does not hold any data because it needs to be recalculated or refreshed. ...
  58. The query requires the generation of a data request involving a slice that consists of an arbitrary-shaped set with tuples ...
  59. The query results are still being transmitted from the server to your computer. This operation might take a long time due ...
  60. The query results cannot be displayed because they require more display memory than SQL Server Management Studio allows. ...
  61. The query uses an aggregate function on a large value type expression. Large value type expressions can not be aggregated. ...
  62. The query uses non-ANSI outer join operators ("*=" or "=*"). To run this query without modification, please set the compatibility ...
  63. The query was edited outside of the visual query designer. Using the visual query designer will discard these changes to ...
  64. The queue '%1!s!' has been enabled for activation, but the MAX_QUEUE_READERS is zero. No procedures will be activated. Consider ...
  65. The queue for this subscription with queue_id = '%1!s!' is not empty. Run the Queue Reader Agent to make sure the queue is ...
  66. The Queue Reader Agent has encountered the error '%3' when connecting to '%2' on '%1'. Ensure that the publication and subscription ...
  67. The Queue Reader Agent was started with an invalid parameter (%1). Restart the agent using only the supported parameters. ...
  68. The Queue Reader Agent was unable to find any active queued updating subscriptions. Ensure that queued updating subscriptions ...
  69. The range for the counters in the registry does not match the expected range of the counters for the instance. Please reload ...
  70. The RangeMax function returns either the upper bound of a continuous column or the specified bucket of a discretized column. ...
  71. The RangeMid function returns either the midpoint of a continuous column or the specified bucket of a discretized column. ...
  72. The RangeMin function returns either the lower bound of a continuous column or the specified bucket of a discretized column. ...
  73. The RANU instance is terminating in response to its internal time out. This is an informational message only. No user action ...
  74. 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 ...
  75. The raw adapter attempted to skip %1!d! bytes in the input file for unreferenced column "%2!s!" with lineage ID %3!d!, but ...