January 17, 2023 at 6:35 pm
We are planning to change the server IP of normal SQL Server instance, not a cluster. My understanding is this change should be a transparent change. Restarting the sql server is what needs to be done after the IP change. Let me know if I am missing anything?
January 17, 2023 at 7:13 pm
Nope, this should be it. Clients that connect by IP will have issues, but the server will start listening on the new IPs when it starts.
Might check that the configuration manager isn't specifically set up to point to an IP as opposed to any IPv4 or any IPv6.
January 17, 2023 at 7:20 pm
Thanks Steve. Do the network team has to open up firewalls to listen the TCP port to the new IP address?
January 17, 2023 at 7:42 pm
They may. That is basic networking stuff. Clients need to be able to send a packet on whatever port you have the server listening on, plus the browser if you use that service.
January 17, 2023 at 8:14 pm
You can track the sessions and look for IPs, but you can't be sure of where clients connect from, given proxies and firewalls. Not always easy to ensure what is connecting.
January 17, 2023 at 8:31 pm
On a different note, we are doing firmware upgrade on Always on AG group but this upgrade is pushed all at once to both UAT and Prod. I was hoping to suspend the data movement until the upgrade is done. Do you think of anything this should be done differently or cause any issues or better approach?
January 17, 2023 at 8:57 pm
Best to start a separate thread for this, so people can find the answer.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply