Browsing Translations
Upon
completing the addition of our Translations, we would next deploy the
solution, as we have done in various articles of this series. Once this has
been accomplished, we can fully leverage the Browser that the Cube
Designer and Dimension Designer each make available to us. While we
have not input any Translations, we can still examine the simple steps
involved in "switching Translations" within the Cube Browser by
taking the following steps:
1.
Return to the ANSYS051_Translations.cube
tab, which we opened via the Cube Designer earlier (re-open if
necessary), by clicking the appropriately marked tab, as depicted in Illustration
53.
Illustration 53: Return
to the ANSYS051_Translations Cube Designer View ...
2.
Click the Browser
tab to initialize the Browser for the Designer.
Once the Browser
loads, we receive a message here indicating that a connection cannot be made,
due to the fact that we have not deployed the solution and performed a
reconnection. Our point here is to show that, had we populated the Translations,
and then performed the deployment / reconnection, our next step would be to
switch among the Translations for the data displayed by selecting the desired
Translation from the Language selector (to the immediate right of
the Perspectives selector, atop the Browser tab). Doing so for Spanish
(Spain), we would make the appropriate
selection within the Language selector, which would be populated once
deployed / reconnected, as shown in Illustration 54.
Illustration 54: Shifting
between Translations in the Cube Designer Browser ...
Performing the switch
between Translations is quite similar within the Dimension Designer,
and consists of the following steps:
3.
Return to the Dim
Customer.dim tab, which we opened via the Dimension Designer earlier
(re-open if necessary), by clicking the appropriately marked tab, as depicted
in Illustration 55.
Illustration 55: Return
to the Dim Customer.dim Dimension Designer View ...
4.
Click the Browser
tab to initialize the Browser for the Designer.
Here, as was the case
with the Cube Browser, had we populated the Translations, and
then performed the deployment / reconnection, our next step would be to switch
among the Translations for the data displayed by selecting the desired Translation
from the Language selector (to the immediate right of the Hierarchy
selector, atop the Browser tab). Doing so for Spanish (Spain), we would make the appropriate
selection within the Language selector, which would be populated once
deployed / reconnected, as shown in Illustration 56.
Illustration 56: Shifting
between Translations in the Dimension Designer Browser ...
And so it becomes clear
that shifting among Translations within the Browsers is a simple
matter of making a choice of a valid Translation with the respective dropdown
selector, once we have deployed / reconnected with the appropriate Translation
entries in place.
5.
Select File
-> Save All from the main menu to save our
work through this point, as depicted in Illustration 57.
Illustration 57: Saving All Work
from Our Session
6.
Select File
-> Exit, when ready, to leave the Business
Intelligence Development Studio.
Conclusion
In this article, we introduced
and overviewed Translations, a feature that allows us to support
localized presentations of Analysis Services objects with ease. After
introducing the concept of Translations, we overviewed their addition,
and discussed ways in which they can offer flexibility in supporting our cube
and solution / application end users. In preparation for our examination of the
steps involved in extending our cubes to leverage Translations, we
prepared Analysis Services, and our environment, by creating an Analysis
Services Project to house our development efforts, and to serve as a
platform for the design of a quick cube model, within which to perform
subsequent procedures in our session. We next performed the steps that are
common to the design and creation of any cube within Analysis Services,
including the creation of a Data Source, containing the information Analysis
Services needs to connect to a database, and a Data Source View
containing schema information.
We then created a basic cube, referencing our Data
Source and Data Source View, based upon data from our sample
relational tables. Next, we discussed the detailed steps of adding Translations,
via the Translations tab of the Cube and Dimension Designers.
Finally, after discussing the need for deploying and reconnecting our solution,
after adding the specific Translation values for both types of Translations,
we discussed the steps involved in switching between available Translations
within each of the Cube and Dimension Browsers.
»
See All Articles by Columnist William E. Pearson, III
Discuss this article in the MSSQL Server 2000 Analysis Services and MDX Topics Forum.
» 
Comment and Contribute
