I'm just starting to learn Azure and I can't see too many scenarios where you would want to put something into an Azure storage table as opposed to SQL. I guess maybe I'm used to working in environments where I need related data?
When is it better to put something into an Azure storage table and not in a table in a Azure SQL database?
Azure SQL Database offers Database-as-a-service (DBaaS-PaaS). With SQL Database, you don't have access to the machines that host your databases. In contrast, Azure Virtual Machine offers Infrastructure-as-a-service (IaaS).
Azure Table storage is a database you can use to store NoSQL data in Azure. It enables you to store structured, schemaless data using a key/attribute design. You can also use it for structured, non-relational data.
Azure Cosmos DB can be classified as a tool in the "NoSQL Database as a Service" category, while Azure Storage is grouped under "Cloud Storage". Some of the features offered by Azure Cosmos DB are: Fully managed with 99.99% Availability SLA. Elastically and highly scalable (both throughput and storage)
Azure Table storage is a service that stores non-relational structured data (also known as structured NoSQL data) in the cloud, providing a key/attribute store with a schemaless design. Because Table storage is schemaless, it's easy to adapt your data as the needs of your application evolve.
SQL Azure is great when you want to work with structured data using relations, indexes, constraints, etc.
Azure storage table is great when you need to work with centralized structured data without relations and usually with large volumes.
The Price: SQL Azure: $25.98/mo for 5GB
Storage table: $21.88/m for 175 GB (without transactions or bandwidth) So when you store large volumes of data, storage table is a lot cheaper... think of logging for example.
The centralization: Windows Azure is a distributed environment for servers so if you save something on one machine, others won't know about it, therefore storage table is a good solution for centralized loggins, session handling, settings or whatever (keep on mind that there is latency even in one datacenter)
The speed: If you design it right, in many cases storage table should be faster than sql azure but it probably depends on use cases and I haven't really tested this.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With