evaluate-offline-migration-readiness

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Evaluate Offline Migration Readiness

评估离线迁移就绪性

The bundled references define local readiness, default configuration-based sizing, and native combined reporting.
随附的参考文档定义了本地就绪性、 默认的基于配置的规格估算,以及原生组合报告。

When to Use

使用时机

Use directly or from
run-migration-assessment
for local/on-premises readiness assessment, with configuration-based sizing by default. Invoke after the server is confirmed Local. Route Azure identifiers and unresolved servers through
run-migration-assessment
.
直接使用,或从
run-migration-assessment
调用,以进行本地或本地部署的就绪性 评估,默认采用基于配置的规格估算。在确认服务器为
Local
后调用。 对于 Azure 标识符和未解析的服务器,请通过
run-migration-assessment
路由处理。

Workflow

工作流

Step 1: Check the Host and Tools

第 1 步:检查主机和工具

Before asking for connection details, apply OS requirements, then review assessment prerequisites before continuing. Continue on a supported Windows host.
在询问连接详情之前,先应用 OS 要求,然后 查看评估前置条件,再继续执行。 必须在受支持的 Windows 主机上继续。

Step 2: Confirm Inputs

第 2 步:确认输入

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.
复用上下文中的实例和输出文件夹。如果文件夹缺失, 则提供可选择的默认选项(
%LOCALAPPDATA%\Microsoft\SqlAssessment
)和自定义 选项。等待用户回答并使用所选路径。

Step 3: Check Existing Results

第 3 步:检查现有结果

When checking for prior 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.
检查已有结果时,使用
references/command-execution.md
查找与规范化后的 实例名称完全匹配的最新结果。
  • 已有结果 -> 在询问任何其他问题之前读取并呈现该结果。显示其 生成时间,并且只有在获得明确确认后才运行新的评估。
  • 没有结果 -> 继续执行。

Step 4: Run Assessment

第 4 步:运行评估

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 when details are missing, then run the matching command from
references/command-execution.md
when starting the assessment.
复用对话上下文中已有的完整连接详情。 如果服务器和凭据已经提供,不要询问连接方式。仅收集缺失的连接信息; 当缺少详情时,使用本地服务器连接,然后在启动评估时 运行
references/command-execution.md
中的匹配命令。

Step 5: Render

第 5 步:呈现结果

Read the output JSON, then read and render
references/readiness-output.md
before presenting results.
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.
读取输出 JSON,然后在呈现结果之前读取并遵循
references/readiness-output.md
。
这是必须严格遵循的输出约定:
  • 精确使用模板;不要用叙述性摘要替代模板。
  • 呈现全部三个目标部分和报告路径。
  • 在询问 SKU 规格估算之前,呈现完整的评估结果。
  • 重试、成功完成的新评估或已有结果均使用相同的 模板。
  • 用户之后选择的 SKU 数据收集时长不得替代或缩短 本步骤要求的就绪性响应。

Step 6: Choose SKU Sizing

第 6 步:选择 SKU 规格估算

Immediately after rendering readiness, ask:
"How would you like to size the Azure SQL recommendations?"
Always present selectable options with the first choice preselected:
  • Configuration-based sizing (Default, Recommended; no performance collection)
  • Collect 2 hours of performance data
  • Collect 24 hours of performance data
  • I don't want a SKU recommendation
Accepting the picker without changing its selection, or submitting an empty sizing answer, selects configuration-based sizing. Wait for the picker response; do not treat an unanswered question as permission to collect performance data. Allow a custom collection duration through the free-form answer. Preserve any explicit sizing preference already in context as the selection.
Delegate to
recommend-sku-sizing
with the selected mode, instance, output folder, native executable path, and exact readiness JSON path. For performance collection, also pass the selected duration in seconds. If the user declines, finish with the native readiness-only report already generated; identify unavailable SKU data rather than inventing recommendations.
呈现就绪性结果后,立即询问:
“您希望如何估算 Azure SQL 推荐规格?”
始终提供可选择选项,并预先选中第一个选项:
  • 基于配置的规格估算(默认,推荐;不收集性能数据)
  • 收集 2 小时性能数据
  • 收集 24 小时性能数据
  • 我不需要 SKU 推荐
接受选择器但未更改其选择,或提交空的规格估算答案,均表示选择基于配置的规格估算。 等待选择器的响应;不要将未回答的问题视为收集性能数据的许可。 允许通过自由格式答案指定自定义数据收集时长。保留上下文中已有的 明确规格估算偏好,并将其作为当前选择。
使用所选模式、实例、输出文件夹、原生可执行文件路径和 准确的就绪性 JSON 路径,委托给
recommend-sku-sizing
。对于性能数据收集, 还需以秒为单位传入所选时长。如果用户拒绝,则以已经生成的原生仅就绪性报告 结束;应说明 SKU 数据不可用,而不是虚构推荐结果。

Check it worked

检查是否执行成功

  • Positive verification: When reusing an existing report, confirm it matches the exact normalized instance name. When running a new assessment, additionally require the assessment command to succeed.
  • Cleanup verification: Confirm the generated temporary config was deleted whether the command succeeded or failed; retain the user-selected output folder and reports.
  • 正向验证: 复用已有报告时,确认其与规范化后的实例名称完全匹配。运行新评估时, 还需要确保评估命令执行成功。
  • 清理验证: 确认无论命令成功还是失败,生成的临时配置均已删除; 保留用户选择的输出文件夹和报告。

Notes

注意事项

  • Confirm the output folder before checking files.
  • Prefer an exact instance-tagged report. If the CLI generates
    SqlAssessmentReport-*.json
    instead, use it only from the confirmed per-instance output folder.
  • Include the generated native
    AssessmentReport-*.html
    path. Missing combined HTML is a report-generation failure, not a successful JSON-only fallback.
  • 检查文件之前,先确认输出文件夹。
  • 优先使用带有准确实例标记的报告。如果 CLI 改为生成
    SqlAssessmentReport-*.json
    ,则只能从已确认的按实例划分的输出文件夹中使用该文件。
  • 包含生成的原生
    AssessmentReport-*.html
    路径。缺少组合 HTML 报告属于报告生成失败, 不能视为仅生成 JSON 的成功降级方案。

Error Handling

错误处理

  • Cannot connect -> check server name, port, firewall, and credentials.
  • Tool or extension unavailable -> follow assessment prerequisites when restoring prerequisites.
  • 无法连接 -> 检查服务器名称、端口、防火墙和凭据。
  • 工具或扩展不可用 -> 恢复前置条件时遵循 评估前置条件。

References

参考文档

  • Open
    references/command-execution.md
    when checking or running an assessment.
  • Local server connection
  • OS requirements
  • Assessment prerequisites
  • Open
    references/readiness-output.md
    before rendering assessment results.
  • 检查或运行评估时,打开
    references/command-execution.md
    。
  • 本地服务器连接
  • OS 要求
  • 评估前置条件
  • 呈现评估结果之前,打开
    references/readiness-output.md
    。