asked
Server move from one network to another!!!!!!
Hi, We are using **Windows Server 2003**,**MS SQL SERVER 2005** Our Server move from one network IP to another network IP. 1. How will i check the connectivity working or not between two server i.e old network server to newly moved network server? give the procedures or step by step approach 2. Are They linked servers and SQL jobs and replication jobs affected or not? How to handle and what are procedures to take care after Server move?
Are you relocating a server? Or creating a new copy of the server? 1. If it's a relocation job, and the server is physically moving / being readdressed, then there's no problem - if client sstill connect using their existing connection strings, you'll be able to see the traffic on the server. If they don't, then you'll need to make sure that nothing else has gone wrong. 2. Linked servers - again, if it's a server move (physical relocation), then there should be nothing to worry about - assuming that the firewall paths are all good. If you're doing a side-by-side, ie going from one server to another, the easiest thing to do is turn off the original server (or at least disable the SQL Server services) and see what still works / what's broken. Much better (in my mind) to do a side-by-side upgrade, ie transfer just the data across from one to another - that way, you've got a much faster fallback should things go wrong.
As long as you are not using the IP addres of the server hard coded in any DTS, SSIS, SPROCs, or linked server you should be fine as long as DNS is updated. If the servers are securied internally behind a firewall that requires rules for internal servers to communciate with each other then you would need your firewall person to create the additional rule sets. Outside of DNS and firewall issues, an IP address change is pretty much a non event for a database server.
-----------To Test linked server connectivity----------- select * from sys.servers exec sp_linkedservers exec sp_testlinkedserver SQLDC sp_tables_ex seddev declare @srvr nvarchar(128), @retval int; set @srvr = 'seddev'; begin try exec @retval = sys.sp_testlinkedserver @srvr; end try begin catch set @retval = sign(@@error); end catch; if @retval <> 0 raiserror('Unable to connect to server. This operation will be tried later!', 16, 2 ); Is it correct???
+1 Nice answer tim radney
![alt text][1] [1]: /storage/temp/643-linked+server+connectivity+checks.jpg Is it useful or correct way of checking linked server connection?
13 People are following this question.
