Work across more than one platform
Assess a Synapse dedicated pool or SSIS estate for a rebuild on Fabric
- When Fabric is the mandate and the estate is hundreds of packages nobody wants to open.
- When a Synapse dedicated pool holds logic nobody has inventoried in years.
Inventory a Synapse dedicated pool or SSIS estate, flag unsupported T-SQL and components, map data types, and rank a prioritised lift, rebuild, or retire backlog. Covers the assessment and its backlog, not performing the rebuild itself.
Sample This Recipe has not been materialized in the Cookbook repository yet. Its trigger, description, prompt, agent guidance and acceptance conditions, and the explanation below, are prototype drafts. Its name, job, area and readiness come from the reconciled Cookbook seed snapshot. Readiness is a separate question from this one: it says whether the capability exists, not whether the writing has been reviewed.
Review planned Recipe
At least one capability or object type this Recipe needs is not supported yet.
Read the VibeData Recipe `assess-synapse-ssis-for-fabric` at https://getvibedata.ai/cookbook/assess-synapse-ssis-for-fabric At least one capability or object type this Recipe needs is not supported yet. Treat it as a reference, not as work to execute.
Recipe id assess-synapse-ssis-for-fabric · Not yet materialized in the Cookbook repository, so the pointer addresses this page.
Verified by
What has to be observably true before this Recipe is finished.
- the inventory reconciles to the source catalog with no object missing
- every unsupported T-SQL construct or component is flagged with its location
- each object in the estate is ranked lift, rebuild, or retire with a stated reason
- the dependency graph accounts for every object in the inventory
Recipe promptThe task specification the agent reads. Reference only — it is not what you copy.
Deliver: Assess a Synapse dedicated pool or SSIS estate for a rebuild on Fabric. Inventory a Synapse dedicated pool or SSIS estate, flag unsupported T-SQL and components, map data types, and rank a prioritised lift, rebuild, or retire backlog. Covers the assessment and its backlog, not performing the rebuild itself. Execute inside the current Intent. Its Domain, repository, platform, environment and attached sources are the context for this work — read them rather than asking for them. The work is done when: - the inventory reconciles to the source catalog with no object missing - every unsupported T-SQL construct or component is flagged with its location - each object in the estate is ranked lift, rebuild, or retire with a stated reason - the dependency graph accounts for every object in the inventory Report the evidence for each condition above with the result. A condition you cannot meet is something to say, not something to work around.
Agent guidanceHow the agent approaches the work, and what it will not do.
Establish which platform is authoritative today and what in the project is platform-specific. Build against the target in an isolated copy and reconcile the two runs against each other before anything is cut over.
Composes
- permission and billing reads
- dbt in the project
- isolated-copy execution and gate verification
Guardrails
- Build in an isolated copy. Production is read, never written.
- At least one capability this Recipe needs is not supported yet. Say so and stop rather than substituting a different approach.
What you need
- Microsoft Fabric Warehouse.
- Read access to the billing or permission surface the work reads from.
- dbt in the project, or the intent to add it.
- Needs read access to the full Synapse or SSIS estate.
How it goes
- Name both platforms, and which one is authoritative today.
- Let it read what in the project is platform-specific and what is not.
- Review the plan before anything is rebuilt.
- Build and run against the target in an isolated copy.
- Reconcile the two runs against each other, at the grain the consumers read.
- Read the acceptance conditions before you cut over, not after.
What you end up with
The deliverable, in your own repository, as governance and cost work a reviewer who knows the project reads as native to it. Alongside it, the evidence for every one of the acceptance conditions above — which is the part that is still there in three weeks when somebody asks.