zava-act1-migrate
Act 1 of the Zava Lending Hyperscale workshop — Migrate & Modernize — and the standalone, approve-each-step runbook to migrate ANY on-prem / IaaS SQL Server database to Azure SQL Database Hyperscale using the local `az datamigration` CLI. USE WHEN the user wants to run "Act 1" / "the migrate act", stand up the SQL Server 2019 source, migrate ZavaLendingDB to Hyperscale, or modernize after migrating (compatibility level 170 / intelligent query processing, rowstore → clustered columnstore, automatic index compaction); OR for any SQL Server → Hyperscale migration: verifying migration prerequisites / "make sure the pre-reqs are installed", assessing a SQL Server instance for Azure SQL readiness, finding migration blockers/issues, provisioning a Hyperscale target (the create-time-only zone-redundancy decision), creating a Database Migration Service (DMS) + Self-Hosted Integration Runtime (SHIR), migrating schema then data offline, validating row counts, running any of the scripts/ files (00-setup, 01-assess, 02-pr
Source facts
- Repository
- microsoft/azuresqlfoundations
- Last source activity
- August 4, 2026 at 17:40
- Detected SKILL.md language
- English
- Stars
- 2
- Forks
- 1
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Showing SKILL.md
| name | zava-act1-migrate |
|---|---|
| description | Act 1 of the Zava Lending Hyperscale workshop — Migrate & Modernize — and the standalone, approve-each-step runbook to migrate ANY on-prem / IaaS SQL Server database to Azure SQL Database Hyperscale using the local `az datamigration` CLI. USE WHEN the user wants to run "Act 1" / "the migrate act", stand up the SQL Server 2019 source, migrate ZavaLendingDB to Hyperscale, or modernize after migrating (compatibility level 170 / intelligent query processing, rowstore → clustered columnstore, automatic index compaction); OR for any SQL Server → Hyperscale migration: verifying migration prerequisites / "make sure the pre-reqs are installed", assessing a SQL Server instance for Azure SQL readiness, finding migration blockers/issues, provisioning a Hyperscale target (the create-time-only zone-redundancy decision), creating a Database Migration Service (DMS) + Self-Hosted Integration Runtime (SHIR), migrating schema then data offline, validating row counts, running any of the scripts/ files (00-setup, 01-assess, 02-pr |