March 15, 2011 at 9:31 am
Hi all,
I'm working on a project that will be transferring to a new location shortly. I currently work on a SQL Server that is physically located in the same place as I am. When we move, the server doesn't.
The server is connected to the company's WAN and is currently accessed via RDP. I'll be doing the same from our new location.
I have the option to run some testing ahead of the move, but am not really sure what to test (essentially, what might go wrong?). So, I was hoping that someone might help with some advice on what I should be checking?
Thanks, Iain
March 15, 2011 at 9:38 am
Once the domain is setup on the new location, plug a pc and try to connect.
Debug if it fails.
repeat step 1 untill it works.
The server is working now. So the only thing that can screw it up is wrong setup of the network at new location.
Problem #2 could be bandwith.
March 15, 2011 at 9:39 am
I presume you would want to test connectivity to the SQL box from your remote site?
Try connecting to it using the same methodology as if you were still located there... Ensure the relevant SQL ports are open (especially if your using named instances), Test all components of SQL that might be in use SSMS, SSIS, SSRS, SSAS so on and so forth.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply