How to validate health of network connecting between servers located in office and those on cloud

We are having performance issues regarding data replicating between a DB server located on our local server and another on the cloud.

I want to check that the network between the nodes if functioning as expected over the  2mb dedicated pipe we have.  I need some guidance on tools to use and how to interpret results to assess the health and performance of the network.

I've started and included trace routes done from both servers shown below.  Perhaps these are enough though I'm uncertain if the times are what I should be expecting.

From Local to Cloud:

Local server
From Cloud to Local:

Cloud server
canuckconsultingAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
rharland2009Connect With a Mentor Commented:
Not SQL-specific, but you can set up a Performance Monitor counter for bytes transferred. It's not perfect, but will give you some picture of the data flowing out of your local box.

http://www.sqlshack.com/sql-server-network-performance-metrics-important-metrics/
0
 
rharland2009Commented:
2mb pipe isn't exactly huge. What is the physical distance in miles between your premise and your cloud location?
0
 
canuckconsultingAuthor Commented:
The office is based in Florida and I believe the cloud location is in Maryland so say 1000 miles roughly.
0
Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

 
rharland2009Commented:
Okay. Given the distance and the assumption that the connection right now is not under excessive load, then 45msec isn't out of the realm of ordinary latency.
It might be interesting to perform these same tests while attempting replication.
What is the size of the DB/dataset you're attempting to replicate across this pipe?
0
 
canuckconsultingAuthor Commented:
I'll do another test when replication kicks off tomorrow morning and post the results.

The size of the entire db (mdf file) is just under 2GB.
0
 
rharland2009Connect With a Mentor Commented:
Okay. Are you doing change-only replication, or is this a full replication of that 2GB dataset?
Moving 2GB across that link - given no other load and perfect conditions - will still take between 2 and 3 hours.
And of course, conditions are not usually perfect!
0
 
canuckconsultingAuthor Commented:
I'm doing snapshot replications.  The reason for this is every morning this the source database on local is completely refreshed from a non-sql data source.  I then take a snapshot which replicates over to the cloud.  Since all the tables on the local db are truncated I thought snapshot was the way  to go.  Does this approach make sense to you?
0
 
rharland2009Commented:
It's probably the safest way to make sure you have a complete dataset in the cloud post-replication, yeah. Bandwidth limitations are always a challenge.
Just to verify, when you say 'performance issues', do you mean the replication takes a long time, or fails, or speed to the net stinks during replication?
0
 
canuckconsultingAuthor Commented:
It seems to slow at points.  When I look in Replication Monitor it sometimes waits for some time on "Waiting for System response". I was wondering if that might have been caused by network faults or some other related limitation.

I guess what I need to do is work out exactly how much data is transferred (not just look at the size of the mdf) and how long it takes.  I can then compare actual mb/sec and compare that to the ideal.  Is there a way to do that?  I can tell from Replication Monitor how long it took but I'm not sure how to work out how many mb were transferred.
0
 
canuckconsultingAuthor Commented:
Thank you!
0
 
rharland2009Commented:
It's a pleasure to help.
0
All Courses

From novice to tech pro — start learning today.