Renaming a SQL Server requires modifying connections for Maintenance Plans - by vs2015junkie

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 357953 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 7/26/2008 12:20:41 PM
Access Restriction Public


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.
Sign in to post a comment.
Posted by Microsoft on 5/22/2011 at 12:03 AM

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.


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.

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.