April 1, 2016 at 8:47 am
We have a VERY, VERY old SQL 2000 database (if it ain't broke....) that we are finally starting to get migrated up to new versions of SQL, and the first step had to be migrating to SQL 2005. So a temp server (sparetemp) was set up, SQL 2005 installed, the logons migrated over, databases migrated over, etc. We were planning on staying on SQL 2005 for a couple of weeks to make sure that this transition was stable, so I knew we had to rename the temporary server over to the original production server name.
My research into renaming the server told me it was possible using sp_dropserver/sp_addserver...and that maintenance plans "probably" would not work any longer . Not a big deal. So with production still up and running, we tested the rename process on another test server and discovered that the SQL system users (created at SQL install time) would not get renamed to show the new server name in the login PATH under the SECURITY\Logins.
So, how critical is it for these three logins to have the correct servername in the PATH? I have tried to rename these users and that doesn't work. I can delete them, but how do I regenerate them? If I leave them alone, does that cripple this install of SQL? User names listed below:
Note: old server was 'sparetemp' / new srvr is 'sparetemp3'
SPARETEMP\SQLServer2005MSFTEUser$SPARETEMP$MSSQLSERVER
SPARETEMP\SQLServer2005MSSQLUser$SPARETEMP$MSSQLSERVER
SPARETEMP\SQLServer2005SQLAgentUser$SPARETEMP$MSSQLSERVER
...So how do I replace the SPARETEMP values above to SPARETEMP3, the new name for the server?
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply