Showing posts with label rename. Show all posts
Showing posts with label rename. Show all posts

Monday, March 19, 2012

Issues Renaming Analysis Server Instance

Hi Friends

I want to rename My Analysis Services Instance installed on E: Drive. I read an article how to rename the Analysis Service Instance . Then I followed 64-bit path to rename, but it gives the following error rolling back to the original Instance Name:

Registering the new performance counters file:

LoadPerfCounterTextStrings for file C:\Program Files\Microsoft SQL Server\MSSQL.1\OLAP\bin\msmdctr.ini failed with error code 2

The System cannot find the file Specified

Has anybody came across this issue. Any workarounds ?

Thanks

Subhash Subramanyam.

Hi Subash,

I need few more info from you before I troubleshoot the issue.

1) What was the intial folder your Analysis Service resides? ex: E:\program files\mssql.1\olap\bin

2) What was the original instance name and what did you rename to?

3) Do you get this error from asinstancerename tool?

Thanks,

Deva

|||

1) What was the intial folder your Analysis Service resides? ex: E:\program files\mssql.1\olap\bin

C:\Program Files\Microsoft SQL Server\MSSQL.1\OLAP\bin

2) What was the original instance name and what did you rename to?

original instance name: ss2005

rename to: as2005

3) Do you get this error from asinstancerename tool?

Yes

Hope this helps.

Thanks

Subhash Subramanyam

Issues after server rename

We have a new SQL Server 2005 box in place and we named this server - Server2. Restored all the production databases from original Server1. Server1 is running SQL Server 2000 Enterprise Edition. Server1 also has three subscribers ServerA, ServerB, and ServerC.

After Server2 was renamed to Server1 and Server1 decommissioned, replication is not working on the new Server1 due to the renaming issue. I can afford to re do replication from ground up on Server1 but cannot reinstall SQL Server 2005 and start from scratch since the server is already in production.

How can I resolve this issue? What is the right approach to take for the scenario described above?

Its unclear to me what state the new server 1 is in now. To get this to work you should have restored the master, msdb, distirbution, and publication databases, and then the transaction logs of the publication databases, followed by the tail of the publication database restored with the keep_replication switch. These should have been restored to a SQL 2000 server, the new SQL 2000 server should br renamed Server1 and restarted. Then run the sp_replrestart command, and run with the continue on data consistency error profile until the errors are cleared.

Then upgrade your publisher to SQL 2005.

If publications exist in Server1, attempt to script them out and then drop the publications and recreate them with the script and then redeploy your subcribers.

Wednesday, March 7, 2012

Issue with Attaching database (MS SQL Server 2000)

Attach a database as MYDB_X using Enterprise manager. (File names:
MYDB_X.MDF & MYDB_X_LOG.LDF)
Detach this database,
Rename the files as MYDB_X11.MDF & MYDB_X11_LOG.LDF
Select this MDF file in Attach Database Dlg of Enterprise manager.
"Attach As" gets populated as MYDB_X (Name as last attached)
Attach DB as MYDB_X11.
Detach this database,
Rename the files as MYDB_X.MDF & MYDB_X_LOG.LDF
Select this MDF file in Attach Database Dlg of Enterprise manager.
"Attach As" gets populated as MYDB_X11 (Name as last attached)
Attach DB as MYDB_X.
Detach this database,
Select this MDF file in Attach Database Dlg of Enterprise manager,
"Attach As" gets populated as MYDB_X11
When MDF file is selected shouldnt it get populated with MYDB_X? Or how to
make sql server remember the last "Attach As"'
It seems that, "Database Name" property doesnt get updated everytime in Db
attach process... If database name length is more then only its updating.
DhirenHi
I think this is a known issue http://tinyurl.com/jk8fr, the workaround would
be to use sp_renamedb and attach it as the original name. If you are
attaching using sp_attach_db then it would not be an issue.
John
"Tinu" wrote:
> Attach a database as MYDB_X using Enterprise manager. (File names:
> MYDB_X.MDF & MYDB_X_LOG.LDF)
> Detach this database,
> Rename the files as MYDB_X11.MDF & MYDB_X11_LOG.LDF
> Select this MDF file in Attach Database Dlg of Enterprise manager.
> "Attach As" gets populated as MYDB_X (Name as last attached)
> Attach DB as MYDB_X11.
> Detach this database,
> Rename the files as MYDB_X.MDF & MYDB_X_LOG.LDF
> Select this MDF file in Attach Database Dlg of Enterprise manager.
> "Attach As" gets populated as MYDB_X11 (Name as last attached)
> Attach DB as MYDB_X.
> Detach this database,
> Select this MDF file in Attach Database Dlg of Enterprise manager,
> "Attach As" gets populated as MYDB_X11
> When MDF file is selected shouldnt it get populated with MYDB_X? Or how to
> make sql server remember the last "Attach As"'
> It seems that, "Database Name" property doesnt get updated everytime in Db
> attach process... If database name length is more then only its updating.
> Dhiren
>
>

Issue with Attaching database (MS SQL Server 2000)

Attach a database as MYDB_X using Enterprise manager. (File names:
MYDB_X.MDF & MYDB_X_LOG.LDF)
Detach this database,
Rename the files as MYDB_X11.MDF & MYDB_X11_LOG.LDF
Select this MDF file in Attach Database Dlg of Enterprise manager.
"Attach As" gets populated as MYDB_X (Name as last attached)
Attach DB as MYDB_X11.
Detach this database,
Rename the files as MYDB_X.MDF & MYDB_X_LOG.LDF
Select this MDF file in Attach Database Dlg of Enterprise manager.
"Attach As" gets populated as MYDB_X11 (Name as last attached)
Attach DB as MYDB_X.
Detach this database,
Select this MDF file in Attach Database Dlg of Enterprise manager,
"Attach As" gets populated as MYDB_X11
When MDF file is selected shouldnt it get populated with MYDB_X? Or how to
make sql server remember the last "Attach As"'
It seems that, "Database Name" property doesnt get updated everytime in Db
attach process... If database name length is more then only its updating.
DhirenHi
I think this is a known issue http://tinyurl.com/jk8fr, the workaround would
be to use sp_renamedb and attach it as the original name. If you are
attaching using sp_attach_db then it would not be an issue.
John
"Tinu" wrote:

> Attach a database as MYDB_X using Enterprise manager. (File names:
> MYDB_X.MDF & MYDB_X_LOG.LDF)
> Detach this database,
> Rename the files as MYDB_X11.MDF & MYDB_X11_LOG.LDF
> Select this MDF file in Attach Database Dlg of Enterprise manager.
> "Attach As" gets populated as MYDB_X (Name as last attached)
> Attach DB as MYDB_X11.
> Detach this database,
> Rename the files as MYDB_X.MDF & MYDB_X_LOG.LDF
> Select this MDF file in Attach Database Dlg of Enterprise manager.
> "Attach As" gets populated as MYDB_X11 (Name as last attached)
> Attach DB as MYDB_X.
> Detach this database,
> Select this MDF file in Attach Database Dlg of Enterprise manager,
> "Attach As" gets populated as MYDB_X11
> When MDF file is selected shouldnt it get populated with MYDB_X? Or how to
> make sql server remember the last "Attach As"'
> It seems that, "Database Name" property doesnt get updated everytime in Db
> attach process... If database name length is more then only its updating.
> Dhiren
>
>