Forum Discussion

RajeshKapur's avatar
RajeshKapur
Icon for Helper I rankHelper I
1 year ago
Solved

Share warehouse/lakehouse between Workspaces

Hi All,   We have a situation in our project where we have DataPipelines and Lakehouse/Warehouse in Workspace A. Now for each departments we have different workspaces say WorkspaceDeptA,WorkspaceDe...
data warehouse
Warehouse
  • Anonymous's avatar
    Anonymous
    1 year ago

    Hi RajeshKapur ,

     

    Thanks for the reply from DataBard .

     

    You can use the Deployment pipeline to deploy the data you need to share in WorkspaceDeptA (e.g. lakehouse, warehouse) to WorkspaceDeptB, WorkspaceDeptC.

     

    This approach enables data sharing without opening up access to Workspace A to all users.

     

    For more information about the Deployment pipeline, please refer to the official documentation below:

    Get started using deployment pipelines, the Fabric Application lifecycle management (ALM) tool - Microsoft Fabric | Microsoft Learn

     

    If you have any other questions please feel free to contact me.

     

    Best Regards,
    Yang
    Community Support Team

     

    If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.
    If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!

DataBard's avatar
DataBard
Icon for Most Valuable Professional rankMost Valuable Professional
1 year ago

Hi RajeshKapur,

 

For lakehouses, Shortcuts would be the recommended approach. Yes you do have to select what to shortcut table-by-table, but it's a more efficient approach than having to write a process to do the same.

 

For warehouses, it depends on what destination you want to go to.

  • Lakehouse? Under tables, you can see a schema shortcut option. This would let you select a schema and shortcut all tables in the schema.

  •  

  • Warehouse? You can't shortcut per se, but within a warehouse, you can hit the plus sign in a warehouse to add a connection to another warehouse. It's not technically a shortcut (assuming you have access, you would be able to modify data/objects in the source), but it's an option depending on your use case. I haven't looked at this yet from the lens of security, so testing would be needed to assess whether this approach persists security or not.

  •  

As to your question about devops pipeline, are you looking to deploy warehouses/lakehouses that have the shortcuts defined? If so, in my testing, shortcuts in lakehouses and warehouses are not retained. You would have to set the shortcuts up again in each workspace.

 

Once you have your answer, be sure to select it so others in the community can learn from it.