Microsoft KB Archive/940949

= FIX: You receive an error message when you run an UPDATE CUBE statement to update a cube in SQL Server 2005 Analysis Services =

Article ID: 940949

Article Last Modified on 8/13/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Analysis Services

-



Bug #: 50001573 (SQL Hotfix)



Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.



SYMPTOMS
In Microsoft SQL Server 2005 Analysis Services, you run an UPDATE CUBE statement to update a cube. The writeback operation may fail if the following conditions are true:
 * There is no user hierarchy in the cube.
 * The slicing attribute that is specified in the UPDATE CUBE statement differs from the granularity attribute in the measure group.

If you use the Microsoft .NET Framework Data Provider for SQL Server for the data source, you receive the following error message:

Errors in the high-level relational engine. The following exception occurred while the managed IDbConnection interface was being used: This SqlTransaction has completed; it is no longer usable.

If you use the SQL Native Client OLE DB provider for the data source, you receive the following error message:

Internal error: An unexpected exception occurred.



CAUSE
This problem occurs because SQL Server 2005 Analysis Services adds two attribute hierarchies for the slicing attribute and the granularity attribute. The newly added attribute for the slicing attribute prevents the member of the granularity attribute from being copied to the data cache.



RESOLUTION
The fix for this issue was first released in Cumulative Update. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

939537 Cumulative update package for SQL Server 2005 Service Pack 2

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released

Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

939537 Cumulative update package 3 for SQL Server 2005 Service Pack 2

