SQL and IIS on AZURE interfacing with on premise SQL and IIS

We currently have a site to AZURE vpn configured and we are getting 60ms ping times thru it.  We have integrated AD to our AZURE servers.  We have an on premise SQL server and an IIS server that host applications and databases for our internal users.  (12 db's none over 3gb).  We also have a SQL server and an IIS server hosted on AZURE that our external customers access.  The web server on AZURE gets data input and dumps it in the AZURE SQL server which replicates back into our internal SQL server.  Our internal SQL server gets input from our internal users and replicates to the AZURE SQL server.  We are having all sorts of database issues and failures.  Is this a viable way for doing this?  What other options do we have.  **Note**  The AZURE servers are our external webservers for the public.  This is not my forte.  This is actually our web/sql guys issue but he is not having any luck solving it.
Brian DeBoltNetwork EngineerAsked:
Who is Participating?
Zachariah BrowningCommented:
Is your Azure SQL actually SQL running on an IaaS Server hosted in Azure or are you using the PaaS Azure SQL DB Service? You could be running into IOPS issues or DTU limits..

Most likely your issue is with your VPN setup/gateway device. not so much connection speed but high packet loss or bandwidth limitation somewhere. Some causes could be if azure is far away from your office like connecting to East Europe when you live in West Coast US. Issue with gateway setup/VPN device on premises. Multiple site-to-site vpn connections.

First i would check what the throughput is between on premises and Azure via VPN to test what your actual connection speed is. Since on the surface that sounds like the real issue. If you find that your throughput is very low then troubleshooting that network connection, gateway setup etc.- would be the main priority.

You could look into getting a ExpressRoute setup if your Internet Service Provider supports it. This would create a tunneled high security connection directly to azure for consistent and fast connection speeds. Just as one option. You might also want to upgrade your gateway to a Standard or high performance gateway if you are only using the basic gateway setup. Even a standard (or small)  dynamic routed gateway should have 100Mbps throughput, or 1000Mbps Expressroute throughput.
Zachariah BrowningCommented:
My main question is why are you double replicating instead of having only the Azure SQL DB?

~Azure does not charge for data ingress- but does charge for all data egress, so every time you do a replication to on prem you have  a small little charge associated with it. From your description you want the two servers in as close to synchronized as possible.. if you are already in a VPN situation, why not just use the azure server directly and reconfigure on premises web servers to be directed to the Azure SQL DB>?
Brian DeBoltNetwork EngineerAuthor Commented:
When we try and run an app internally that queries the AZURE SQL we get about 10 rows of data every 30 seconds.  That's why we are not just using the AZURE SQL server.
I am curious if the issue is with our site to Azure VPN or using blob storage instead of premium storage?  A ping to our AZURE server over our VPN is between 60ms and 65ms.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.