SQL Server 2008 R2

  1. The DATA_COMPRESSION option was specified more than once for the table, or for at least one of its partitions if the table ...
  2. The date frequency level is required. If you do not want it to be visible, you can hide this attribute in the dimension editor. ...
  3. The date part parameter specified for function "%1!s!" is not valid. It must be a static string. The date part parameter ...
  4. The date provided is before the start of the Hijri calendar which in Microsoft's 'Kuwaiti Algorithm' is July 15th, 622 C.E. ...
  5. The date/time is converted to the RFC1123 standard format. It follows the custom pattern 'ddd, dd MMMM yyyy HH:mm:ss G\MT'. ...
  6. The date/time is converted to the universal full format. Pattern is always the same regardless of culture or format provider. ...
  7. The date/time is converted to the universal sortable format. Pattern is always the same regardless of culture or format provider. ...
  8. The datediff function resulted in an overflow. The number of dateparts separating two date/time instances is too large. Try ...
  9. The DBCC NEWALLOC, DBCC ROWLOCK, DBCC TEXTALL, and DBCC TEXTALLOC commands were previously announced as deprecated and have ...
  10. The DBMS type or version of "%1!s!" is not supported. A connection to Microsoft SQL Server version 8.0 or later is required. ...
  11. The DDL operation is not supported for article '%1!s!'. If the column in the DDL operation is enabled for FILESTREAM or is ...
  12. The default buffer maximum rows must be larger than %1!d! rows. An attempt was made to set the DefaultBufferMaxRows property ...
  13. The default buffer size must be between %1!d! and %2!d! bytes. An attempt was made to set the DefaultBufferSize property ...
  14. The default constraint '{0}.{1}.{2}' will not be scripted for article '{3}' because it is defined on the unpublished column ...
  15. The default folder may not be accessible by synchronization agents running at the following Subscriber(s): {0}. The folder ...
  16. The default folder may not be accessible by synchronization agents running at the following Subscriber(s): {0}. The folder ...
  17. The Default Measure for the {0} perspective is not valid because it refers to a measure that is not included in the perspective. ...
  18. The default report processing timeout value, in seconds, for all reports managed in the report server namespace. This value ...
  19. The default session (progress report) trace cannot be subscribed to because the connection is not associated with an existing ...
  20. The default sort string for type "{0}" is invalid or contains references to non-existent identifier parts or property names. ...
  21. The default value Expression for the {0} contains one or more of the following: Path, Function, AttributeRef, EntityRef, ...
  22. The default value was attempted to be set for column %1!Iu!. Default values can not be set for InMemory Rowset columns. InMemory ...
  23. The DefaultAggregateAttributeID property for the {0} is specified, but the IsAggregate property is true. A default aggregate ...
  24. The DefaultAggregateAttributeID property for the {0} refers to the {2}, which is not a variation of "{1}". The default aggregate ...
  25. The defaults you have specified will initialize the properties of new articles as they are published. One or more {0} have ...
  26. The DEFAULT_SCHEMA clause cannot be used with a Windows group or with principals mapped to certificates or asymmetric keys. ...
  27. The definition of this report is not valid. In this report, {0} refer to each other in a circular manner. Correct the circular ...
  28. The delegate for assignment expressions must take at least two arguments: an expression evaluation context and an output ...
  29. The delegating allocator does not support reassignment of the base allocator unless all allocated memory is first released. ...
  30. The delete operation cannot be performed because the server has encountered more than one member in a parent-child dimension ...
  31. The delete operation involves more than 20 lines. Are you sure you wish to save the deleted text in the Undo buffer? Responding ...
  32. The delivery extension associated with this subscription is no longer installed in the system. Select a different extension ...
  33. The delivery extension associated with this subscription is not available on this report server. Verify that the delivery ...
  34. The delivery extension settings and report parameter values can use field values returned by the command or query. If there ...
  35. The delivery extension used by this subscription is no longer available on the report server. To continue, choose a new delivery ...
  36. The dependencies reported for entity "%1!s!" do not include references to columns. This is either because the entity references ...
  37. The dependent column "{1}" is contained in the determinant columns. Please remove it from the determinant columns to correct ...
  38. The dependent object '{0}' will not be considered during per-article dependencies analysis because it is of the type '{1}' ...
  39. The deployment server name has not been specified. To set the server name, right click the project name in Solution Explorer, ...
  40. The derived event type does not match the expected event type of the external stream {0} in the referenced query template. ...
  41. The derived hierarchy level cannot be saved. A level cannot be added on top of a recursive level while anchoring is turned ...
  42. The derived hierarchy level cannot be saved. An explicit hierarchy level is not supported in a recursive derived hierarchy. ...
  43. The derived hierarchy was not deleted because a subscription view exists. To delete the hierarchy, you must first delete ...
  44. The designer cannot display calculations because there are one or more syntax errors in the MDX script. To display these ...
  45. The designer window cannot be closed while a package is running. Stop the debugger before attempting to close the window. ...
  46. The destination object in a property mapping has no parent. The destination object is not a child of any sequence container. ...
  47. The destination table of the newly created relationship has no primary key defined. Would you like to define a logical primary ...
  48. The DESX keyword is now deprecated and will be removed in a future version of SQL Server. Avoid using it in new development ...
  49. The detail dimension with ID of '%{dimensionid/}', Name of '%{dimensionname/}' referenced by the '%{detail/}' measure group ...
  50. The Detect Categories tool automatically detects the rows in a table that share similar properties, then groups them into ...
  51. The device information is invalid because the closing tag for the element '{0}' was expected but not found (rrExpectedEndElement). ...
  52. The device information is invalid because the opening tag for a parameter was expected but not found (rrParameterExpected). ...
  53. The diagnostic provider is not registered.NoSuitableSchedulingPolicy = No suitable scheduling policy was found for the given ...
  54. The diagram cannot be opened because the current owner of the diagram no longer exists. Do you want to take over ownership ...
  55. The diagram cannot be opened because the current owner of the diagram no longer exists. Do you want to take over ownership ...
  56. The dialog lifetime value of %1!s! is outside the allowable range of %2!s! to %3!s!. Specify a valid dialog lifetime value. ...
  57. The dialog will backup metadata for ROLAP partitions, metadata and aggregations for HOLAP partitions, metadata, source data ...
  58. The dialog {0}:{1} could not create the target endpoint because the EXECUTE AS failed for user {2} with the following error: ...
  59. The differential backup is not allowed because it would be based on more than one base backup. Multi-based differential backups ...
  60. The differential base attribute for file '%1!s!' of database '%2!s!' has been reset because the file has been restored from ...
  61. The differential partial backup is including a read-only filegroup, '%1!s!'. This filegroup was read-write when the base ...
  62. The dimension cannot be browsed. Either structural changes have been made that require the dimension to be reprocessed, or ...
  63. The dimension contains multiple non-aggregatable attributes: {0}. Consider having just one to avoid non-intuitive query results. ...
  64. The dimension has been reprocessed on the server. To prevent possible browsing errors, click *$*Reconnect*$*. To hide this ...
  65. The dimension has been updated on the server. To prevent possible browsing errors, click *$*Reconnect*$*. To hide this message, ...
  66. The dimension is write-enabled, but not all attribute bindings are in a single table (dimension writeback is only possible ...
  67. The dimension should be materialized (set the 'Materialize' property to 'Regular') because the intermediate dimension '{0}' ...
  68. The dimension table and the measure group table are the same for a fact relationship. The granularity attribute is the key ...
  69. The dimension table is joined to an intermediate fact table. The intermediate fact table is joined, in turn, to an intermediate ...
  70. The dimension type changed from linked to regular while the dialog box was open. You must close and reopen the dialog box. ...
  71. The dimension type changed from regular to linked while the dialog box was open. You must close and reopen the dialog box. ...
  72. The dimension will not be migrated because it depends, through the 'DependsOnDimension' property, on the '{0}' dimension ...
  73. The dimension with ID of '%{dimensionid/}', Name of '%{dimensionName/}' referenced by the '%{cube/}' cube, does not exist. ...
  74. The dimension writeback operation cannot be executed since it is attempting to modify the contents of the read only database ...
  75. The dimension writeback statement contains syntax that is not valid. The last component of a new member definition must be ...