SQL Azure SPLIT AT后端流程和资源限制 [英] SQL Azure SPLIT AT Backend Process and Resource Throttling

问题描述

发出SPLIT AT命令时，数据库被拆分为2个新的联合成员.这两个成员会坐在同一台服务器上吗?它们将具有相同数量的I/O，CPU资源吗?如果应用程序必须增加到50个成员，那么除了SPLIT AT命令之外，还有其他需要扩展的内容吗?这50名成员会分散在多台服务器上吗?此操作是否需要一个单独的SQL Azure Server帐户?

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?

当使用SQL Azure进行资源限制时，可量化的限制是多少?

What are the quantifiable limits when the Resource Throttling kicks in with the SQL Azure?

推荐答案

对David注释的更正:所有联合身份验证成员均分发到sql azure群集，因此成员不在同一物理服务器上 >.联盟成员是系统中的常规数据库，它们的分布方式与环境中所有数据库的放置方式相同.通过查看数据库的所有资源，包括成员在内的所有数据库都通过sql azure负载平衡引擎放置在群集中.我在此处谈论它.

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.

这篇关于SQL Azure SPLIT AT后端流程和资源限制的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！