Closed masashi-MSFT closed 5 years ago
@masashioms Thanks for the question and we will get back to you regarding the same.
@masashioms The following document answers your question: https://docs.microsoft.com/en-us/azure/sql-database/sql-database-service-tier-hyperscale#hyperscale-pricing-model
It says "We create a primary replica and one read-only replica per Hyperscale database by default. Users may adjust the total number of replicas including the primary from 1-5."
Hope this information helps. Please get back to us if you need any further information.
@NavtejSaini-MSFT Thanks, but as the number of secondaries is a configurable option between 0 to 4, I think that it should not be a fixed number.
@masashioms We are assigning this to author for further clarity. @stevestein Please confirm regarding the following questions a) What exactly is Primary Replica, is it replica of Primary DB or the Primary DB itself b) If the Secondary replicas can be configured to 0 as well, the 2 replica by default statement in the document is not true. See screen shots.
@Kevin-Farlee - Can you take a look at this one? Thanks!
@Kevin-Farlee Please let us know if you need any further information regarding this issue for resolution.
@masashioms - thanks for raising this issue.
To clarify, the replicas are secondary replicas, and you can have 0-4. The doc should be updated within the next few days.
Thanks!
Replica is an ambiguous/generic term, and means any replica whether primary or secondary. Primary Replica is the single copy of the database which is read/write active. If there is only one replica, it's a Primary. Secondary Replica means any replicas in addition to the Primary, which are in this case read-only.
So, my preference is when documenting the Portal configuration screen, where it's referring to secondary replicas, and the range is 0-4, it should be labeled as "Secondary Replicas". If you're referring to the total of all replicas, it should be labeled as "All Replicas".
@masashioms Hope the information from @kfarlee has helped. And @stevestein will update the document is sometime as well.
@stevestein Do we have a PR number for this change that we can get updates from. Please share.
@NavtejSaini-MSFT Resolved in this PR: https://github.com/MicrosoftDocs/azure-docs-pr/pull/86250 Related public PR: https://github.com/MicrosoftDocs/azure-docs/pull/36584
@masashioms The Document has been updated. We are going ahead and closing this thread.
The documentation says HS has two replicas. Does this mean we have at least one secondary replica for compute node internally even if we don't configure any secondary replicas on the Azure portal?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.