Can't set Locale Identifier through Analysis Services UI

Discussion in 'microsoft.public.sqlserver.olap' started by Jonathan Levine, Jun 1, 2004.

  1. I'm connecting an Analysis Services Server running on an Windows 2003
    (locale ID 1033) machine to an SQL Server containing Japanese data.

    The default connection is in Locale ID 1033, which unfortunately
    munges the Japanese. So I want to change the Locale ID to 1041.

    I've observed the following when trying to do this via the UI

    1. Right Click the data source
    2. Select Edit...
    3. Select the All tab
    4. Select Locale Identifier
    5. Select Edit Value...
    6. Change the value to 1041
    7. OK out of the dialogs
    8. Select Edit...
    9. Select the All tab

    OBSERVE: the Locale Identifier is set back to 1033. And the Japanese
    is still munged.

    If I go directly into the repository database (in an SQL Server
    database) and directly change the connection string to include Locale
    Identifier=1041, then restart the server, the Japanese appears OK.
    But if I go back to Data Source/Edit.../All, the Locale Identifier is
    still displaying as 1033.

    Is this a bug?


    Jonathan Levine, Jun 1, 2004
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.