Globalization scenarios for Analysis Services

Applies to: SQL Server Analysis Services Azure Analysis Services Fabric/Power BI Premium

SQL Server Analysis Services stores and manipulates multilingual data and metadata for both tabular and multidimensional data models. Data storage is Unicode (UTF-16), in character sets that use Unicode encoding. If you load ANSI data into a data model, characters are stored using Unicode equivalent code points.

The implications of Unicode support means that SQL Server Analysis Services can store data in any of the languages supported by the Windows client and server operating systems, allowing read, write, sort, and comparison of data in any character set used on a Windows computer. BI client applications consuming SQL Server Analysis Services data can represent data in the user's language of choice, assuming the data exists in that language in the model.

Language support can mean different things to different people. The following list addresses a few common questions related to how Analysis Services supports languages.

• Data, as already noted, is stored in any Unicode-encoded character set found on a Windows client operating system.

• Metadata, such as object names, can be translated. Although support varies by model type, both multidimensional and tabular models support the addition of translated strings inside the model. You can define multiple translations, and then use a locale identifier to determine which translation is returned to the client. See Features below for more details

• Error, warning, and informational messages returned by the SQL Server Analysis Services engine (msmdsrv) are localized into the 43 languages supported by Office and Office 365. No configuration is required to get messages in a specific language. The locale of the client application determines which strings are returned.

• Configuration file (msmdsrv.ini) and AMO PowerShell are in English only.

• Log files will contain a mix of English and localized messages, assuming you have installed a language pack on the Windows server that Analysis Services runs on.

• Documentation and tools, such as Management Studio and SQL Server Data Tools, are translated into these languages: Chinese Simplified, Chinese Traditional, French, German, Italian, Japanese, Korean, Portuguese (Brazil), Russian, and Spanish. Culture is specified during installation.

For multidimensional models, Analysis Services lets you set language, collation, and translations independently throughout the object hierarchy. For tabular models, you can only add translations: language and collation are inherited by the host operating system.

Scenarios enabled through Analysis Services globalization features include:

• One data model provides multiple translated captions so that field names and values appear in the user's language of choice. For companies operating in bi-lingual countries/regions such as Canada, Belgium, or Switzerland, supporting multiple languages across client and server applications is a standard coding requirement. This scenario is enabled through translations and currency conversions. See Features below for details and links.

• Development and production environments are geo-located in different countries/regions. It's increasingly common to develop a solution in one country/region and then deploy it another. Knowing how to set language and collation properties is essential if you are tasked with preparing a solution developed in one language, for deployment on a server that uses a different language pack. Setting these properties allows you to override the inherited defaults that you get from the original host system. See Languages and Collations (Analysis Services) for details about setting properties.

Features for building a globalized multi-lingual solution

At the client level, globalized applications that consume or manipulate SQL Server Analysis Services multidimensional data can use the multilingual and multicultural features in SQL Server Analysis Services.

You can retrieve data and metadata from SQL Server Analysis Services objects on which translations have been defined automatically by providing a locale identifier when connecting to an SQL Server Analysis Services instance.

See Globalization Tips and Best Practices (Analysis Services) for design and coding practices that can help you avoid problems related to multi-language data.

Capability	Tabular	Multidimensional
Languages and Collations (Analysis Services)	Inherited from the operating system.	Inherited, but with the ability to override both language and collation for major objects in the model hierarchy.
Scope of translation support	Captions and descriptions.	Translations can be created for object names, captions, identifiers, and descriptions, can also be in any Unicode language and script. This is true even when the tools and environment are in another language. For example, in a development environment that uses English language and a Latin collation throughout the stack, you can include in your model an object that uses Cyrillic characters in its name.
Implementing translation support	Create using SQL Server Data Tools to generate translation files that you fill in and then import back into the model. See Translations in Tabular models (Analysis Services) for details.	Create usingSQL Server Data Tools to define the translations for the caption, description, and account types for cubes and measures, dimension and attributes. See Translations in Multidimensional Models (Analysis Services) for more information.
Currency conversion	Not available.	Currency conversion is through specialized MDX scripts that convert measures containing currency data. You can use the Business Intelligence Wizard in SQL Server Data Tools - Business Intelligence to generate an MDX script that uses a combination of data and metadata from dimensions, attributes, and measure groups to convert measures containing currency data. See Currency Conversions (Analysis Services).

See Also

Translation support in Analysis Services
Internationalization for Windows Applications
Globalization
Writing Windows Store apps with locale-based adaptive design