SQL Server 2016

  1. The ProtectionLevel property of the project has changed. To build the project, the packages need to have the same protection ...
  2. The provided EntitySet name must be qualified by the EntityContainer name, such as 'EntityContainerName.EntitySetName', or ...
  3. The provided IFeatureResultStore instance of type {0} did not supply any outcomes, and so no product feature outcomes can ...
  4. The provided list of key-value pairs contains an incorrect number of entries. There are {1} key fields defined on type '{0}', ...
  5. The provider '{0}' has declared support for more than one version of domain '{1}'. The request cannot resolve to a single ...
  6. The provider instance of type '{0}' used with this method has not been created in the current runtime context and cannot ...
  7. The provider library does not contain a required feature for the database configuration. Upgrade the provider library or ...
  8. The provider used by the '%{datasource_name/}' data source referenced in the OPENQUERY clause cannot be used by this instance. ...
  9. The provider {0} is attached to a domain and cannot be deleted. Please detach the provider from all domains before deleting. ...
  10. The publication "%1!s!" cannot allow multiple subscriptions per partition if it contains articles using @partition_options ...
  11. The publication '%1!s!' could not be added because non-SQL Server Publishers only support the @sync_method parameter values ...
  12. The publication '%1' contains logical record relationships. Logical records are not supported when using Web synchronization ...
  13. The publication '{0}' contains filtered articles and can not be configured via the Peer-To-Peer Topology wizard. This type ...
  14. The publication cannot use precomputed partitions because there is at least one circular reference in the join filters specified ...
  15. The publication does not support stand-alone Distribution Agents and cannot accept subscriptions created using Active X controls. ...
  16. The publication does not support this type of subscribers. Only publications in character bcp mode support heterogeneous ...
  17. The publication must support Subscriber-requested partitioned snapshot generation because one or more articles use subscription-based ...
  18. The publication property '%1!s!' cannot be modified because the peer-to-peer publication '%2!s!' is not enabled for conflict ...
  19. The publication uses parameterized filtering which has been configured to have only one subscriber per partition. Another ...
  20. The published object {0} ({1}) is dependent on the unpublished object {2} ({3}), creation of the published object at the ...
  21. The publisher '%1!s!' uses distribution database '%2!s!' and not '%3!s!' which is required in order to host the publishing ...
  22. The publisher '%1!s!' with distributor '%2!s!' is not known as a publisher at distributor '%3!s!'. Run sp_adddistpublisher ...
  23. The Publisher and Subscribers can update the published data independently after the Subscribers receive an initial snapshot ...
  24. The Publisher cannot be assigned a new range of identity values, because the values for the identity column's data type have ...
  25. The Publisher failed to allocate a new set of identity ranges for the subscription. This can occur when a Publisher or a ...
  26. The publisher login must be a member of the 'db_owner' role at the publisher database when generating a regular snapshot. ...
  27. The publisher login of the snapshot agent must be granted permission to create databases in order to generate a replication ...
  28. The Publisher must use this password when it automatically connects to the Distributor to perform replication administrative ...
  29. The publisher name of the contacted Oracle instance does not match the configured name for the publisher at this distributor. ...
  30. The Publisher or Distributor is not configured properly for replication, or you do not have permission to retrieve information ...
  31. The Publisher to which you connected, '{0}', is a database mirroring partner of the original Publisher, '{1}'. The subscription ...
  32. The Publisher was dropped at the Distributor, but information on the Publisher '%1!s!' was not dropped. Connect to the Oracle ...
  33. The pull subscription to publication '%1' has not been configured correctly. Create an entry for this subscription at the ...
  34. The qualifier cannot be an empty string. If line break suppression is required, the qualifier cannot contain the newline ...
  35. The qualifier has not been set on this instance of the connection manager. Setting the qualifier is required to complete ...
  36. The query against the '%{Name/}' model cannot be performed because this edition of Analysis Services does not support predictions ...
  37. The query at the redirected publisher '%1!s!' to determine the health of the availability group associated with publisher ...
  38. The query at the redirected publisher '%1!s!' to determine whether the publisher database '%2!s!' belonged to an availability ...
  39. The query at the redirected publisher '%1!s!' to determine whether the SQL Server instance is a replication publisher failed ...
  40. The query at the redirected publisher '%1!s!' to determine whether there were sysserver entries for the subscribers of the ...
  41. The query cannot be executed because some files are either missing or not registered. Run setup again to make sure the required ...
  42. The query contains a grouping based on the expression "{0}" which returns a large value type. Expressions which return large ...
  43. The query contains secure information '{0}' or '{1}'. It may create security threat to the product. Do you want to continue? ...
  44. The query could not be generated because the same column (TableId='%{table/}', ColumnId='%{column/}') is being ordered more ...
  45. The query definition projects one or more expressions with duplicate aliases. Ensure that all projected expressions specify ...
  46. The query designer could not be loaded. Verify your connection string and query string or enter a valid query to continue. ...
  47. The query encountered a data consistency issue that prevents further execution. This issue could have been caused by use ...
  48. The query encountered security filters on a table relationship that cannot be reconciled for the current user. Please contact ...
  49. The query exceeded the maximum memory allowed for queries executed in the current workload group (Requested %d{MemoryUsed/}KB, ...
  50. The query for this visualization was canceled. Click the Refresh button in the ribbon to retry the query or Undo to revert ...
  51. The query has been canceled because the estimated cost of this query (%1!s!) exceeds the configured threshold of %2!s!. Contact ...
  52. The query has encountered a design where a many-to-many, reference dimension or measure expression have a circular relationship ...
  53. The query has exceeded the maximum number of result sets that can be displayed in the results grid. Only the first {0} result ...
  54. The query memory grant detected "{0}", which may impact the reliability. Grant size: Initial {1} KB, Final {2} KB, Used {3} ...
  55. The Query Mode deployment property is not valid. When a model is in DirectQuery mode, the Query Mode property cannot be set ...
  56. The Query Mode deployment property is not valid. When a model is not in DirectQuery mode, the Query Mode property must be ...
  57. The query mode on a partition must be one of the following: Import, DirectQuery, or Default. Partition '%{partition/}' in ...
  58. The query must have at least one axis. The first axis of the query should not have multiple hierarchies, nor should it reference ...
  59. The query processor could not produce a query plan because a USE PLAN hint was used for a query that modifies data while ...
  60. The query processor could not produce a query plan because a worktable is required, and its minimum row size exceeds the ...
  61. The query processor could not produce a query plan because a worktable is required, and its minimum row size exceeds the ...
  62. The query processor could not produce a query plan because CURSOR fetch queries cannot reference external tables. Ensure ...
  63. The query processor could not produce a query plan because distributed query does not support materializing intermediate ...
  64. The query processor could not produce a query plan because FORCESEEK or FORCESCAN hints on table or view '%1!s!' cannot be ...
  65. The query processor could not produce a query plan because the FORCESEEK hint on table or view '%1!s!' cannot be used with ...
  66. The query processor could not produce a query plan because the FORCESEEK hint on table or view '%1!s!' cannot be used with ...
  67. The query processor could not produce a query plan because the FORCESEEK hint on table or view '%1!s!' specified more seek ...
  68. The query processor could not produce a query plan because the FORCESEEK hint on view '%1!s!' is used without a NOEXPAND ...
  69. The query processor could not produce a query plan because the name '%1!s!' in the FORCESEEK hint on table or view '%2!s!' ...
  70. The query processor could not produce a query plan because there is a subquery in the predicate of the full outer join. This ...
  71. The query processor could not produce a query plan for a query with a spatial index hint. Reason: %1!s!. Try removing the ...
  72. The query processor is unable to produce a plan for the table or view '%1!s!' because the table resides in a filegroup that ...
  73. The query processor is unable to produce a plan. The table '%1!s!' is unavailable because the heap is corrupted. Take the ...
  74. The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected ...
  75. The query referenced a relationship between '%{FKTable/}'[%{FKColumn/} and '%{PKTable/}'[%{PKColumn/}], which depends on ...