June 28, 2011 at 12:39 pm
We migrated servers. On the servers we have Packet Trap (network monitoring software, and SQL 2005 Enterprise)
So we had server 192.168.1.34, backed up the SQL data, restored it to our new server, 192.168.1.35.
Now 192.168.1.35 is running, .34 is not.
Problem is one client needs to look at SQL 192.168.1.34, but it's not there .35 is.
How can I make the SQL database currently .35 --> .34?
I just want to change the IP without locking myself out, or corrupting something.
June 28, 2011 at 12:55 pm
The IP doesn't matter. SQL tends to work by name, and that's what's important. SQL Server tends to listen on all IPs that the server has configured.
That gets translated to an IP, and you can use an IP. What you can also do is add a second IP to the server in the Windows networking.
June 28, 2011 at 3:07 pm
thank you.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply