问题
When the SPLIT AT command is issued, the database is split into 2 new federated members. Will these 2 members sit on the same server? will they have the same amount of I/O, CPU resources? If the application will have to grow to 50 members, is there anything else needed aside from SPLIT AT command to scale out? Will these 50 members be split across multiple servers? Is there a separate SQL Azure Server account needed for this operation?
What are the quantifiable limits when the Resource Throttling kicks in with the SQL Azure?
回答1:
One correction to David's note: all federation members are distributed to the sql azure cluster so members don't reside on the same physical server. Federation member are regular databases in the system and they are distributed the same way all dbs in the env behave in placement. All dbs including members are placed in the cluster through the sql azure load balancing engine by looking at their resource utilization. I talk about this here.
回答2:
Yes, each federation is on the same database server, just separate databases.
Specifics around throttling are now in the SQL Azure Wiki, with a recent MSDN blog post talking about the various wiki updates here.
来源：https://stackoverflow.com/questions/10901462/sql-azure-split-at-backend-process-and-resource-throttling