Scribd
Upload
22 views1 page

Azure Book 106

Uploaded by

jayantascribe
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
22 views1 page

Azure Book 106

Uploaded by

jayantascribe
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

 93

Common uses of Table storage include:


●● Storing TBs of structured data capable of serving web scale applications. For example, you can store
any number of entities in a table, and a storage account may contain any number of tables, up to the
capacity limit of the storage account.
●● Storing datasets that don't require complex joins, foreign keys, or stored procedures. Example data-
sets include web applications, address books, device information.
●● Quickly querying data using a clustered index55. Access to Table storage data is fast and cost-effec-
tive for many types of applications. Table storage is typically lower in cost than traditional SQL for
similar volumes of data.
Azure Cosmos DB provides the Table API for applications that are written for Azure Table storage and that
need premium capabilities like high availability, scalability, and dedicated throughput.
There are some differences in behavior between Azure Storage tables and Azure Cosmos DB tables to
remember if you are considering a migration. For example:
●● You are charged for the capacity of an Azure Cosmos DB table as soon as it is created, even if that
capacity isn't used. This charging structure is because Azure Cosmos DB uses a reserved-capacity
model to ensure that clients can read data within 10 ms. In Azure Storage tables, you are only charged
for used capacity, but read access is only guaranteed within 10 seconds.
●● Query results from Azure Cosmos DB are not sorted in order of partition key and row key as they are
from Storage tables.
●● Row keys in Azure Cosmos DB are limited to 255 bytes.
●● Batch operations are limited to 2 MBs.
●● Cross-Origin Resource Sharing (CORS) is supported by Azure Cosmos DB.
●● Table names are case-sensitive in Azure Cosmos DB. They are not case-sensitive in Storage tables.
While these differences are small, you should take care to review your apps to ensure that a migration
does not cause unexpected problems.

Other benefits to moving to Cosmos DB


Applications written for Azure Table storage can migrate to the Cosmos DB Table API with few code
changes. Azure Cosmos DB Table API and Azure Table storage share the same table data model and
expose the same create, delete, update, and query operations through their SDKs.

55 https://docs.microsoft.com/sql/relational-databases/indexes/clustered-and-nonclustered-indexes-described

You might also like