| title | Translations in Multidimensional Models | Microsoft Docs | |
|---|---|---|
| ms.custom | ||
| ms.date | 06/13/2017 | |
| ms.prod | sql-server-2014 | |
| ms.reviewer | ||
| ms.technology | analysis-services | |
| ms.topic | conceptual | |
| f1_keywords |
|
|
| ms.assetid | 5521f8ef-b10a-4861-9df7-1e43e0a1fb3f | |
| author | minewiskan | |
| ms.author | owend | |
| manager | craigg |
Multilanguage support in [!INCLUDEmsCoName] [!INCLUDEssNoVersion] [!INCLUDEssASnoversion] is accomplished by using translations. A translation contains a language identifier and bindings for properties of [!INCLUDEssASnoversion] objects which can be presented in multiple languages. For example, you can define a translation for an [!INCLUDEssASnoversion] database to present the caption and description of that database in a specified language. For more information about translations, see Cube Translations.
You can define translations in [!INCLUDEssBIDevStudioFull] by using the appropriate designer for the [!INCLUDEssASnoversion] object to be translated. Defining a translation creates a Translation object associated with the appropriate [!INCLUDEssASnoversion] object that has the specified explicit literal values, in the specified language, for the properties of the associated [!INCLUDEssASnoversion] object.
The following objects and properties in [!INCLUDEssASnoversion] can have translations associated with them:
1 The CaptionColumn property of an attribute can be bound to a column in a data source view and can use a Windows collation other than that specified for the instance, unlike other translations.
Translations associated with attributes in database dimensions are handled differently than other translations in the following ways:
-
A column binding, instead of an explicit literal value, can be associated with the
CaptionColumnproperty so that the member names of members for that attribute can be translated. -
A Windows collation other than the collation specified for the instance can be used so that members in the attribute can be appropriately sorted for the language specified in the translation.
You can use the Attribute Data Translation dialog box in [!INCLUDEssBIDevStudioFull] to define translations for attributes in database dimensions. For more information about the Attribute Data Translation dialog box, see Attribute Data Translation Dialog Box (Analysis Services - Multidimensional Data).
If a client application requests information in a specified language identifier, the [!INCLUDEssASnoversion] instance attempts to resolve data and metadata for [!INCLUDEssASnoversion] objects to the closest possible language identifier. If the client application does not specify a default language, or specifies the neutral locale identifier (0) or process default language identifier (1024), then [!INCLUDEssASnoversion] uses the default language for the instance to return data and metadata for [!INCLUDEssASnoversion] objects.
If the client application specifies a language identifier other than the default language identifier, the instance iterates through all available translations for all available objects. If the specified language identifier matches the language identifier of a translation, [!INCLUDEssASnoversion] returns that translation. If a match cannot be found, [!INCLUDEssASnoversion] attempts to use one of the following methods to return translations with a language identifier closest to the specified language identifier:
-
For the following language identifiers, [!INCLUDEssASnoversion] attempts to use an alternate language identifier if a translation for the specified language identifier is not defined:
Specified language identifier Alternate language identifier 3076 - Chinese (Hong Kong SAR, PRC) 1028 - Chinese (Taiwan) 5124 - Chinese (Macao SAR) 1028 - Chinese (Taiwan) 1028 - Chinese (Taiwan) Default language 4100 - Chinese (Singapore) 2052 - Chinese (PRC) 2074 - Croatian Default language 3098 - Croatian (Cyrillic) Default language -
For all other specified language identifiers, [!INCLUDEssASnoversion] extracts the primary language of the specified language identifier and retrieves the language identifier indicated by Windows as the best match for the primary language. If a translation for the best match language identifier cannot be found, or if the specified language identifier is the best match for the primary language, then the default language is used.
You can right-click a translation object in the dimension or cube designer to permanently remove it. You cannot restore or recycle a deleted object, so be sure to review the list of affected objects before continuing.
Globalization scenarios for Analysis Services Multiidimensional
Languages and Collations (Analysis Services)