SQL Azure SPLIT AT Backend Process and Resource Throttling -
when split @ command issued, database split 2 new federated members. these 2 members sit on same server? have same amount of i/o, cpu resources? if application have grow 50 members, there else needed aside split @ command scale out? these 50 members split across multiple servers? there separate sql azure server account needed operation?
what quantifiable limits when resource throttling kicks in sql azure?
one correction david's note: federation members distributed sql azure cluster members don't reside on same physical server. federation member regular databases in system , distributed same way dbs in env behave in placement. dbs including members placed in cluster through sql azure load balancing engine looking @ resource utilization. talk here.
Comments
Post a Comment