Share via

Migration feature on SSMS 22

Urbel 605 Reputation points
2026-05-25T02:27:55.1566667+00:00

Hi Expert,

I'm running first time Migrate SQL Server feature on SSMS 22 for Database Assessment with 10TB size, this report as below:

"Status": "Error",

  "**AssessmentRecommendations": [],**

  "Name": "DBStaging",

  "SizeMB": 11429068.8125,

  "ServerVersion": "13.0.5820.21",

  "ServerEdition": "Enterprise Edition: Core-based Licensing (64-bit)",

  "CompatibilityLevel": "CompatLevel130",

  "ServerName": "myDBs"

another DB report Status: "Completed"

is this normally result if Status: "Error" ? because on Dialog box said that this DBStaging .." There are no Compatibility issues with your database. And Findings 0

thanks for all ang great appreciation for reply

warm regards,

UrBel

SQL Server | Other
SQL Server | Other

Additional SQL Server features and topics not covered by specific categories

Answer recommended by moderator

Akhil Gajavelly 1,830 Reputation points Microsoft External Staff Moderator
2026-05-27T07:15:27.3333333+00:00

Hi @Urbel ,

Thank you for sharing the additional details, and thanks as well to the Q&A Assist response for the helpful explanation.

Just following up to check whether you were able to re-run the assessment for the DBStaging database or validate the results using an updated SSMS build / DMA assessment.

Since the database is quite large (~10 TB), we want to confirm whether the "Status": "Error" persists or if the assessment now completes successfully. Any additional logs or screenshots from the assessment output would also help the community better understand what may be causing the issue.

Please let us know how things are progressing when you have a chance.

Thanks,
Akhil.

Was this answer helpful?

0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-05-25T02:28:09.5633333+00:00

    “Status: Error” in the JSON output is not normal for a successful assessment, even if the dialog says “There are no compatibility issues” and “Findings 0”. A completed and healthy assessment should show a status like “Completed/Ready/Ready with warnings/Not ready” depending on the tool and target.

    Key points from the tools in SSMS 22:

    1. The migration/upgrade components in SSMS are designed to:
      • Run an assessment and then open a report listing issues by category (breaking changes, behavior changes, deprecated features, feature parity).
      • Show readiness states such as Ready, Ready with warnings, or Not ready for Azure targets, or a completed upgrade assessment for on‑prem upgrades.
      • When there are no compatibility issues, the report should still complete successfully, not return an error status.
    2. For upgrade assessment (on‑prem to higher SQL version):
      • After running Upgrade Assessment, the tool completes and opens a report.
      • The report lists issues; if there are none, it simply shows no findings.
      • There is no indication in the documentation that “no findings” should map to a JSON Status: "Error".
    3. For Azure migration readiness in SSMS:
      • Readiness categories are Ready, Ready with warnings, or Not ready.
      • “Error” is not documented as a normal readiness state; it indicates the assessment did not run or complete correctly.

    Given that:

    • One database shows Status: "Completed" and the other Status: "Error".
    • The dialog for DBStaging says “no compatibility issues” and “Findings 0”.

    The most likely interpretation is:

    • The assessment engine encountered a non‑compatibility‑related problem (for example, size, metadata read, or internal rule execution) and flagged the run as Error, but the compatibility rules that did execute did not find any issues.
    • This is not the expected or “normal” final state; it should be treated as a failed or partial assessment, not as a clean bill of health.

    Recommended actions:

    1. Re‑run the assessment for DBStaging only, ensuring:
      • SSMS 22 is fully up to date and the Hybrid and Migration workload is installed.
      • The login used has sysadmin permissions, as required by the migration/upgrade components.
    2. If the status remains Error while showing 0 findings, treat it as an assessment failure and not as “no issues”. For a 10 TB database, consider:
      • Using the Azure Arc–based migration assessment (if the instance is Arc‑enabled) and reviewing the readiness and compatibility tabs.
      • Or using a separate assessment tool such as Data Migration Assistant (DMA) for cross‑validation.
    3. Only rely on the DBStaging assessment as “clean” once the status is a normal completed/readiness state rather than Error.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.