Sep 10 2020 08:20 AM
I’m looking to migrate away from our on prem DC and separate SQL server into Azure.
My plan is to join our Windows 10 clients to our existing Azure domain (AAD), continue to use Exchange online for email and move files and folders to OneDrive.
All of the above I’m happy with so far. The bit I’m unsure about is our SQL databases which our client software uses. I know I can create a SQL instance in Azure and potentially migrate our data across to it but am concerned about latency between the client app and the azure sql instance. We have a 100mb/100mb leased line as our internet link.
any advice on this please
Sep 22 2020 08:36 PM
Have you tested the app for its latency sensitivity?
If you know the thresholds, then potentially review where you host SQL. You can test the latency from your office to the location here
https://www.azurespeed.com/Azure/Latency
Sep 23 2020 11:39 AM
Hi @Ljs007 ,
You will need to do some latency testing to see how the connection will be. And if you want to have low latency you might consider using Azure ExpressRoute. Pleas check:
Dec 24 2020 03:10 AM
Jan 03 2021 11:19 AM - edited Jan 03 2021 11:20 AM
Hi why don't you migrate the client as well ?
I mean you can replicate both and test before failover .
You can have some inputs about the latency here https://www.azurespeed.com/Azure/Latency
In my opinion you should leave or migrate both .