evaluate-offline-migration-readiness
Run migration readiness assessment for a local or on-premises SQL Server using az datamigration. Windows-only.
- License 许可
- MIT
- 最近更新
- 2026-11-01
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- evaluate-offline-migration-readiness
- description
- Run migration readiness assessment for a local or on-premises SQL Server using az datamigration. Windows-only.
- allowed-tools
- Bash(az:*) PowerShell Grep View
02 资源文件 3
- 参考文档references/command-execution.md2.3 KB
- 参考文档references/readiness-output.md2.4 KB
- 参考文档skill-contract.yml3.3 KB
03 SKILL.md 正文
Evaluate Offline Migration Readiness
When to Use
Use directly or from run-migration-assessment for local/on-premises readiness
assessment without performance-based SKU sizing. Invoke after the server is
confirmed Local. Route Azure identifiers and unresolved servers through
run-migration-assessment.
Workflow
Step 1: Check the Host and Tools
Apply OS requirements, then assessment prerequisites, before asking for connection details or an output folder. Continue on a supported Windows host.
Step 2: Confirm Inputs
Reuse the instance and output folder from context. If the folder is missing,
present selectable Default (%LOCALAPPDATA%\Microsoft\SqlAssessment) and Custom
choices. Wait for the answer and use the selected path.
Step 3: Check Existing Results
Use references/command-execution.md to find the latest result matching the exact
normalized instance name.
- Existing result -> read and render it before asking anything else. Show its generation time and run a fresh assessment only after explicit confirmation.
- No result -> continue.
Step 4: Run Assessment
Reuse complete connection details already present in conversation context.
Do not ask how to connect when the server and credentials were already
provided. Collect only missing connection information using
local server connection, then run the matching command
from references/command-execution.md.
Step 5: Render
Read the output JSON, then read and render
references/readiness-output.md.
This is a hard output contract:
- Use the template exactly; do not replace it with a prose summary.
- Render all three target sections and the report path.
- Render the complete assessment before asking about SKU sizing.
- A retry, successful fresh assessment, or existing result uses the same template.
- The user's later SKU-duration choice must not replace or shorten the readiness response already required by this step.
Step 6: Offer SKU Sizing
Immediately after rendering readiness, ask:
"How long should I collect performance data for a right-sized Azure SQL SKU recommendation?"
Present selectable options:
- 2 hours
- 24 hours (Recommended)
- I don't want a SKU recommendation
Allow a custom duration through the free-form answer. Convert the selected
duration to seconds and delegate to recommend-sku-sizing. If the user declines,
finish after readiness. Present the duration choices directly after readiness.
Notes
- Confirm the output folder before checking files.
- Prefer an exact instance-tagged report. If the CLI generates
SqlAssessmentReport-*.jsoninstead, use it only from the confirmed per-instance output folder. - Include the generated report path. Prefer HTML when present; otherwise link the JSON report.
Error Handling
- Cannot connect -> check server name, port, firewall, and credentials.
- Tool or extension unavailable -> follow assessment prerequisites.
References
references/command-execution.md- Local server connection
- OS requirements
- Assessment prerequisites
references/readiness-output.md
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.