Renaming databases sloooow

We have SSAS 2005 setup which rebuilds our cubes each night on a single server. What we were trying to do is make it so that each night a second database is built and processed for the next days data, and then the previous days database is dropped and the new one renamed to the correct name. This was meant to minimize downtime. The problem is, renaming the database is slow (it takes hours!) .. is this a bug? We've tried renaming it through AMO and SQL Studio, both of which cause the CPU to go up to 50% for more than 2 hours before the rename completes. These databases have approx 8 cubes with many measure groups.

You should be able to change database name by issuing a simple XMLA command like:

<Alter AllowCreate="true" ObjectExpansion="ObjectProperties" xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
<Object>
<DatabaseID>CountMeasure</DatabaseID>
</Object>
<ObjectDefinition>
<Database xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ID>MyDb1</ID>
<Name>MyDb2</Name>
</Database>
</ObjectDefinition>
</Alter>

Try running Profiler and see what is happening during database rename.
During rename you should see bunch of Notification events about changes in database objects.

See how long in average each Notification Event takes. Is it possible rename of the database is getting blocked by some other operation?

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

rename machine name

Hi,
After installing SQL 7, I rename the server machine name from A to B. I run
the setup and change server name. The server name shows B when using selec
t @.servername. But, in SQL log file, there is one line still show the old n
ame
Using 'SSMSRP70.DLL' version '7.0.961' to listen on 'A'.
What's the reason for that? Thanks.
Yulingsp_dropserver oldname
sp_addserver newname, LOCAL
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"Yuling" <anonymous@.discussions.microsoft.com> wrote in message
news:FA945477-ADF0-4A31-96DA-CAC304CC9547@.microsoft.com...

quote:

---

> Hi,
> After installing SQL 7, I rename the server machine name from A to B. I

---

run the setup and change server name. The server name shows B when using
select @.servername. But, in SQL log file, there is one line still show the
old name

quote:

---

> Using 'SSMSRP70.DLL' version '7.0.961' to listen on 'A'.
> What's the reason for that? Thanks.
> Yuling

---

|||Look at question 5 in the following article:
195759 INF: Frequently Asked Questions - SQL Server 7.0 - SQL Setup
Basically you have to do the following:
Open the SQL Server Network Utility. Select Multiprotocol and
click on Remove. Click Add and select Multiprotocol from the list on the
left
hand window. This should now display the correct servername. Once
Multiprotocol is added, restart the SQL Server service and this should
correct
the problem.
Rand
This posting is provided "as is" with no warranties and confers no rights.sql

rename machine name

Hi
After installing SQL 7, I rename the server machine name from A to B. I run the setup and change server name. The server name shows B when using select @.servername. But, in SQL log file, there is one line still show the old nam
Using 'SSMSRP70.DLL' version '7.0.961' to listen on 'A'
What's the reason for that? Thanks
Yulingsp_dropserver oldname
sp_addserver newname, LOCAL
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Yuling" <anonymous@.discussions.microsoft.com> wrote in message
news:FA945477-ADF0-4A31-96DA-CAC304CC9547@.microsoft.com...
> Hi,
> After installing SQL 7, I rename the server machine name from A to B. I
run the setup and change server name. The server name shows B when using
select @.servername. But, in SQL log file, there is one line still show the
old name
> Using 'SSMSRP70.DLL' version '7.0.961' to listen on 'A'.
> What's the reason for that? Thanks.
> Yuling|||Look at question 5 in the following article:
195759 INF: Frequently Asked Questions - SQL Server 7.0 - SQL Setup
Basically you have to do the following:
Open the SQL Server Network Utility. Select Multiprotocol and
click on Remove. Click Add and select Multiprotocol from the list on the
left
hand window. This should now display the correct servername. Once
Multiprotocol is added, restart the SQL Server service and this should
correct
the problem.
Rand
This posting is provided "as is" with no warranties and confers no rights.