differences b/w azure blob and azure sql

Hi,

Azure Blob is part of larger concept called Azure Storage which comprises of following four services: Blob storage, Table storage, Queue storage, and File storage. A storage account is a required for storing your unstructured data as blobs (objects) in Azure Storage.

Azure SQL Database is a cloud database. Consider a scenario where you wana copy your CRM Online data (for better reporting requirements) then you can use tools like Microsoft Data Export Services or Scribe Online replication services to create a copy of your online DB onto your Azure SQL db. This will sync DBs as per set intervals as well. Azure SQL behaves exactly like onpremise DB only difference being data is residing in cloud.

I think Igorek has addressed your SQL Azure concerns. You seem to still have questions about Tables vs Blobs, though.

In your case using Table storage would be annoying. Each property/column in ATS can be at most 64KB, so you would have to split the documents across multiple properties and then reassemble them. There is also a limit of 4MB per entity, which would be a problem. Blob storage has neither of these limitations.

I would tend to use Azure Table Storage when you have smallish entities with many properties that need to be stored and queried separately. So it works wells for stored objects, or small documents with lots of metadata.

Blob storage works better for things without a ton of metadata. It's good for things that might work well as files on a filesystem.

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Manikandan Murugesan9y ago
Hi,

Azure Blob is part of larger concept called Azure Storage which comprises of following four services: Blob storage, Table storage, Queue storage, and File storage. A storage account is a required for storing your unstructured data as blobs (objects) in Azure Storage.
Azure SQL Database is a cloud database. Consider a scenario where you wana copy your CRM Online data (for better reporting requirements) then you can use tools like Microsoft Data Export Services or Scribe Online replication services to create a copy of your online DB onto your Azure SQL db. This will sync DBs as per set intervals as well. Azure SQL behaves exactly like onpremise DB only difference being data is residing in cloud.

I think Igorek has addressed your SQL Azure concerns. You seem to still have questions about Tables vs Blobs, though.

In your case using Table storage would be annoying. Each property/column in ATS can be at most 64KB, so you would have to split the documents across multiple properties and then reassemble them. There is also a limit of 4MB per entity, which would be a problem. Blob storage has neither of these limitations.

I would tend to use Azure Table Storage when you have smallish entities with many properties that need to be stored and queried separately. So it works wells for stored objects, or small documents with lots of metadata.

Blob storage works better for things without a ton of metadata. It's good for things that might work well as files on a filesystem.

0
Gokhul Varman9y ago
If you refer the link given you can get a clear solution for your problem:https://stackoverflow.com/questions/29079268/differences-between-azure-block-blob-and-page-blob
0