Forum Discussion
Two Capacities With Same Data
Then I would recommend loading the data into separate lakehouses.
A lakehouse is tied into a workspace which is tied into a cpacity. For true separation you would need to load your data into two lakehouses, each in separate workspaces, and each workspace in a separate capacity.
Are you running Direct Lake queries or Import Mode?
Direct Lake.
Then I would recommend loading the data into separate lakehouses.
Follow up question on this: I tend to agree with you here. Is there any tool I can use to ensure the Internal and External stay in sync with each other? As stated previously, they will be the same data but only separated for usage concerns. If an update is made to one, the other would need to be updated as well.
You could decide to use the same data pipeline to feed both lakehouses. But yet again, a data pipeline is bound to a workspace so it will eat the CUs for that workspace's capacity.