Hosted SQL advice please

%3CLINGO-SUB%20id%3D%22lingo-sub-1653468%22%20slang%3D%22en-US%22%3EHosted%20SQL%20advice%20please%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1653468%22%20slang%3D%22en-US%22%3E%3CP%3EI%E2%80%99m%20looking%20to%20migrate%20away%20from%20our%20on%20prem%20DC%20and%20separate%20SQL%20server%20into%20Azure.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20plan%20is%20to%20join%20our%20Windows%2010%20clients%20to%20our%20existing%20Azure%20domain%20(AAD)%2C%20continue%20to%20use%20Exchange%20online%20for%20email%20and%20move%20files%20and%20folders%20to%20OneDrive.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAll%20of%20the%20above%20I%E2%80%99m%20happy%20with%20so%20far.%20%26nbsp%3BThe%20bit%20I%E2%80%99m%20unsure%20about%20is%20our%20SQL%20databases%20which%20our%20client%20software%20uses.%20I%20know%20I%20can%20create%20a%20SQL%20instance%20in%20Azure%20and%20potentially%20migrate%20our%20data%20across%20to%20it%20but%20am%20concerned%20about%20latency%20between%20the%20client%20app%20and%20the%20azure%20sql%20instance.%20We%20have%20a%20100mb%2F100mb%20leased%20line%20as%20our%20internet%20link.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eany%20advice%20on%20this%20please%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1653468%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAZURE%20SQL%20data%20base%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESQL%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1700637%22%20slang%3D%22en-US%22%3ERe%3A%20Hosted%20SQL%20advice%20please%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1700637%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F789073%22%20target%3D%22_blank%22%3E%40Ljs007%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20you%20tested%20the%20app%20for%20its%20latency%20sensitivity%3F%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20know%20the%20thresholds%2C%20then%20potentially%20review%20where%20you%20host%20SQL.%20You%20can%20test%20the%20latency%20from%20your%20office%20to%20the%20location%20here%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.azurespeed.com%2FAzure%2FLatency%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.azurespeed.com%2FAzure%2FLatency%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1704362%22%20slang%3D%22en-US%22%3ERe%3A%20Hosted%20SQL%20advice%20please%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1704362%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F789073%22%20target%3D%22_blank%22%3E%40Ljs007%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20will%20need%20to%20do%20some%20latency%20testing%20to%20see%20how%20the%20connection%20will%20be.%20And%20if%20you%20want%20to%20have%20low%20latency%20you%20might%20consider%20using%20Azure%20ExpressRoute.%20Pleas%20check%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fservices%2Fexpressroute%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fservices%2Fexpressroute%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

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

4 Replies

@Ljs007 

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 

 

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:

 

https://azure.microsoft.com/en-us/services/expressroute/

Consider the size of your DB, if it's small, you can set up a replica to the Azure SQL.

But if the size if big, then it's better to backup your on prem DB and upload it to Azure then restore it to Azure SQL.
Then setup a replication between on prem DB and Azure SQL. Once they both are lined up. Disconnect the on prem DB and direct users to use the Azure SQL DB instead. This shift needs to be done in a pre defined maintenance window to avoid any business disruption

Hope this helps!

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 .