asked on sql server upgrade
I have a database server that is about 4 years old. we have a bunch of users that point their applications to this server.
the name of the server is Alpha
We want to upgrade the sql server version from 2012 to 2016. I think i would like to create a new server and do a clean install of sql server instead of doing an in-place upgrade.
So the new server would be bravo...... (if we do not do an in-place upgrade)
isn't it true that if i get the permissions right on bravo and restore all the databases on bravo. that i could thereotically change the name of Alpha to lets say Alpha1 and then rename Bravo to Alpha that the users would not need any configuration changes.
Can someone please verify or send me to a document that outlines the best way to do this.
the name of the server is Alpha
We want to upgrade the sql server version from 2012 to 2016. I think i would like to create a new server and do a clean install of sql server instead of doing an in-place upgrade.
So the new server would be bravo...... (if we do not do an in-place upgrade)
isn't it true that if i get the permissions right on bravo and restore all the databases on bravo. that i could thereotically change the name of Alpha to lets say Alpha1 and then rename Bravo to Alpha that the users would not need any configuration changes.
Can someone please verify or send me to a document that outlines the best way to do this.
DatabasesMicrosoft SQL ServerMicrosoft SQL Server 2008SQL
Last Comment
Jim Metcalf
Typically you'd want to just have the name "Alpha" route to the Bravo server using DNS or other routing. Afaik, although I am not a network person at all, the DNS name and the server name don't actually need to match. The specified name just needs to get you to the correct IP address.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Over time you should migrate to a logical name rather than a physical name anyway. For example, "ProdApp1" rather than "Bravo" or any other actual server name. Keep the physical names completely separate from the logical/app names. That allows you to, for example, move an app from one server to another and never worry about changing the apps/connections themselves.
Hi,
I assume we are discussing changing hostnames for default instances of SQL Server installed. After successfully changing hostname in Windows advanced host properties and AD you issue:
Regards,
Daniel
I assume we are discussing changing hostnames for default instances of SQL Server installed. After successfully changing hostname in Windows advanced host properties and AD you issue:
--verify you have old name
select * from sys.servers where server_id=0;
--remove old name
sp_dropserver 'old_server_name';
GO
--ad new name
sp_addserver 'new_server_name', 'local';
GO
--restart SQL Server instance
--verify you have new name
select * from sys.servers where server_id=0;
Regards,
Daniel
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Perfectomundo