We are in the process of "localising" our transaction system - including
regional languages.

Is there a site where I can get information on how the data warehouse / mart
modeling and AS2000 cubes need to be changed for introducing regional
languages in reports?

TIA

--
Message posted via http://www.sqlmonster.com

In SQL2K, we are somewhat listed in this area. Look in BOL under the topic:
Multiple Language Implementation using Member Properties

In SQL2K5, there is an entirely new translation subsystem which handles all
of this.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Angie via SQLMonster.com" <forum (AT) nospam (DOT) SQLMonster.com> wrote

Thanks very much!

I was able to check this out using French and English and it worked perfectly
fine

But when I use Russian, I get only "????" as output on the Query analyser as
well as on AS2000 cube browser.

I did set the locale ID to Russian and checked the affect using word - it
does seem to work fine.

Are there any specific settings in SQL server 2000 that need to be set?

ps- all columns are already defined as nvarchar

TIA

--
Message posted via http://www.sqlmonster.com

In my case, dimension member data will be a mix of English and other
languages. So I don't need to show data based on the LocaleID of the client
workstation. I just need to display whatever it is that I have in the
database.

But the Cube browser does not seem to be able to show Russian although I am
able to see this on query analyser. Is there some setting that I need to
enable?

tia

--
Message posted via http://www.sqlmonster.com

Member names are stored as unicode. we depends on the front-end component to
render it. what seems to be happening is that the cube browser can render in
ascii and roman languages, but not ones that need additional fonts -- I
don't know if that is true or not. It wouldn't surprise me as we consider it
to be an administrative component; not a end-user tool.

Make sure your regional settings are in russian as well as you session --
and machine settings -- so the unicode characters which need different fonts
will be loaded.

Sorry -- I've played a bit in this area -- I'm not an expert by any means.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Angie via SQLMonster.com" <forum (AT) SQLMonster (DOT) com> wrote