SQL Server 2016
- The ProtectionLevel property of the project has changed. To build the project, the packages need to have the same protection ...
- The provided EntitySet name must be qualified by the EntityContainer name, such as 'EntityContainerName.EntitySetName', or ...
- The provided IFeatureResultStore instance of type {0} did not supply any outcomes, and so no product feature outcomes can ...
- The provided list of key-value pairs contains an incorrect number of entries. There are {1} key fields defined on type '{0}', ...
- The provider '{0}' has declared support for more than one version of domain '{1}'. The request cannot resolve to a single ...
- The provider instance of type '{0}' used with this method has not been created in the current runtime context and cannot ...
- 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 provider {0} is attached to a domain and cannot be deleted. Please detach the provider from all domains before deleting. ...
- 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 published object {0} ({1}) is dependent on the unpublished object {2} ({3}), creation of the published object at the ...
- The publisher '%1!s!' uses distribution database '%2!s!' and not '%3!s!' which is required in order to host the publishing ...
- The publisher '%1!s!' with distributor '%2!s!' is not known as a publisher at distributor '%3!s!'. Run sp_adddistpublisher ...
- 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 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 against the '%{Name/}' model cannot be performed because this edition of Analysis Services does not support predictions ...
- The query at the redirected publisher '%1!s!' to determine the health of the availability group associated with publisher ...
- The query at the redirected publisher '%1!s!' to determine whether the publisher database '%2!s!' belonged to an availability ...
- The query at the redirected publisher '%1!s!' to determine whether the SQL Server instance is a replication publisher failed ...
- The query at the redirected publisher '%1!s!' to determine whether there were sysserver entries for the subscribers of the ...
- 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 definition projects one or more expressions with duplicate aliases. Ensure that all projected expressions specify ...
- The query designer could not be loaded. Verify your connection string and query string or enter a valid query to continue. ...
- The query encountered a data consistency issue that prevents further execution. This issue could have been caused by use ...
- The query encountered security filters on a table relationship that cannot be reconciled for the current user. Please contact ...
- The query exceeded the maximum memory allowed for queries executed in the current workload group (Requested %d{MemoryUsed/}KB, ...
- The query for this visualization was canceled. Click the Refresh button in the ribbon to retry the query or Undo to revert ...
- 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 encountered a design where a many-to-many, reference dimension or measure expression have a circular relationship ...
- 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 memory grant detected "{0}", which may impact the reliability. Grant size: Initial {1} KB, Final {2} KB, Used {3} ...
- The Query Mode deployment property is not valid. When a model is in DirectQuery mode, the Query Mode property cannot be set ...
- The Query Mode deployment property is not valid. When a model is not in DirectQuery mode, the Query Mode property must be ...
- The query mode on a partition must be one of the following: Import, DirectQuery, or Default. Partition '%{partition/}' in ...
- 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 CURSOR fetch queries cannot reference external tables. Ensure ...
- 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 FORCESEEK or FORCESCAN hints on table or view '%1!s!' cannot be ...
- The query processor could not produce a query plan because the FORCESEEK hint on table or view '%1!s!' cannot be used with ...
- The query processor could not produce a query plan because the FORCESEEK hint on table or view '%1!s!' cannot be used with ...
- The query processor could not produce a query plan because the FORCESEEK hint on table or view '%1!s!' specified more seek ...
- The query processor could not produce a query plan because the FORCESEEK hint on view '%1!s!' is used without a NOEXPAND ...
- The query processor could not produce a query plan because the name '%1!s!' in the FORCESEEK hint on table or view '%2!s!' ...
- 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 that ...
- The query processor is unable to produce a plan. The table '%1!s!' is unavailable because the heap is corrupted. Take the ...
- 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 a relationship between '%{FKTable/}'[%{FKColumn/} and '%{PKTable/}'[%{PKColumn/}], which depends on ...