For the past few years I was working on data warehouse project that is customized and installed for different clients. As part of customization, sometimes clients might request to use different names for dimensions, attributes or measures. For example in Geography dimension for US customers that do business just in US you would want to have hierarchy Country-State-City, but for Canadian customer the same hierarchy would be Country-Province-City. For customers that do business in US and Canada, the same hierarchy could be called Country-State|Province-City.
| Customizing object names in Analysis Services database using translations |
| Written by Vidas Matelis |
| Monday, 03 December 2007 19:48 |
|
Link to source Analysis Services 2005 provides easy interface to rename dimensions, attributes or measures. But things become more complicated when these object names are used in cube MDX script - these renames can break script. Instead of renaming actual object, you might consider using “Translation” feature of Analysis Services 2005. I usually create translation for language that matches clients PCs language. This way Excel 2007 uses translated names without any additional steps. For other SSAS clients you might have to specify locale ID in connection string parameter, example: ”Language Identifier=1033;”. With translations you can choose to rename just a few objects. If no translations exists, Analysis Services uses default object name assigned during object creation. Here is a quick example on how to rename a few attributes in Adventure Works database. This is how Geography translation tab looks with shipped version of Adventure Works database:
I added translation for “State-Province” and “Postal Code” attributes and rename them to “State” and “Zip”:
After deploying this change to there server, there are results in Excel 2007:
|
Latest Author Articles
- How to use MDW to collect Analysis Services 2008 performance counters
- Analysis Services 2008 performance counters
- Microsoft SQL Server 2008 RC0 - New Adventure Works Sample Databases for SSAS
- SSAS 2008 RC0 - New function SYSTEMRESTRICTSCHEMA for restricted schema rowsets - DMVs
- Excel 2007 Pivot Table with SharePoint On Vista PC - works good after SP1
Top Rated
- SSAS Implementation Best Practices slides in PDF format
- SSRS Report Against a SSAS Parent Hierarchy
- Using AS Data Mining to Add Forecast Values to a Cube
- Handling inter-dimensional members dependency and reducing cube sparsity using reference dimensions in Analysis Services 2005
- Cube structure optimization for MDX query performance in Analysis Services 2005 SP2: Tips for Parent Child Hierarchies usage
- Handling Multiple Calendars with a M2M Scenario
- Passing MDX parameters in Reporting Services reports
- Using UserName to Control Data Access and Default Member in SSAS 2K5 (Carrie Williams)







