The Azure Table service supports a simple two-level hierarchy. There is a single level of tables, each of which contains zero or more entities. An entity can have up to 255 properties, including three system-defined properties, and there is no requirement that different entities in the same table have the same properties. This feature makes the Table service schemaless. The only requirement of entities in a table is that the combination of
RowKey properties is distinct for each entity in a table. Consequently, when a table is created, the only required information is its name.
The Azure Storage library contains a
CloudTableClient class that provides a set of synchronous and asynchronous methods that support the ...