COST: Consumption of Fabric Capacity by Datamarts

[DidiermaFR]

Fabric Trial include  Datamart features. Datamart Datamart consume some capacity somewhere either from a Power BI Premium or from a Fabric workspace : has the Datamart use any impact on the Fabric Capacity consumption - and at which cost - or should we consider it as an independant SAS software with no cost impact on Fabric Capacity ? 

[dieter92]

@otravers @Greg_Deckler The Fabric Capacity metrics app approve Otravers opinion : Datamart use only the compute of the Fabric Dataset, and not the storage. In the compute, on demand refresh of the Datamart and writing the Dataset is also considered by the Microsoft app compute duration.

[otravers]

It's a compute, so in principle it should consume computing units within the Fabric capacity. Microsoft just added logging of warehouse consumption in the metrics app, I haven't checked whether datamart compute registers.

[Greg_Deckler]

@otravers Well, there is storage involved as well. I mean, you have to actually store the data for datamarts somewhere. Do datamarts count as OneLake storage? Does the datamart count as OneLake storage and then also the dataset count separately as OneLake storage? The Fabric capacity reports are useless in this regard, they only report at the workspace level and don't actually show what in the workspace is consuming storage. It's all a big mystery and all things you never had to worry about with Premium since each premium capacity entitled you to 100TB of storage. It's a wreck.

[otravers]

Fair enough, I saw your bathrobe reveal video.

[Greg_Deckler]

@DidiermaFR Who boy, who really knows right now? If you have a Premium capacity, each Premium capacity comes with 100TB of storage. Those rules change under Fabric. You have to pay for storage separately, at least in the current "pay-as-you-go" model. Maybe reserved capacities will include storage? It's completely unknown from what I can find. Here's my analysis so far: