Forum Discussion
Helper Vone or mutiple fabric capacities?
Exceeded capacity limits makes your fabric environment fail hard. It makes Power BI etc. unaccessible. In order to protect my report layer I am considering moving my reports to a separate capacity if possible. Is that a good idea? For example replacing a F8 with two F4.
As in my case where I want to separate the reports - what else do I need to have in the "reports capacity"? warehouse and semantic model?
Anyone with similar experiences?
Workspace A (capacity A):
- This is your existing Workspace on the existing Capacity
- Here is your existing Warehouse A
New capacity B, with new workspace B:
- Create a new Lakehouse B
- Create shortcuts inside Lakehouse B, which point to the tables in Warehouse A (the tables in Warehouse A are the target paths for the shortcuts).
This means, the tables from Warehouse A will be available inside Lakehouse B.
- Create a new, custom direct lake semantic model, using the shortcut tables in Lakehouse B.
- Build reports on the semantic model.
Warehouse A (Capacity A) -> shortcuts -> Lakehouse B (Capacity B) -> Semantic model (Capacity B) -> Reports (I think they can be wherever, but put them on Capacity B for simplicity. Anyway, it's the semantic model that consumes the resources.)
13 Replies
- lbendlin
Super User
Generally a good idea, but you need to make sure that the workspaces you move don't have any leftover dependencies on workspaces you didn't move.
(Don't bother with the details - this is all happening on workspace level)
frithjof_vCommunity Champion
Are you using Direct Lake or Import mode?
If you're using Direct Lake, you could create a new Lakehouse on your "report capacity", and use shortcuts to bring data into that Lakehouse. Then build a semantic model and report.
If you're using Import Mode, you can have the semantic model and reports in a pro license workspace (shared capacity).
joakimfennoDirekt Lake
do I understand it correct that i could create shortcut in lakehouse pointing to my warehouse in a separate workspace and then create a semantic model on top of the shortcut objects in the warehouse?
- frithjof_v
Workspace A (capacity A):
- This is your existing Workspace on the existing Capacity
- Here is your existing Warehouse A
New capacity B, with new workspace B:
- Create a new Lakehouse B
- Create shortcuts inside Lakehouse B, which point to the tables in Warehouse A (the tables in Warehouse A are the target paths for the shortcuts).
This means, the tables from Warehouse A will be available inside Lakehouse B.
- Create a new, custom direct lake semantic model, using the shortcut tables in Lakehouse B.
- Build reports on the semantic model.
Warehouse A (Capacity A) -> shortcuts -> Lakehouse B (Capacity B) -> Semantic model (Capacity B) -> Reports (I think they can be wherever, but put them on Capacity B for simplicity. Anyway, it's the semantic model that consumes the resources.)
