Skip to content


Making Some Noise with Azure SQL Database


[This is part Eight of  Top 10 Things You Will Hate About Azure SQL Database]


The concept of a noisy neighbor is not unique to Azure SQL Database, but in cloud computing it is the term used to describe a customer monopolizing the resources and degrading the performance for other customers. Of all the items that out of your control this one tops the list. It doesn’t mean you should rule out SQL Database, but it does need to be considered.

If you are managing resources for your on premises SQL servers and you have resource contention between applications you can monitor what is happening and devise a solution.  In the cloud someone could be running a stress test and slow down your web application and there is nothing you can do about it. OK, you could upgrade to the Premium level of SQL Database, which will guarantee some dedicated resources, but you have to pay for extra.

Microsoft does have some throttling and resource governing in place to make sure no one customer can affect things too much, but it still allows for someone to be using more than you are at a given moment.

The interesting thing about this issue is that it doesn’t just apply to SQL Database, the concept of a noisy neighbor has to be considered for all cloud solutions. The whole idea is using shared commodity resources to reduce cost of ownership, which means there will always be sharing unless you pay the extra money for dedicated servers.


From → SQL Server

Leave a Comment

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s