SSAS - deploying to a renamed database

SSAS - deploying to a renamed database by Darren Gosbell

Active

Type:	Bug
ID:	281595
Opened:	6/6/2007 5:30:36 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

If you rename a database in SQL Server Management Studio and then try to deploy from BIDS to this database you cannot. BIDS expects the database name and ID to be identical.

14 July 2008 - I just checked this in SQL 2008 RC0 and it is not fixed

Details (expand)

English

SQL Server 2005 SP2 - Developer Edition

Analysis Services

Windows XP SP2 Professional

US English

Go into SSMS - rename "Adventure Works DW" to "Adventure Works DW2"
Go into BIDS and open up the "Adventure Works Sample"
Change your target database in the deployment settings to "Adventure Works DW2"
Try to deploy - you will get and error

An error about a database called "Adventure Works DW2" already existing on the server.

If you changer your target database back to "Adventure Works DW" - your database gets renamed!

BIDS should connect to the server and try to find the database by it's name and fetch the ID. If the database does not exist the ID should be set to the same value as the name.

And if a database with the same ID that is being deployed exists on the server, but with a different name, the user should have the option of overwriting or generating a new ID. This supports scenarios where the user wants to rename the existing database and then deploy a new version to do side by side testing. This second point is minor, but the idea is that the user should not need to be aware of the internal ID's that SSAS is using. It should be transparent to them and at the moment it is not.

0 attachments

Posted by Microsoft on 8/17/2007 at 1:11 PM

Thank you for reporting, Darren. This is a duplicate of an exisitng bug that we want to fix.

Posted by Microsoft on 8/17/2007 at 1:11 PM

Closing as we have another bug to track this issue.

Posted by Darren Gosbell on 8/17/2007 at 3:48 PM

Can you post a link to the duplicate bug so that I can add it to my watch list?

Posted by Microsoft on 8/17/2007 at 4:14 PM

Unfortuantely not--the duplicate bug is not a Connect bug.

Posted by Microsoft on 12/17/2007 at 10:48 AM

Thank you for reporting this problem, we fixed it in the 2008 release.

Posted by Darren Gosbell on 7/13/2008 at 9:49 PM

I just re-opened this item as it is not fixed in SQL 2008 RC0

Posted by Darren Gosbell on 11/18/2008 at 2:53 PM

I recently posted an extensive blog post outlining the issue as I see it http://geekswithblogs.net/darrengosbell/archive/2008/09/28/ssas-deploying-to-renamed-databases.aspx