SQL Server 2012

  1. The query for this visualization was canceled. Click the Refresh button in the ribbon to retry the query or Undo to revert ...
  2. The query has been canceled because the estimated cost of this query (%1!s!) exceeds the configured threshold of %2!s!. Contact ...
  3. The query has encountered a design where a many-to-many, reference dimension or measure expression have a circular relationship ...
  4. The query has exceeded the maximum number of result sets that can be displayed in the results grid. Only the first {0} result ...
  5. The Query Mode deployment property is not valid. When a model is in DirectQuery mode, the Query Mode property cannot be set ...
  6. The Query Mode deployment property is not valid. When a model is not in DirectQuery mode, the Query Mode property must be ...
  7. The query must have at least one axis. The first axis of the query should not have multiple hierarchies, nor should it reference ...
  8. The query processor could not produce a query plan because a USE PLAN hint was used for a query that modifies data while ...
  9. The query processor could not produce a query plan because a worktable is required, and its minimum row size exceeds the ...
  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 distributed query does not support materializing intermediate ...
  12. The query processor could not produce a query plan because FORCESEEK or FORCESCAN hints on table or view '%1!s!' cannot be ...
  13. The query processor could not produce a query plan because the FORCESEEK hint on table or view '%1!s!' cannot be used with ...
  14. The query processor could not produce a query plan because the FORCESEEK hint on table or view '%1!s!' cannot be used with ...
  15. The query processor could not produce a query plan because the FORCESEEK hint on table or view '%1!s!' specified more seek ...
  16. The query processor could not produce a query plan because the FORCESEEK hint on view '%1!s!' is used without a NOEXPAND ...
  17. The query processor could not produce a query plan because the name '%1!s!' in the FORCESEEK hint on table or view '%2!s!' ...
  18. The query processor could not produce a query plan because there is a subquery in the predicate of the full outer join. This ...
  19. The query processor could not produce a query plan for a query with a spatial index hint. Reason: %1!s!. Try removing the ...
  20. The query processor is unable to produce a plan for the table or view '%1!s!' because the table resides in a filegroup which ...
  21. The query processor is unable to produce a plan. The table '%1!s!' is unavailable because the heap is corrupted. Take the ...
  22. The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected ...
  23. The query referenced a relationship between '%{FKTable/}'[%{FKColumn/} and '%{PKTable/}'[%{PKColumn/}], which depends on ...
  24. The query referenced calculated column '%{table/}'[%{column/} which does not hold any data because evaluation of one of the ...
  25. The query referenced calculated column '%{table/}'[%{column/} which does not hold any data because there is an error in its ...
  26. The query referenced column '%{table/}'[%{column/} which depends on another column, relationship or measure that is not in ...
  27. The query referenced hierarchy '%{table/}'[%{hierarchy/} which depends on a column, relationship, or measure that is not ...
  28. The query referenced hierarchy '%{table/}'[%{hierarchy/} which does not hold any data because it needs to be processed or ...
  29. The query requires the generation of a data request involving a slice that consists of an arbitrary-shaped set with tuples ...
  30. The query results are still being transmitted from the server to your computer. This operation might take a long time due ...
  31. The query results cannot be displayed because they require more display memory than SQL Server Management Studio allows. ...
  32. The query to determine whether the local distributor '%1!s!' is the distributor for remote publisher '%2!s!' failed with ...
  33. The query uses an aggregate function on a large value type expression. Large value type expressions can not be aggregated. ...
  34. The query was edited outside of the visual query designer. Using the visual query designer will discard these changes to ...
  35. The queue %1!s! in database %2!s! has activation enabled and contains unlocked messages but no RECEIVE has been executed ...
  36. The queue '%1!s!' has been enabled for activation, but the MAX_QUEUE_READERS is zero. No procedures will be activated. Consider ...
  37. The queue for this subscription with queue_id = '%1!s!' is not empty. Run the Queue Reader Agent to make sure the queue is ...
  38. The Queue Reader Agent has encountered the error '%3' when connecting to '%2' on '%1'. Ensure that the publication and subscription ...
  39. The Queue Reader Agent was started with an invalid parameter (%1). Restart the agent using only the supported parameters. ...
  40. The Queue Reader Agent was unable to find any active queued updating subscriptions. Ensure that queued updating subscriptions ...
  41. The range for the counters in the registry does not match the expected range of the counters for the instance. Please reload ...
  42. The RangeMax function returns either the upper bound of a continuous column or the specified bucket of a discretized column. ...
  43. The RangeMid function returns either the midpoint of a continuous column or the specified bucket of a discretized column. ...
  44. The RangeMin function returns either the lower bound of a continuous column or the specified bucket of a discretized column. ...
  45. The RANU instance is terminating in response to its internal time out. This is an informational message only. No user action ...
  46. 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 ...
  47. The raw adapter attempted to skip %1!d! bytes in the input file for unreferenced column "%2!s!" with lineage ID %3!d!, but ...
  48. The raw certificate data cannot be obtained from the supplied certificate object (error: %1!s!). This occurs when CPackage::put_CertificateObject ...
  49. The raw source adapter opened a file, but the file contains no columns. The adapter will not produce data. This could indicate ...
  50. The RBS FILESTREAM Provider server-side data cannot be removed because there are existing blobs in the provider. This data ...
  51. The read operation for the notification polling process against the '%{datasource/}' data source failed, because the result ...
  52. The read-only routing operation failed. This is sent when the primary replica has a READ_ONLY_ROUTING_LIST configured and ...
  53. The read-only routing server name returned to the client in the routing response. The server name is determined using the ...
  54. The reader is not in the state to support the current operation. NextResult method has not been invoked or reader has moved ...
  55. The READPAST lock hint is only allowed on target tables of UPDATE and DELETE and on tables specified in an explicit FROM ...
  56. The READ_ONLY_ROUTING_URL '%1!s!' specified for availability replica '%2!s!' is not valid. It does not follow the required ...
  57. The Rebuild Index task reorganizes data on the data and index pages by rebuilding indexes. This improves performance of index ...
  58. The Rebuild task reorganizes data on the data and index pages by rebuilding indexes. This improves performance of index scans ...
  59. The reconciler process was stopped because the Subscriber that initiated the synchronization is no longer connected. If this ...
  60. The record was skipped because a null attribute key was encountered. Attribute: %{Property/} of Dimension: %{Dimension/} ...
  61. The record was skipped because the attribute key is a duplicate. Attribute: %{Property/} of Dimension: %{Dimension/} from ...
  62. The record was skipped because the attribute key was not found. Attribute: %{Property/} of Dimension: %{Dimension/} from ...
  63. The recovery LSN %1!s! was identified for the database with ID %2!s!. This is an informational message only. No user action ...
  64. The recovery model cannot be changed to SIMPLE when any files are subject to a RESTORE PAGE operation. Complete the restore ...
  65. The recovery unit files metadata, sys.database_files, of a database segment is copied from the sys.master_files system table. ...
  66. The Rectangle '{0}' is too complex to export to Word. Please group the ReportItems together into rectangles to simplify. ...
  67. The reference column "%1!s!" may be a SQL timestamp column. When the fuzzy match index is built, and a copy of the reference ...
  68. The reference data configuration was updated by another user, your changes cannot be saved. The configuration data will be ...
  69. The reference parameter given to XMLDT method '%1!s!' was generated from a different XML instance than the one it is being ...
  70. The reference should be specified as null given the specified validate type. Change the validate type to allow for a specified ...
  71. The reference table '%1!s!' contains a non-integer type identity column which is not supported. Use a view of the table without ...
  72. The reference table '%1!s!' does not have a clustered index on an integer identity column, which is required if the property ...
  73. The reference table name "%1!s!" is not a valid SQL identifier. This error occurs if the table name cannot be parsed from ...
  74. The reference table specified has too many rows. Fuzzy Lookup only works with reference tables having less than 1 billion ...
  75. The reference to column "%1!s!" is not allowed in an argument to a TOP, OFFSET, or FETCH clause. Only references to columns ...