Hi @sachinkrsah1995
Thanks for using Fabric Community.
In the scenario you described, if you create a lakehouse shortcut in prod01 using a shortcut from prod02, the data is still located in prod02 and uses the capacity of fabric02. The shortcut in prod01 is just a reference to the data in prod02, so it doesn’t consume any additional capacity in fabric01.
Here's why:
- Fabric shortcuts are essentially pointers to existing data sources. They don't hold the actual data themselves.
- When you create a shortcut in prod01 that points to another shortcut in prod02, you're simply creating a reference to the data ultimately stored in the target shortcut (located in prod02).
- Since the target shortcut resides in prod02 and leverages capacity fabric02, any operations performed through the shortcut in prod01 will utilize the resources of fabric02.
Therefore, regardless of the capacity assigned to the workspace where the new shortcut is created (prod01 with fabric01), the processing and resources will be consumed by the target shortcut's capacity (fabric02).
Hope this helps. Please let me know if you have any further questions.
