get-migration-assessment
Retrieve existing SQL Server migration assessment data from Azure Resource Graph using required instance-level and database-level queries.
- License 许可
- MIT
- 最近更新
- 2026-11-01
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- get-migration-assessment
- description
- Retrieve existing SQL Server migration assessment data from Azure Resource Graph using required instance-level and database-level queries.
- allowed-tools
- Bash(az:*, curl:*) PowerShell Grep View
02 资源文件 3
- 参考文档references/arg-queries.md7.6 KB
- 参考文档references/response-schema.md10.5 KB
- 参考文档skill-contract.yml3.6 KB
03 SKILL.md 正文
Get Migration Assessment
When to Use
Use for existing Azure SQL Server assessment, readiness, blocker, SKU, and cost data. This skill does not trigger a new assessment.
Workflow
Step 1: Resolve Inputs
Use ARM resource identification. Reuse identifiers already in context. Confirm a defaulted subscription by display name and ID.
Step 2: Query Instance Data
Build and execute the instance query from references/arg-queries.md.
Step 3: Query Database Data
Build and execute the database query from references/arg-queries.md for every
returned instance.
Step 4: Interpret Results
Use references/response-schema.md. For every NotReady target, identify the
server or database blocker. If blocker details are unavailable, report a data gap.
If assessment data or assessmentUploadTime is missing, state that no migration
assessment data is available and identify likely causes: it has not been enabled
or run, results have not uploaded, the agent is not configured, or permissions are
insufficient.
Step 5: Render Results
Use assessment output to render the combined readiness and SKU recommendation.
- Multiple instances -> show a summary table, then render each instance.
For multiple instances, include aggregate readiness, cost, and common blocker insights when the returned data supports them.
Completion Check
- Both query phases completed for every instance.
- Pagination completed.
- Every
NotReadyresult has a cause or data-gap note. - Missing settings or readiness are stated explicitly.
Notes
- Use ARG as the assessment read transport.
- Execute queries through the
curladapter inreferences/arg-queries.md. - Exclude
master,model,msdb, andtempdb. - Show subscription display name with its ID.
- Follow the output template exactly.
Error Handling
- 401/403 -> verify Azure CLI login and read permission on the target scope.
- 429 -> honor
Retry-After; report persistent throttling. - Invalid resource URI -> show the expected Azure SQL Server instance resource-ID format.
- Empty result -> show the subscription display name/ID and resource group that were searched.
References
references/arg-queries.mdreferences/response-schema.md- ARM resource identification
- Assessment output
04 同仓库更多 Skills
keynote-demo-app
Build or extend a SQLCon EU 2026 keynote demo application so it looks and behaves like the other keynote apps. Use when creating a new demo view (invoices, operations, orders), restyling an existing app to match, adding a deliberate database anti-pattern for a troubleshooting demo, or wiring an app to Azure SQL or Fabric SQL with managed identity. Triggers include "make this look like the keynote app", "build a demo view", "add the slow query demo", "match Caldova styling".
validate-post-migration-data
Validate data and schema after migrating SQL Server to Azure SQL Database, Azure SQL Managed Instance, or SQL Server on Azure VM. Use after migration, restore, BACPAC import, LRS completion, cutover validation, row-count comparison, or source-target reconciliation.
sql-server-to-sql-mi-lrs-migration
Migrate SQL Server databases to Azure SQL Managed Instance with Log Replay Service (LRS) using managed identity for Blob access. Use for SQL Server to SQL MI, LRS, log replay, continuous restore, or low-downtime backup-chain migrations.
sql-bacpac-to-azure-sql-db-migration
Migrate one or all user databases from SQL Server to Azure SQL Database with an offline BACPAC workflow. Use for BACPAC, SqlPackage export/import, bulk database migration, or offline Azure SQL Database migration requests.
sql-backup-restore-to-azure-sql-vm-migration
Migrate a SQL Server 2008 through SQL Server 2025 source to a SQL Server 2025 target wherever it runs, including SQL Server on Azure VM, by creating a local full backup, uploading it to Azure Blob Storage with AzCopy and the operator's Microsoft Entra identity, and restoring from URL with the target SQL Server managed identity. Sources newer than SQL Server 2025 are blocked because target restore compatibility has not been validated. Use for SQL-to-SQL, local-backup, AzCopy, managed-identity, Azure SQL VM, or SQL Server 2025 restore migrations.
run-migration-assessment
Route generic or unresolved SQL Server assessment, readiness, compatibility, cost, and SKU recommendation requests. Use for bare server names or whenever Azure versus local/on-premises is not explicit; ask which source applies, then delegate.