Forum Discussion
Link to Fabric - Cost
Hi,
I'm evaluating Dataverse Link to Microsoft Fabric and I'm trying to better understand the actual cost implications.
The documentation states that:
"Tables added to OneLake consume Dataverse storage."
and
"Enabling this feature results in an increase in Dataverse database storage consumption."
However, it's not entirely clear how significant this increase is in real-world scenarios.
Could anyone share their experience regarding:
How much additional Dataverse storage is typically consumed when enabling Link to Fabric?
Hi Luigia-Costabil,
That depends oon how much data you have.
The Link to Fabric feature will take all your dataverse data, and create parquet files for it that are compatible with Fabric Lakehouses. These parquet files are stored in Dataverse, not in OneLake.
So if you have a very small dataverse enviornment, the storage will be small. If you have a very large one, the storage used will be larger.
1 Reply
Hi Luigia-Costabil,
That depends oon how much data you have.
The Link to Fabric feature will take all your dataverse data, and create parquet files for it that are compatible with Fabric Lakehouses. These parquet files are stored in Dataverse, not in OneLake.
So if you have a very small dataverse enviornment, the storage will be small. If you have a very large one, the storage used will be larger.