provision-hyperscale
Puts a real workload on the Hyperscale service tier of Azure SQL Database: when to choose it, how to size it, and how to convert an existing database without walking through a door that does not open again. Use when a user asks "should I use Hyperscale", "convert my database to Hyperscale", "we are close to the 4 TB ceiling", "how many vCores for Hyperscale", "Hyperscale serverless or provisioned", "add a read replica", "elastic pool for Hyperscale", or "can I go back from Hyperscale". Also use when a free offer database has to become a real one, because the free limit must be turned off before the tier can change and that step cannot be undone. Covers the eligibility rules for reverse migration, controlling the cutover, replica-based read scale-out, and what actually limits write throughput. Creating the server, the database and the firewall rule belongs to provision-azure-sql-db.
Pinned to revision eeb1c6867c2d, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/provision-hyperscale/SKILL.md
- skills/provision-hyperscale/references/exit-paths-and-eligibility.md
Every link opens the file at its source, pinned to the revision this page describes.