FIX: The return value of the Member_Unique_Name property in SQL Server 2005 Analysis Services differs from the return value in SQL Server 2000 Analysis Services

This article describes the following about this hotfix release:

• The issues that are fixed by this hotfix package
• The prerequisites for installing the hotfix package
• Whether you must restart the computer after you install the hotfix package
• Whether you must make any registry changes
• The files that are contained in the hotfix package

In Microsoft SQL Server 2000 Analysis Services, the Member_Unique_Name property returns a value of [Dimension].[Hierarchy].&[member key] when the MemberKeysUnique property for the hierarchy is set to TRUE. In Microsoft SQL Server 2005 Analysis Services, the Member_Unique_Name property returns a value of [Dimension].[Hierarchy].[level name].&[member key] even when the MemberKeysUnique property is set to TRUE. This behavior change in SQL Server 2005 Analysis Services may break existing Analysis Services applications if the application relies on the name format that SQL Server 2000 Analysis Services uses.

Service pack information

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

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

• Microsoft SQL Server 2005 Service Pack 1 (SP1)
  
  For more information, click the following article number to view the article in the Microsoft Knowledge Base:
  913089  (http://support.microsoft.com/kb/913089/ ) How to obtain the latest service pack for SQL Server 2005

Restart information

You must restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry.

File information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.

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 item in Control Panel.

SQL Server 2005 Analysis Services, 32-bit version

SQL Server 2005 Analysis Services, x64-based version

SQL Server 2005 Analysis Services, Itanium-based version

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

This problem was corrected in Microsoft SQL Server Service Pack 2.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: