Home Dashboard Directory Help
Search

Renaming a SQL Server requires modifying connections for Maintenance Plans by vs2010junkie


Status: 

Closed
 as Won't Fix Help for as Won't Fix


4
0
Sign in
to vote
Type: Bug
ID: 357953
Opened: 7/26/2008 12:20:41 PM
Access Restriction: Public
1
Workaround(s)
view
0
User(s) can reproduce this bug

Description

After renaming a SQL Server, one must go in an edit all of the connections for a Maintenance Plan to coincide with the new SQL Server name. This is not handled automatically nor is there a wizard provided to edit/update all of the connections automatically after performing a server rename.
Details
Sign in to post a comment.
Posted by Microsoft on 5/22/2011 at 12:03 AM
Hi:

We took a look at this bug along with several others recently. Unfortunately, triaging it against other critical bugs, I do not think we would get to investigating this in the near future. However, we have taken note of this internally, and when we revisit this functionality in the future, we will try and get this resolved.

Thanks for writing in to Microsoft.

Cheers,

Chandramouli | Program Manager | SQL Server Manageability
Posted by Microsoft on 5/11/2010 at 4:40 AM
Thanks for your feedback. We will consider your request for future release of SQL Server.

Thanks,
Sateesh Pragallapati
Posted by moody31415 on 9/23/2008 at 1:14 PM
I think this should be done by running the sp_addserver 'name', 'local' code - shouldn't that automatically update the maintenance plans etc.?

Also, this is a big issue for us, as we like to keep the same servername when we upgrade to new hardware - but we want to minimize downtime so we try to setup everything in advance on the new machine under a different name.
Sign in to post a workaround.
Posted by Benjamin Lotter on 9/11/2009 at 6:21 AM
After renaming the SQL Server, delete and recreate the Maintenance Plans. Still looking for a solution, however.

/*
verify the incorrect server name
select @@SERVERNAME
*/
--the following commands rename the SQL Server
exec sp_dropserver 'old_servername\instance'
GO
exec sp_addserver 'new_servername\instance', 'local'
GO
--restart sql service

/*
verify the correct server name
select @@SERVERNAME
*/