Forum Discussion
Issue on "Large dataset storage format" setting behavior in Power BI workspaces
Hi MAdam90 ,
Please try to consider using other methods:
(1)Using the enhanced refresh REST API , you can perform fine grained data refreshes, so that the memory needed by the refresh can be minimized to fit within your capacity's size.
(2) Optimize the data model by removing unnecessary columns, reducing the number of calculated columns, and using efficient data types. This helps to reduce the memory footprint of the dataset.
(3) Another option is to incrementally refresh the data. You can configure Power BI to refresh only a subset of data, such as the latest data or changed data, rather than refreshing the entire dataset. This helps reduce the memory requirements during the refresh process.Best Regards,
Neeko Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
hello Anonymous, XMLA endpoints for partitioning may not be applicable in my case, as my data is stored as CSV files in Azure, and CSV files don't natively support partitioning. XMLA is more suitable for Power BI datasets directly connected to a database.
Regards,
Hi MAdam90 ,
Please try to consider using other methods:
(1)Using the enhanced refresh REST API , you can perform fine grained data refreshes, so that the memory needed by the refresh can be minimized to fit within your capacity's size.
(2) Optimize the data model by removing unnecessary columns, reducing the number of calculated columns, and using efficient data types. This helps to reduce the memory footprint of the dataset.
(3) Another option is to incrementally refresh the data. You can configure Power BI to refresh only a subset of data, such as the latest data or changed data, rather than refreshing the entire dataset. This helps reduce the memory requirements during the refresh process.
Best Regards,
Neeko Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.