Performance of database partitioned across multiple Azure Data Disks -

Performance of database partitioned across multiple Azure Data Disks -

would partitioning sql server database across separate page blobs (azure info disks) have performance impact when querying partition 1 if partition 2 under heavy load?

i understand page blobs aren't necessary separate physical disks, i'm wondering performance.

context edit: want partition old (archive) info away live info (so on 3 months old) cut down database , index size. archive info must still queryable.

this "it depends" reply , take testing on part.

the 2012 scalability targets show blob @ 60 mb/sec while vm sizes show big instance gets 800 mb/sec - target throughput dependent on usage, may or may not able close figure , if can, you're saturating allotted bandwidth absolutely no point going further.

i'd inclined go basic configuration of each database instance getting 1 drive data, 1 drive logs. if still have headroom on network can @ partitioning farther appropriate.

alternatively, perhaps @ using data compression if issue how fast you're able retrieve info blob underlying azure drive...

azure windows-azure-storage partitioning azure-storage-tables azure-storage-blobs