3
votes

I've designed a data access layer for a worker role, which will execute range queries and batch inserts on one Azure Table partition. This partition can potentially contains millions of row.

While this partition will only be consumed by a few workers only, with a reasonable access rate, and good performance is not a critical requirement, is there any problem doing so? Is there a limit on the size of the rowkey index?

Of course I have read Real World: Designing a Scalable Partitioning Strategy for Windows Azure Table Storage.

1
Not sure why there are votes to close this question, but this is a reasonable question to askIgorek
loool good one @nathanchere :)uzul

1 Answers

3
votes

There is no stated limit on a size of a partition that I'm aware of.

Do know that there is a limit in number of operations per partition (500/sec) and that availability of storage is at the partition level (ie: if the partition goes down, everything inside it goes down)

Obviously batch inserts will be limited to no more than 100 entities at a time