SQL Server Home
Renaming a SQL Server requires modifying connections for Maintenance Plans
as Won't Fix
7/26/2008 12:20:41 PM
User(s) can reproduce this bug
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.
SQL Server 2005 SP2 - Standard Edition
Win2003 Standard Server (SP2)
Operating System Language
Steps to Reproduce
1. Install SQL 2005 SP2
2. Create one or more maintenance plans using the Maintenance Plan Wizard and save the maintenance plans
3. Rename the host server on which SQL Server is installed
4. Re-boot the computer to allow the name change to take effect
5. Run the appropriate SQL statement on the server to ensure that SELECT @@SERVERNAME displays correctly. (Usually requires stopping and starting SQL Server service)
6. Attempt to delete any of the existing maintenance plans
7. Notice that you are unable to delete any of the existing maintenance plans or jobs
8. Instead, you must manually edit the connections for each of the maintenance plan steps that were created through the Maintenance Plan wizard to ensure that the connections are up-to-date otherwise the Maintenance Plan will not run.
Requires manual editing of the maintenance plan connections to update the server connections after a host server rename.
Should provide a SQL Server "Rename wizard" which allows all existing maintenance plans,jobs etc. to be updated with the appropriate connection information simultaneously rather than requiring manual editing and running of SQL Scripts for a host server rename.
to post a comment.
Please enter a comment.
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
on 5/11/2010 at 4:40 AM
Thanks for your feedback. We will consider your request for future release of SQL Server.
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.
to post a workaround.
Please enter a workaround.
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
--the following commands rename the SQL Server
exec sp_dropserver 'old_servername\instance'
exec sp_addserver 'new_servername\instance', 'local'
--restart sql service
verify the correct server name
© 2013 Microsoft