Menu
What would be best practices for choosing partition/row keys for entities in Azure Tables? The common advice is to magically balance between partition size and number of partitions. But no one seems to have a good definition of how it can be accomplished in 3 easy steps. Is there a general approach for choosing keys so that everything then just works?
364
A. They should always be unique, like a primary key in a SQL table.
The partition key is a unique identifier for the partition within a given table, specified by the PartitionKey property. The partition key forms the first part of an entity's primary key. The partition key may be a string value up to 1 KiB in size.
The primary key for an Azure entity consists of the combined PartitionKey and RowKey properties. The two properties form a single clustered index within the table.
What are the elements of an Azure Table storage key? Table name and column name Partition key and row key O Row number 2. When should you use a block blob, and when should you use a page blob? Use a block blob for unstructured data that requires random access to perform reads and writes.
There is a detailed article on this very subject up on MSDN: Designing a scalable partitioning strategy for Windows Azure Storage.
109
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
