Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Reply
pmscorca
Helper V
Helper V

How creating a warehouse shortcut for another warehouse

Hi,

I've two warehouses, the first one in the workspace named ws1 and the second one in the workspace named ws2.

In a such scenario, how could I create a shortcut in the warehouse of ws2 to point to the warehouse of ws1 as an internal source?

Moreover, it seems that for a shortcut it is possible to point only to a warehouse table and not also to a view; the views are not visible.

Any helps to me, please? Thanks

It seems that Fabric doesn't manage very well the lakehouse/warehouse views and this is a serious lack!

1 ACCEPTED SOLUTION
AndyDDC
Memorable Member
Memorable Member

Hi @pmscorca if you're talking about the Warehouse (and not lakehouse) then currently you can't create a shortcut from a Warehouse.  You can only create shortcuts in Lakehouses (to other Lakehouses and Warehouses).

 

Keep an eye on the roadmap for any features What's new and planned for OneLake in Microsoft Fabric - Microsoft Fabric | Microsoft Learn

 

Add an Idea to the ideas site for anything you believe is lacking in features/functionality: Home (microsoft.com)

 

------------------------------------------------------------

If my reply has been useful please consider providing

kudos (thumbs up).

If my reply has answered your question please consider

marking it as the solution to close the thread

----------------------------------------------------------------

View solution in original post

4 REPLIES 4
frithjof_v
Resident Rockstar
Resident Rockstar

If you have a table in Warehouse A in WS1.

 

You want to shortcut this table into Warehouse B in WS2 (no-copy approach).

 

I think you will first need to create a Lakehouse in WS2. In this Lakehouse, create a shortcut to bring the table from the Warehouse A in WS1 into the Lakehouse in WS2. Then, in the Warehouse B in WS2, use a cross-database query to use the Lakehouse table in Warehouse B.

 

I think this is the current approach to solve that need.

Hi, many thanks for your reply and suggest, but it is a workaround and not a direct solution. Thanks

AndyDDC
Memorable Member
Memorable Member

Hi @pmscorca if you're talking about the Warehouse (and not lakehouse) then currently you can't create a shortcut from a Warehouse.  You can only create shortcuts in Lakehouses (to other Lakehouses and Warehouses).

 

Keep an eye on the roadmap for any features What's new and planned for OneLake in Microsoft Fabric - Microsoft Fabric | Microsoft Learn

 

Add an Idea to the ideas site for anything you believe is lacking in features/functionality: Home (microsoft.com)

 

------------------------------------------------------------

If my reply has been useful please consider providing

kudos (thumbs up).

If my reply has answered your question please consider

marking it as the solution to close the thread

----------------------------------------------------------------

Hi, thanks for your reply?

If it is possible to create a shortcut in a lakehouse, I don't understand because it isn't possible to create a shortcut in a warehouse: perhaps for an architectural reason?

About the view object as a feature/functionality there are some related issues: a lakehouse view isn't usable in a data pipeline, a warehouse view isn't visible for a shortcut in a lakehouse to point a warehouse, a warehouse view isn't usable in a PBI semantic model/report; why does a view seem an incomplete feature? For an architectural reason? Does a view on delta format cause some issues?

In general, whatever feature should follow a logic, a functional strategy, a vision, should be complete and not fragmented. An idea should be related to a new feature to propose and not to a missing segment about a functionality. Why is it possible to create a lakehouse view and is not possible to use it in a data pipeline? Is it better to have an incomplete feature or a complete feature? At least I think that it is very important to know the reasons because a feature is incomplete. We interface with the customers:  what do we tell them in such cases?

Helpful resources

Announcements
Europe Fabric Conference

Europe’s largest Microsoft Fabric Community Conference

Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.

AugFabric_Carousel

Fabric Monthly Update - August 2024

Check out the August 2024 Fabric update to learn about new features.

August Carousel

Fabric Community Update - August 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors