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