September 18, 2018 at 10:29 am
Recently we did a migration of database from one server to another for an application for library called Destiny, then we swapped windows server name.
next I ran stored procedure dropserver, addServer to change the SQL server name,
Then I stoppped and restarted the SQL service.
The database runs fine. But later we found the web application was not working.
Then we have to restart the server , the application works again.
My question is in which case we need to reboot the server so that the web application can reconnect?
For most cases I found I don't need to restart the server, the web site will reconnect the database automatically.
But this case it is not. This case happened to be that the web server and database are in one server.
September 18, 2018 at 1:11 pm
sqlfriends - Tuesday, September 18, 2018 10:29 AMRecently we did a migration of database from one server to another for an application for library called Destiny, then we swapped windows server name.
next I ran stored procedure dropserver, addServer to change the SQL server name,Then I stoppped and restarted the SQL service.
The database runs fine. But later we found the web application was not working.
Then we have to restart the server , the application works again.My question is in which case we need to reboot the server so that the web application can reconnect?
For most cases I found I don't need to restart the server, the web site will reconnect the database automatically.
But this case it is not. This case happened to be that the web server and database are in one server.
Just in general, no SQL Server involved.....When you rename a server you need to restart the server. The NetBios name of the server is set at startup when it reads the name from the registry. So the old name is still cached until the restart.
Other times when you didn't have to restart the server, the server was probably already restarted after the server rename. Then you got the server and had to do the rename for SQL Server, which would only require the service restart.
Sue
September 18, 2018 at 1:18 pm
Thanks,
Yes, after they rename the Server, it has been rebooted.
Then they didnot change the SQL name until second day I found and changed the SQL server name.
After that, I did a restart of SQL service. Then the system admin of that application found the application not start up.
I asked her to reboot the server, then it works.
The application and database in this case is on the same server.
September 18, 2018 at 1:33 pm
sqlfriends - Tuesday, September 18, 2018 1:18 PMThanks,
Yes, after they rename the Server, it has been rebooted.Then they didnot change the SQL name until second day I found and changed the SQL server name.
After that, I did a restart of SQL service. Then the system admin of that application found the application not start up.I asked her to reboot the server, then it works.
The application and database in this case is on the same server.
Yeah I think it just gets confusing as there are two different things needed for the rename - one on the Windows side and one on the SQL Server side.
When it comes to SQL Server - the issues after the server rename are mostly due to the server name in sys.servers. That's what you are changing when you do the sp_dropserver, sp_addserver. So there are two different areas to do the rename - one for Windows and one for SQL Server. And a lot of times, sysadmin or windows admin won't know that a SQL Server admin has to do a rename. And SQL Server admins often don't know about the server itself needing to be rebooted as we usually get those servers passed back to us after they have already rebooted it after the rename.
Sue
September 19, 2018 at 3:41 pm
This was removed by the editor as SPAM
September 19, 2018 at 3:43 pm
This was removed by the editor as SPAM
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply