Forum Discussion
Anthony_A
1 year agoRegular Visitor
Deploying from Dev to Prod
Hi All, I am new to fabric. I've been using my Dev environment for the last few months. I recently created a prod workspace and deployed my LH and WH. I noticed none of the tables or schemas went...
- 1 year ago
As lbendlin mentioned deployment pipelines in Fabric are designed; they move content definitions, code, and metadata rather than the actual data or the underlying physical table structures
They copy items like reports, notebooks, and other code artifacts while preserving their connections and configurations
create notebook, data pipeline etc to move and create actual data
good read
https://www.kevinrchant.com/2024/11/06/fabricators-guide-to-microsoft-fabric-deployment-pipelines
lbendlin
1 year agoSuper User
That is normal. Whatever doesn't get committed to Version control is also not getting deployed. You should have notebooks dedicated to the setups in each of the deployment pipeline's workspaces.