When I present on Windows Azure SQL Database, one of the biggest concerns comes up around throttling. Just the concept that your queries might be shut down because they use too many resources tends to freak people out. I’m not sure why. I think we ought to have the same facility in the on-premises product. But, Microsoft recognizes that this is a concern and that people need better information. A new set of documentation around this topic was recently posted. Read Resource Management in Windows Azure SQL Database to get a great overview of how the throttling works and how to detect it. There is more and more information coming out on this all the time. I learned quite a few things from this documentation. Remember, the most important thing you can do for your WASD applications is implement a robust retry logic within the code.
I have twenty+ years experience in IT. That time was spent in technical support, development and database administration. I work forRed Gate Software as a Product Evangelist. I write articles for publication at SQL Server Central, Simple-Talk, PASS Book Reviews and SQL Server Standard. I have published two books, ”Understanding SQL Server Execution Plans” and “SQL Server 2008 Query Performance Tuning Distilled.” I’m one of the founding officers of the Southern New England SQL Server Users Group and its current president. I also work on part-time, short-term, off-site consulting contracts. In 2009 and 2010 I was awarded as a Microsoft SQL Server MVP. In the past I’ve been called rough, intimidating and scary. To which I usually reply, “Good.” You can contact me through grant -at- scarydba dot kom (unobfuscate as necessary).