Hello All
I have SQL Server running on a Virtual Machine in West Europe. I would like to connect to this database from a web application hosted in a cloudservice in Southeast Asia. When I originally connected the application to the database, the latency makes the web application unusable.
To try and improve the latency I have put the cloudservice in a VNet (Southeast Asia) and the Database VM in a VNet (West Europe) and connected the two VNets following the following article: http://azure.microsoft.com/blog/2014/06/17/vnet-to-vnet-connecting-virtual-networks-in-azure-across-different-regions/
I changed the database connection of the cloudservice to the internal IP of the SQL Server. I was expecting to see a substantial improvement in latency, but there is not much difference in moving the database and cloudservice into a connected VNet.
I do not want to change the database hosting, this exercise is attempting to reduce the number of databases required.
Any suggestions on improving our latency greatly appreciated.