Table Storage versus database tables

For developers used to working with a relational database, Table Storage may seem like a step backwards. After further examination, we may begin to see Table Storage as a very powerful and flexible technology. Table Storage is not a relational mechanism, but simple relations can be maintained in application code. For developers interested in an object-based database, Table Storage may be closer to what is desired.

Tables in databases and Table Storage both have table names. Tables in Table Storage are composed of entities, which are similar to rows in a database table. Each entity has:

• A PartitionKey that is used to group entities onto the same partition

• A RowKey that uniquely identifies a row within a partition

• A system-maintained Timestamp

• Properties that are similar to columns in a database table

Properties are stored and retrieved as <name,value> pairs. The PartitionKey has a very important use. As the Azure Fabric optimizes itself, tables will be...