2

I am very new to MS SQL Server Administration and wants to learn on Migration of SQL Server in detail. We are in a Datacenter migration Project where the Windows server (SQL Server is residing in it) is going to be migrated AS-IS from Source to Destination. I would like to know what are the things that we need to take care for the SQL Server IP address connectivity issues and other related connectivity problems. correct me if anything wrong in framing the question and thanks in advance

asked Dec 13, 2015 at 11:15
0

1 Answer 1

1

If you are just changing IP address ONLY, then there are less things to worry.

Check

  • Change the IP address and restart SQL Server.
  • If your applications are referencing IP address instead of HOST, then they need to change their web.config files to reflect the new IP address.
  • Linked servers referencing IP address needs to be changed as well.

  • If any user workstations are connecting using IP, then they need to flush DNS using ipconfig /flushdns or better just restart their workstations.

  • If the server is part of Failover cluster then follow this steps as well.

If you want to be proactive and find out the applications connecting to your sql server instance, then use this server side trace and then plan accordingly for downtime.

Note: make sure you assign a static IP address and port to sql server.

answered Dec 13, 2015 at 15:57
1
  • If the IP is registered in a DNS server, it also helps to reduce TTL to a couple minutes or X seconds a couple days before and revert it back to its original value after the IP change. Commented Dec 14, 2015 at 8:11

Your Answer

Draft saved
Draft discarded

Sign up or log in

Sign up using Google
Sign up using Email and Password

Post as a guest

Required, but never shown

Post as a guest

Required, but never shown

By clicking "Post Your Answer", you agree to our terms of service and acknowledge you have read our privacy policy.