Connecting the System to the Translation Database

After languages have been enabled for the project, you must configure the system so that MicroStrategy can retrieve the translated data. This configuration varies depending on the data internationalization (DI) model used:

Connection-based DI model: You must specify a database connection for each language.
SQL-based DI model: You must specify a column pattern or table pattern for each language.

These models are described in detail in Storing Translated Data: Data Internationalization Models.

Connecting the System to a Single Database: SQL-Based DI Model

For a detailed explanation of how to set up tables and columns to support SQL-based data internationalization, see the Project Design Help, Internationalization through tables and columns or databases section. The Project Design Help provides extensive examples and images of table and column naming patterns, explains the use of only tables, only columns, or both tables and columns, the use of logical views, and so on.

Your table suffixes for languages should be consistent and unified across the entire warehouse. For example, if you have Spanish translations in your warehouse, the suffix should be _SP for all tables that include Spanish translations, and not _SP, _ES, _EP, and so on.

For detailed steps to connect the system to your translation database, see the Project Design Help, Enabling data internationalization through SQL queries section. The Project Design Help includes details to select your table or column naming pattern, as well as functions to use if your naming pattern does not use suffixes.

If you are changing from one DI model to another, you must reload the project after completing the steps above. Settings from the old DI model are preserved, in case you need to change back.

Connecting the System to more than one Database: Connection-Based DI Model

If you are using a connection-based DI model, you must specify a database connection for each data warehouse that stores translated data.

Connection mapping can also be performed using Command Manager.

For a detailed explanation of how to set up your databases to support data internationalization, see the Project Design Help, Internationalization through tables and columns or databases section. The Project Design Guide provides extensive examples and images of translation table structures in different databases, as well as important restrictions on logical views and supported character sets.

The database connection that you use for each data warehouse must be configured in MicroStrategy before you can provide translated data to MicroStrategy users.

The procedure in the Project Design Guide assumes that you will enable the connection-based DI model. If you decide to enable the SQL-based model, you can still perform the steps to enable the connection-based model, but the language-specific connection maps you create in the procedure will not be active.

The physical schemas of all data warehouses to be used for data internationalization should be identical.

You must have the Configure Connection Map privilege, at either the user level or the project level.

Objects displayed in the Connection Mapping Editor are limited to those objects the user has Browse and Use permissions for.

For detailed steps to connect the system to more than one data warehouse, see the Project Design Help, Enabling data internationalization through connection mappings section.

If you are changing from one DI model to another, you must reload the project after completing the steps in the Project Design Help. Settings from the old DI model are preserved, in case you need to change back.

You can delete a connection mapping by right-clicking on the connection map and selecting Delete.