stored Procedure from an existing Lakehouse to another Lakehouse using a deployment pipelines

[sebh]

=

Hi everyone,

I have a stored procedure in an existing Microsoft Fabric Lakehouse, and I’d like to deploy or copy it to another Fabric Lakehouse using deployment pipelines. Is there a recommended way to do this? Are there any best practices or limitations I should be aware of?

Any guidance or step-by-step instructions would be really helpful. Thank you!

[v-veshwara-msft · Accepted solution]

Glad the information helped.

While there’s no official confirmation yet, feature support in Fabric continues to expand, so it’s possible this capability may be considered in the future.

I’d recommend sharing this as an idea in the Fabric Ideas forum so it can be tracked by the product team. After creating the idea, please share the link here so others can upvote it and help bring it to the product team's attention.

Would you mind marking the helpful reply as the accepted solution to help others viewing this thread find the information more easily?

Regards,
Vinay
Community Support Team.

[v-veshwara-msft]

Thanks to @Srisakthi  for sharing an alternative approach. Using the Lakehouse SQL endpoint as a SQL DB project and integrating it with Git, and deployment through Azure DevOps pipelines, could be a practical workaround in the absence of native support through Fabric deployment pipelines.

Butplease keep in mind that incremental updates might not be supported with this method.

@sebh , you may consider trying this approach to see if it fits your scenario.

If you’ve submitted an idea in the Ideas Portal, please share the link here so others can upvote it and help bring it to the product team’s attention.

If there are no further updates, we may consider closing this thread.

For any new questions or topics, feel free to start a new thread in the Microsoft Fabric Community Forum - we’re here to help.

Thank you for being part of the Microsoft Fabric Community.

[Srisakthi · Accepted solution]

Hi @sebh ,

There is an option in Lakehouse sqlendpoint, sql db project. 

You can download and push to your git repositories and from there you can deploy to your lakehouse using azure devops pipeline.

Note: It might not do incremental update. Please check

Regards,

Srisakthi

[v-veshwara-msft]

Hi @sebh ,
Thanks for reaching out to Microsoft Fabric Community. Apologies for delayed response.

Deployment pipelines in Microsoft Fabric do not currently support deploying stored procedures from Lakehouses. When a Lakehouse is deployed, only the container and metadata like the SQL endpoint are included. Stored procedures, tables, and other internal objects are not carried over.

However, stored procedures created in a Fabric Data Warehouse are supported in deployment pipelines. The deployment will include schema objects such as tables, views, and stored procedures. Data itself is not moved, and any connections must be manually configured in each stage.

To deploy a stored procedure in a Data Warehouse:

1. Create or update the stored procedure in your development Data Warehouse.

2. Assign the Data Warehouse to a deployment pipeline.

3. Use the Deploy option to move it to the target stage.

4. After deployment, verify the stored procedure in the destination environment.

As a best practice, it's recommended to manage your SQL scripts in Git for version control. Stored procedures should avoid hardcoded values tied to a specific environment, and any environment-specific logic should be handled through parameters or configuration. After deployment, review roles and permissions to ensure they are correctly applied in the new environment.

You can find the official list of supported items here:
Overview of Fabric deployment pipelines - Microsoft Fabric | Microsoft Learn

Hope this helps. Please reach out for further assistance.
If this post helps, then please consider to give a kudos and Accept as the solution to help the other members find it more quickly.

Thank you.

[sebh]

thank you for this  - I wonder if Microsoft will be looking at this in the future 

[v-veshwara-msft · Accepted solution]

Glad the information helped.

While there’s no official confirmation yet, feature support in Fabric continues to expand, so it’s possible this capability may be considered in the future.

I’d recommend sharing this as an idea in the Fabric Ideas forum so it can be tracked by the product team. After creating the idea, please share the link here so others can upvote it and help bring it to the product team's attention.

Would you mind marking the helpful reply as the accepted solution to help others viewing this thread find the information more easily?

Regards,
Vinay
Community Support Team.