Two physcial servers with same Database name server
-
Hello, We are retiring our older server, not yet, in place going to have a new server. WE need to name the new database server as our current one. Can we have two such database servers at a given time? How can we migrate from one server to another with no lag time, since it is the production server constantly collecting data. Thank you.
-
Hello, We are retiring our older server, not yet, in place going to have a new server. WE need to name the new database server as our current one. Can we have two such database servers at a given time? How can we migrate from one server to another with no lag time, since it is the production server constantly collecting data. Thank you.
Hi,
vanikanc wrote:
WE need to name the new database server as our current one
First let's separate two totally different things: - the name of the database server is just an alias for the IP-address. So this means that you cannot have two different machines having the same name (thus the same IP-address) at the same time or you'll have enormous problems in you network - the name of the SQL Server instance (the service) is used to distinguish separate SQL Server services on the same machine. So basically your question is client-related. If you want to make the switch-over to the new (physical) server you have to be able to re-configure your clients to start using the new server. For example if your old SQL Server is ServerProduction1\Instance1 (meaning for example 10.1.123.1,1433\Instance1) you would change the client to connect to ServerProduction2\Instance1 (meaning for example 10.1.123.7,1433\Instance1). Of course the instance name can also be changed.
vanikanc wrote:
Can we have two such database servers at a given time?
So the answer from the client side point of view is no. Which one would they connect to?
vanikanc wrote:
How can we migrate from one server to another with no lag time, since it is the production server constantly collecting data
You restrict the changes to the original database during the transfer, transfer all the data from server 1 to the server 2, re-configure the clients to connect to server 2 and off you go.
The need to optimize rises from a bad design.My articles[^]