On the surface, a SQL Server system rename may appear simple. You rename the underlying Windows box and SQL will automatically use the new name.
While that is true for many features in SQL server, there are quite a few items that need help migrating to a new server name. Fortunately many dependencies can be resolved by following instructions provided by Microsoft to update the @@SERVERNAME.
- Rename a Computer that Hosts … SQL Server 2005 (msdn.microsoft.com)
- Use the “Other Versions” drop-down to select your version of SQL Server
Note that Maintenance Plans are one of the most difficult items to fix. The default “local server” connections will still be hard-coded to point to the old server name. A script is provided in the user comments section of the above Microsoft article to fix these hard-coded “local server” connections. Please make sure that you use the script posted to the article for *your version of SQL Server*. These maintenance plan packages are in different system database locations depending on your SQL Server release.
Good luck with your SQL Server rename troubleshooting! You may also find the following Stack Exchange posts useful.
- Change or update local server connection in Maintenance plan job (dba.stackexchange.com)
- Renamed a SQL Server, however maintenance plans still have old name (serverfault.com)