Are you sure SQL Azure Federations are about performance? I believe they are more about scale.
Horizontal distributed partitioning in an on-site implementation can be said to have a performance benefit due to the assumption that the additional hardware will be dedicated to the task at hand. It must be in order to overcome the network hit required to resolve queries where data lives on more than one partition.
But I don't think the same assumptions apply to SQL Azure. You simply have no assurance that each shard will run on dedicated hardware. Quite the opposite, you should assume it's all running on shared servers.
I've asked a number of people if there would be a benefit to doing this:
100 GB of data
Even key distribution
Option 1: One Azure instance holding 100 GB of data (50GB unused space available for growth)
Option 2: Five Azure instances holding 20 GB of data each, Federated into a single 100 GB database
I've been told by multiple people that Option 1 will perform better.
Have you tested SQL Azure Federations for performance? I have not yet had the opportunity.
commented on May 7 2012 4:45AM