Know what the Synapse estate contains before you pick a date

What we look at on Synapse

• Dedicated SQL pools: tables, distributions, stored procedures and the T-SQL that assumes them
• Serverless SQL databases and the external tables they sit on
• Spark pools, notebooks and libraries that will not run unchanged on Databricks runtime
• Azure Data Factory pipelines, triggers and linked services that have to move with the data
• PolyBase, CETAS and COPY paths, and what they become under Lakeflow or Auto Loader
• Synapse RBAC plus SQL permissions, and what that map looks like under Unity Catalog

What a person still has to do

• 01HASH and ROUND_ROBIN distributions have no equivalent to paste. Partitioning on Delta is a design choice.
• 02Stored procedures in T-SQL stay in the residue. Lakebridge will not turn a procedure into a pipeline.
• 03ADF graphs become Lakeflow or Databricks Jobs. The dependencies have to be redrawn, not imported.
• 04Synapse Spark notebooks need a Databricks runtime pass. Libraries and cluster shapes change.
• 05PolyBase and CETAS become an ingestion path we choose, not a converted statement.

What the two weeks produce

• 01An inventory where every object is dispositioned as in scope, excluded, or owned by a person
• 02The exclusions written down and agreed, so the scope still holds when someone questions it in month four
• 03A dependency map and a wave plan that respects it
• 04A named owner against every workload surface
• 05Parity criteria per object type, agreed before any conversion runs
• 06A hard-object pilot, chosen as the thing most likely to break
• 07A go or no-go recommendation with the reasoning shown

The other sources