Updating shortcuts - dating a man with teenagers
So far, this looks very similar to a table in a relational database with the key differences being the mandatory columns, and the ability to store multiple entity types in the same table.
A solution could consist of just a single table that contains all your entities organized into partitions, but typically a solution will have multiple tables.Many of your design differences will reflect the fact that the Table service is designed to support cloud-scale applications that can contain billions of entities (rows in relational database terminology) of data or for datasets that must support very high transaction volumes: therefore, you need to think differently about how you store your data and understand how the Table service works.A well designed No SQL data store can enable your solution to scale much further (and at a lower cost) than a solution that uses a relational database. This section highlights some of the key features of the Table service that are especially relevant to designing for performance and scalability.Note The Table service REST API operations also return an ETag value that it derives from the last-modified timestamp (LMT).In this document we will use the terms ETag and LMT interchangeably because they refer to the same underlying data.Tables help you to logically organize your entities, help you manage access to the data using access control lists, and you can drop an entire table using a single storage operation.
The account name, table name and Partition Key together identify the partition within the storage service where the table service stores the entity.
Every entity stored in a table must have a unique combination of Partition Key and Row Key.
As with keys in a relational database table, the Partition Key and Row Key values are indexed to create a clustered index that enables fast look-ups; however, the Table service does not create any secondary indexes so these are the only two indexed properties (some of the patterns described later show how you can work around this apparent limitation).
For more information about the table service such as supported data types, supported date ranges, naming rules, and size constraints, see Understanding the Table Service Data Model.
As you will see, your choice of Partition Key and Row Key is fundamental to good table design.
Tip The content in this article applies to the original Azure Table storage.