This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
In this post, we will introduce the practice of copying data between Lakehouse that cross different workspaces via Data pipeline.
In this example, we will copy data from a Lakehouse in another workspace to a Lakehouse in the current workspace by leveraging parameters to specify the workspace and Lakehouse.
Follow the steps below to achieve that:
Copy_Data_from_Lakehouse_in_Another_Workspace_Using_Data_pipeline
Screenshot_showing_the_Add_dynamic_content_page
Note that the parameter value should be the Lakehouse object ID. To get your Lakehouse object ID, open your Lakehouse, and the ID is after /lakehouses/ in the URL.
Screenshot_showing_the_Lakehouse_object_ID
Copy_Data_from_Lakehouse_in_Another_Workspace_Using_Data_pipeline
To get your Workspace ID, open your workspace, and the ID is after /groups/ in your URL.
Copy_Data_from_Lakehouse_in_Another_Workspace_Using_Data_pipeline
Copy_Data_from_Lakehouse_in_Another_Workspace_Using_Data_pipeline
We have a plan to introduce a native experience for the cross-workspace experience. This will allow you to select Lakehouses and other objects in another workspace directly. Please stay tuned!
Have any questions or feedback? Leave a comment below!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.