UI Translation

SQL Server 2012

  1. The attribute hierarchy must be enabled for the AccountType attribute. Set the AttributeHierarchyEnabled property to True. ...
  2. The attribute ID of '%{attrId/}' for linked subcube with the ID of '%{cubeId/}' and dimension ID of '%{dimId/}' can not be ...
  3. The attribute key cannot be found when processing: %1[Table: '%{Table/}', Column: '%{Column/}', Value: '%{Value/}'%]%[; Table: ...
  4. The attribute key was converted to an unknown member because the attribute key was not found. Attribute %{Property/} of Dimension: ...
  5. The attribute was saved successfully. Subscription views for this entity and model must be regenerated to reflect this change. ...
  6. The attribute with ID of '%{propertyid/}', Name '%{propertyname/}' of referenced by the '%{cubedimension/}' cube dimension, ...
  7. The attribute with ID of '%{PropertyId/}', Name of '%{PropertyName/}' cannot be discretized because there are too few distinct ...
  8. The attribute with ID of '%{propertyid/}', Name of '%{propertyname/}' in the %{aggregationdimension/} aggregation dimension ...
  9. The attribute with ID of '%{propertyid/}', Name of '%{propertyname/}' referenced by the %{aggregationdimension/} aggregation ...
  10. The attribute with ID of '%{propertyid/}', Name of '%{propertyname/}' referenced by the '%{detaildimension/}' measure group ...
  11. The attribute with ID of '%{propertyid/}', Name of '%{propertyname/}' referred to by the '%{aggregationdimension/}' aggregation ...
  12. The attribute, '%s{attribute/}', is not valid in the current procedure call because the attribute is not a PREDICT or a PREDICT_ONLY ...
  13. The attribute, '%{Attribute/}', of the mining model ,'%{Model/}', has a content type, %{Content/}, that is not supported ...
  14. The authoring tool has returned a Null value for an item marked with the msmConfigItemNonNullable attribute. Module table: ...
  15. The AUTODETECT_MINIMUM_SUPPORT parameter for the '%{modelname/}' model is not valid. AUTODETECT_MINIMUM_SUPPORT must be greater ...
  16. The AUTO_DETECT_PERIODICITY parameter for the mining model, %{modelname/}, is not valid. AUTO_DETECT_PERIODICITY should be ...
  17. The availability group '%1!s!' already exists. This error could be caused by a previous failed CREATE AVAILABILITY GROUP ...
  18. The availability group '%1!s!' already has a listener with DNS name '%2!s!'. Availability groups can have only one listener. ...
  19. The availability group '%1!s!' and/or its local availability replica does not exist. Verify that the specified availability ...
  20. The availability group is in a state that prevents adding databases. Verify that the availability group is online and that ...
  21. The availability group is in a state that prevents adding replicas. Verify that the availability group is online and that ...
  22. The availability group is not ready for automatic failover. The primary replica and a secondary replica are configured for ...
  23. The availability group is offline, and is unavailable. This issue can be caused by a failure in the server instance that ...
  24. The availability group listener (network name) with Windows Server Failover Clustering resource ID '%1!s!', DNS name '%2!s!', ...
  25. The availability group listener (network name) with Windows Server Failover Clustering resource ID '%1!s!', DNS name '%2!s!', ...
  26. The availability group listener (network name) with Windows Server Failover Clustering resource ID '%1!s!', DNS name '%2!s!', ...
  27. The availability group listener does not conform to SQL Server configuration guidelines and cannot be modified within SQL ...
  28. The availability group listener with DNS name '%1!s!' is configured to use DHCP. For listeners with this configuration, IP ...
  29. The availability group with Windows Server Failover Clustering resource ID '%1!s!' and/or its local availability replica ...
  30. The availability replica '%1!s!' specified in the READ_ONLY_ROUTING_LIST for availability replica '%2!s!' does not exist. ...
  31. The availability replica for availability group '%1!s!' on this instance of SQL Server cannot become the primary replica. ...
  32. The availability replica of the specified availability group '%1!s!' is being dropped. Wait for the completion of the drop ...
  33. The AVAILABILITY_MODE option has not been specified for the replica '%1!s!'. Reenter the command, specifying an availability ...
  34. The Axis function was indirectly referenced from the context of a statement other than SELECT. Evaluation of expressions ...
  35. The Back Up Database (Differential) task allows you to specify the source databases, destination files or tapes, and overwrite ...
  36. The Back Up Database (Full) task allows you to specify the source databases, destination files or tapes, and overwrite options ...
  37. The Back Up Database (Transaction Log) task allows you to specify the source databases, destination files or tapes, and overwrite ...
  38. The Back Up Database task allows you to specify the source databases, destination files or tapes, and overwrite options for ...
  39. The background checkpoint thread has encountered an unrecoverable error. The checkpoint process is terminating so that the ...
  40. The background thread running lazy writer encountered an I/O error. Physical file: %{PhysicalFile/}. Logical file: %{LogicalFile/}. ...
  41. The backup cannot be performed because '%1!s!' was requested after the media was formatted with an incompatible structure. ...
  42. The backup data at the end of "%1!s!" is incorrectly formatted. Backup sets on the media might be damaged and unusable. To ...
  43. The backup file path/name where database will be backed up. If only backup file name is mentioned without the location, the ...
  44. The backup media on "%1!s!" is part of media family %2!s! which has already been processed on "%3!s!". Ensure that backup ...
  45. The backup of the file or filegroup "%1!s!" is not permitted because it is not online. Container state: "%2!s!" (%3!s!). ...
  46. The backup of the system database on the device %1!s! cannot be restored because it was created by a different version of ...
  47. The backup on the secondary database "%1!s!" was terminated, but a terminate backup message could not be sent to the primary ...
  48. The backup operation has detected an unexpected file in a FILESTREAM container. The backup operation will continue and include ...
  49. The backup set cannot be restored because the database was damaged when the backup occurred. Salvage attempts may exploit ...
  50. The backup set on device '%1!s!' was terminated while it was being created and is incomplete. RESTORE sequence is terminated ...
  51. The backup store file '%{pathname/}'is empty or doesn't contain proper header; database can not be succesfully restored. ...
  52. The backup store stream is empty or doesn't contain proper header; database can not be succesfully restored. Operation cancelled. ...
  53. The Backup, Restore or Synchronize command cannot be executed within a user initiated transaction or in transactional batch. ...
  54. The BackupDirectory registry key is not configured correctly. This key should specify the root path where disk backup files ...
  55. The BaseEntity of the {0} is the {1}. Based on the SelectedPath, the specified DrillthroughContext can be used only if the ...
  56. The batch '{0}' cannot be found. This error occurs when the batch was not previously opened by the CreateBatch method. It ...
  57. The begin and end action at postition %I64u are not of the same type. Specify matching actions that are the same type and ...
  58. The begin and end columns at position %I64u are not of the same type. Specify matching columns that are the same type and ...
  59. The BI semantic model in the '%{database/}' database is inconsistent. A database must contain a cube when the database contains ...
  60. The binary code for the script is not found. Please open the script in the designer by clicking Edit Script button and make ...
  61. The binary field is too large. The adapter attempted to read a binary field that was %1!d! bytes long, but expected a field ...
  62. The binary operation "%1!s!" failed with error code 2!8.8X!. An internal error occurred, or an out-of-memory condition exists. ...
  63. The binary representaion of the data that was read from the file. This data is used for troubleshooting by Microsoft support. ...
  64. The binding expression '{0}' for Grouping stream is not valid. A correct binding should be one or more method calls on top ...
  65. The binding is missing for the {0}. Role must have exactly one Relation binding, unless the containing Entity is bound to ...
  66. The binding of the measure group '%{measuregroupid/}' references a server measure group '%{remotemgid/}' that does not exist. ...
  67. The binding or the grouping for layer '{2}' in the {0} '{1}' is not valid. A spatial element cannot have more than one matching ...
  68. The bindings for this relationship are not valid. To correct this issue, you can either delete and re-create the relationship, ...
  69. The blob store returned a stream that corresponds to a new blob, which has its initial position set to a value other than ...
  70. The blob store returned a stream that corresponds to an existing blob, which has its its initial position set to a value ...
  71. The Boolean property value that specifies whether the linked server supports remote procedure calls (RPCs) with output parameters. ...
  72. The boolean that indicates whether the client application allows the user to group on this attribute. This value should be ...
  73. The boolean that indicates whether the client application should display the target entity as a look-up when the containing ...
  74. The boolean that indicates whether the client application should treat the entity as a lookup table or as a full-fledged ...
  75. The boolean that indicates whether the client application shows the role to the user and whether the fields of the related ...
Deutsch (Deutschland)
German (Germany) Español (España)
Spanish (Spain) Français (France)
French (France) italiano
Italian 日本語
Japanese 한국어
Korean Português
Portuguese Русский
Russian English
English (United States)