I was at SQL Rally recently (10-11 may 2012) where I happened to have a nice talk about SQL Azure with a fellow attendee. They were considering porting their database (that supports one of their apps) to Microsoft’s cloud service. One of the concern they had was “How to reduce the network latency between SQL Azure and their App?” And Since I knew the solution, I shared it with that person. I am sharing it here so others can benefit too.
Now one of the first question that I asked the attendee was: Are you also porting your app along with the database to Azure?
Turns out, They were considering to host the app on Azure cloud too. So technically that’s called a “Code Near” scenario – And in this case, the application and the database both *should* reside in the same data-center. if you do so, the network latency between your app and the database is minimal.
Now, if you have your app on-premise and you are considering SQL Azure, then select the data-center location that has the minimal network latency between your app and SQL azure. Technically it’s called Code-Far scenario I have written about one of the ways you can do so, here’s the URL: Testing latency between client and SQL Azure via client statistics in SSMS
That’s about it for this post.
Official Resource: SQL Azure and Data access
- The day it all began for SQL Azure (parasdoshi.com)
- Reports hosted on SQL Azure reporting (preview) accessed via Windows Phone, iPhone and Android phones! (parasdoshi.com)
- what’s the role of a “Master” database in a SQL Azure world? (parasdoshi.com)