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.