Microsoft KB Archive/257950

= BUG: Incremental Updates of ROLAP Cubes May Fail =

Article ID: 257950

Article Last Modified on 10/16/2003

-

APPLIES TO


 * Microsoft SQL Server OLAP Services

-



This article was previously published under Q257950



BUG #: 7710 (plato7x)



SYMPTOMS
When you use a Microsoft SQL Server 7.0 relational data source, incremental updates of relational OLAP (ROLAP) Cubes may fail, and you receive the following error message:

Error(208): SQL error (There is already an object named 'tableName' in the database.); Time:07/03/2000 16:01:38



CAUSE
With ROLAP cubes, when you use SQL Server as the data source and you use the SQL Server authentication method (username and password) to connect to SQL Server, Microsoft SQL Server OLAP Services creates tables (as userName.tableName) with the username as specified in the data source as the object owner. However, when the tables are dropped (when incremental updates on ROLAP cubes are performed for the second time), the OLAP server attempts to drop tables that have dbo as the owner (for example, dbo.tablename). Because the original tables are not deleted, the processing fails with the 208 error message.



WORKAROUND
You can use either of the following methods to work around this problem. Both methods allow you to create all objects with the user as dbo.

Method 1

 * 1) Use Microsoft Windows NT authentication when you connect to SQL Server. You can specify this within OLAP Manager. In the OLAP Manager, locate and double-click to open the Library folder. Under the Library folder, locate and double-click to open the Datasources folder.
 * 2) Configure OLAP Services to run under a Microsoft Windows NT account that is part of the administrator group on the SQL Server computer. The Windows NT administrator is automatically mapped to the SQL Server 'sa' login and the 'sa' login is mapped to user 'dbo' on all databases.

Method 2
 Continue to use SQL Server authentication. Create a new SQL Server user, named NewUser.  Alias this NewUser user to dbo as follows by using the sp_addalias command in SQL Server Query Analyzer: sp_addalias NewUser, dbo 



STATUS
Microsoft has confirmed that this is a problem in SQL Server OLAP Services version 7.0.

Keywords: kbbug kbpending KB257950

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.