SQL Server 2008

  1. The DESX keyword is now deprecated and will be removed in a future version of SQL Server. Avoid using it in new development ...
  2. The detail dimension with ID of '%{dimensionid/}', Name of '%{dimensionname/}' referenced by the '%{detail/}' measure group ...
  3. The Detect Categories tool automatically detects the rows in a table that share similar properties, then groups them into ...
  4. The device information is invalid because the closing tag for the element '{0}' was expected but not found (rrExpectedEndElement). ...
  5. The device information is invalid because the opening tag for a parameter was expected but not found (rrParameterExpected). ...
  6. The diagram cannot be opened because the current owner of the diagram no longer exists. Do you want to take over ownership ...
  7. The diagram cannot be opened because the current owner of the diagram no longer exists. Do you want to take over ownership ...
  8. The dialog lifetime value of %1!s! is outside the allowable range of %2!s! to %3!s!. Specify a valid dialog lifetime value. ...
  9. The dialog will backup metadata for ROLAP partitions, metadata and aggregations for HOLAP partitions, metadata, source data ...
  10. The dialog {0}:{1} could not create the target endpoint because the EXECUTE AS failed for user {2} with the following error: ...
  11. The differential backup is not allowed because it would be based on more than one base backup. Multi-based differential backups ...
  12. The differential base attribute for file '%1!s!' of database '%2!s!' has been reset because the file has been restored from ...
  13. The differential partial backup is including a read-only filegroup, '%1!s!'. This filegroup was read-write when the base ...
  14. The dimension cannot be browsed. Either structural changes have been made that require the dimension to be reprocessed, or ...
  15. The dimension contains multiple non-aggregatable attributes: {0}. Consider having just one to avoid non-intuitive query results. ...
  16. The dimension has been reprocessed on the server. To prevent possible browsing errors, click *$*Reconnect*$*. To hide this ...
  17. The dimension has been updated on the server. To prevent possible browsing errors, click *$*Reconnect*$*. To hide this message, ...
  18. The dimension is write-enabled, but not all attribute bindings are in a single table (dimension writeback is only possible ...
  19. The dimension should be materialized (set the 'Materialize' property to 'Regular') because the intermediate dimension '{0}' ...
  20. The dimension table and the measure group table are the same for a fact relationship. The granularity attribute is the key ...
  21. The dimension table is joined to an intermediate fact table. The intermediate fact table is joined, in turn, to an intermediate ...
  22. The dimension type changed from linked to regular while the dialog box was open. You must close and reopen the dialog box. ...
  23. The dimension type changed from regular to linked while the dialog box was open. You must close and reopen the dialog box. ...
  24. The dimension will not be migrated because it depends, through the 'DependsOnDimension' property, on the '{0}' dimension ...
  25. The dimension with ID of '%{dimensionid/}', Name of '%{dimensionName/}' referenced by the '%{cube/}' cube, does not exist. ...
  26. The dimension writeback operation cannot be executed since it is attempting to modify the contents of the read only database ...
  27. The dimension writeback statement contains syntax that is not valid. The last component of a new member definition must be ...
  28. The direct cell writeback operation cannot be committed, because the '%{measuregroup/}' measure group has no direct write-enabled ...
  29. The direction of the self-join from the column '{1}' to the column '{2}' in '{0}' is not consistent with the logical key ...
  30. The DISCOVER_ENUMERATORS schema rowset returns the supported enumerators for a provider, including data types and values. ...
  31. The DISCOVER_LITERALS schema rowset returns the information about supported literals for a provider, including data types ...
  32. The DISCOVER_PROPERTIES schema rowset returns information about the properties supported by an XML for Analysis provider. ...
  33. The DISCOVER_SCHEMA_ROWSETS schema rowset returns a list of all RequestTypes enumeration values that are supported by the ...
  34. The discretization method specified for the '%{property/}' attribute is not valid because this attribute is bound to a non-numeric ...
  35. The discretization parameters (DiscretizationMethod and DiscretizationBucketCount) of the '%{column/}' column of the '%{structure/}' ...
  36. The discretized attribute with ID of '%{propertyId/}', Name of '%{propertyName/}'in the '%{dimension/}' dimension has a name ...
  37. The disk resource '{0}' could not be found on the SQL Server failover cluster. Ensure that the name you provided is correct, ...
  38. The disk resource '{0}' has a dependency on resource '{1}'. To use a disk in a new SQL Server failover cluster instance, ...
  39. The disk resource '{0}' is already in use by resource '{1}'. To use a disk in a new SQL Server failover cluster instance, ...
  40. The DisplayName property indicates the display name of the service. This string has a maximum length of 256 characters. The ...
  41. The distance from the range to the scale in percentage of the size of the gauge (height for horizontal gauges, width for ...
  42. The distance from the tip of the pointer to the scale, measured in percentage of the size of the gauge (height for horizontal ...
  43. The distributed transaction associated with UOW %1!s! is in PREPARE state. Use KILL UOW WITH COMMIT/ABORT syntax to kill ...
  44. The distributed transaction associated with UOW %1!s! is not in PREPARED state. Use KILL UOW to kill the transaction instead. ...
  45. The distributed transaction with UOW %1!s! was forced to commit. MS DTC became temporarily unavailable and forced heuristic ...
  46. The Distribution Agent encountered an error and was unable to write a tracer token to the MStracer_history table in the distribution ...
  47. The Distribution Agent is using the OLEDB streaming optimization for replicating binary large objects greater than %1!d! ...
  48. The Distribution Agent reached the end of current command (transaction: 1 command %2!d!), but the number of bytes read (%3!d!) ...
  49. The Distribution Agent was unable to update the cached log sequence numbers (LSNs) for Originator %1!s!, OriginatorDB %2!s!, ...
  50. The distribution database '%1!s!' cannot be opened due to inaccessible files. The database will be dropped, but distribution ...
  51. The distribution database '%1!s!' has a compatibility level of %2!s!, which is different from that of the master database. ...
  52. The distribution database '{0}' cannot be deleted until all Publishers using this distribution database have been disabled. ...
  53. The distribution database for the contacted Oracle instance does not match the expected name of the distribution database. ...
  54. The distribution database stores changes to transactional publications until Subscribers can be updated. It also stores historical ...
  55. The distribution Publisher property, 'distributor_password', has no usage and is not supported for a Distributor running ...
  56. The distributor login of the logreader agent must be a member of the sysadmin role or db_owner role in distribution database. ...
  57. The DLLs that are listed in the report define extended stored procedures that have not been registered using the full path. ...
  58. The DMX statement, INSERT INTO .COLUMN_VALUES, is not supported since the '%{structure/}' mining structure has one or more ...
  59. The DNS search list on computer {0} does not match. To correct this, synchronize the Public, not Private/heartbeat, network's ...
  60. The document cannot be created because the '{0}' type does not have an appropriate constructor. Make sure that the product ...
  61. The document cannot be created because the '{0}' type is not inherited from DocumentObject. Make sure that the product is ...
  62. The DOM parser failed to load and parse the stream. URL:'%{strURL/}' Reason: '%{strReason/}' Source:'%{strSource/}'. File ...
  63. The domain network is not the first bound network. This will cause domain operations to run slowly and can cause timeouts ...
  64. The DTS upgrade analyzer utility analyzes DTS packages and lists issues that are likely to prove problematic while migrating ...
  65. The dynamic filters property for publication '%1!s!' has been incorrectly set. Use sp_changemergepublication to reset the ...
  66. The edition for the SQL Server Analysis Services feature is not the same on all nodes. The edition on computer {0} is not ...
  67. The edition for the SQL Server Database Services feature is not the same on all nodes. The edition on computer {0} is not ...
  68. The edition of Reporting Services that you are using only supports SQL Server relational databases for report data sources. ...
  69. The edition of Reporting Services that you are using requires that you use local SQL Server relational databases for report ...
  70. The edition of the Analysis Services instance to which a project will be deployed. This provides the default for new projects. ...
  71. The edition of the currently installed instance is different from the specified edition. When you add features to an existing ...
  72. The edition of the currently installed remote node cannot be determined. All failover cluster nodes must be the same SQL ...
  73. The element "{0}" in the ElementPath contains a reference to its value and a subelement. References to both value and subelement ...
  74. The element cannot be found in a collection. This error happens when you try to retrieve an element from a collection on ...
  75. The element indicates whether the client application displays the role's target entity fields and field folders when the ...