FIX: Specify the Analysis Services Client Locale on the Connection String

View products that this article applies to.

BUG #: 14103 (Plato7x)

SYMPTOMS

SQL Server 2000 Analysis Services provides for the multiple language implementation of dimension member names and member properties values through the use of the Caption member property type and the Language property type for dimension member properties. This implementation permits different dimension member names to be displayed based on the locale setting of the client computer. For details about how to implement multiple languages by using member properties, see the "Multiple Language Implementation Using Member Properties" topic in SQL Server Books Online. You can also visit the following Microsoft Web site:

http://msdn2.microsoft.com/en-us/library/aa178241(SQL.80).aspx (http://msdn2.microsoft.com/en-us/library/aa178241(SQL.80).aspx)

Although using the locale of the client computer works well for two-tier Analysis Services solutions, three-tier solutions typically connect to and query the Analysis Services server from a middle-tier computer that may not match the locale of the client. In this scenario, the autodetection of the client locale cannot be used because all connections are made from the same middle-tier computer.

To use the multiple language functionality, you must specify the client locale on the connection string when connecting from the client to the middle-tier computer. You can specify the locale by using the Locale Identifier property in Microsoft ActiveX Data Objects (Multidimensional) (ADO MD) or the DBPROP_INIT_LCID property setting in the OLAP portion of OLE DB when connecting to the Analysis Services server.

Before this hotfix, the Locale settings were not correctly applied for the connection. As a result, the member names and properties were displayed in the language of the middle-tier computer or the client computer, regardless of the value that was specified for the locale when connecting to the Analysis Services server.

Back to the top

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 (http://support.microsoft.com/kb/290211/ ) How to obtain the latest SQL Server 2000 service pack

Back to the top

Hotfix information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

   Date         Time   Version            Size    File name
   ------------------------------------------------------------
   13-May-2003  06:14  8.0.806.0         217,668  Msmdcb80.dll     
   23-Jul-2003  04:23  8.0.0.843       4,055,616  Msmddo80.dll     
   22-Aug-2003  06:18  8.0.853.0       1,032,768  Msmdgd80.dll     
   05-Aug-2003  01:36  8.0.823.0         172,608  Msmdpump.dll     
   13-May-2003  06:14  8.0.0.761       9,638,464  Msmdsgn80.dll    
   22-Aug-2003  01:07  8.0.853.0       1,831,492  Msmdsrv.exe      
   22-Aug-2003  06:18  8.0.853.0       2,077,264  Msolap80.dll     
   10-May-2003  08:05  8.0.820.0         213,069  Msolap80.rll

Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

SQL Server 2000 Analysis Services 64-bit

For additional information about a hotfix build that is designed to be applied on a server that is running SQL Server 2000 Analysis Services 64-bit, or to find out if a fix is scheduled to be included in SQL Server 2000 Analysis Services 64-bit Service Pack 4, click the following article number to view the article in the Microsoft Knowledge Base:

822985 (http://support.microsoft.com/kb/822985/ ) Hotfix Information for Build 8.0.861.0 of SQL Server 2000 Analysis Services 64 bit

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.

Back to the top