title: Getting started with Azure storage: Blobs vs Tables vs SQL Azure
body: <p>It's quite a topic, <em>blobs vs tables vs SQL</em>, and despite all I read so far I still can't find some proper reasoning on what to use when.</p>
  
  <p>We have a multi-tenant SaaS web-application which we are about to move to Azure. We use an SQL Server 2008 database. We store documents and log information that belongs to the documents. Kinda like dropbox does. </p>
  
  <p>The forums state that you better use Azure Tables when you are considering "large" objects. We typically store hundreds of documents per user where the size of the documents vary from 5kb to 30mb where the vast majority will be around 1MB? </p>
  
  <p>Are there some ground rules when to go for Blobs, Tables, Sql? I already learned that I shouldn't store my documents in SQL since it is too expensive. But when does it get "beneficial" to store the documents in Blobs and when would I be better of with tables? Is there some kind of formula like :</p>
  
  <p><code>if (objects * MB/object * objectrequested &gt; y) then blobs, else tables</code></p>