Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

The ultimate Microsoft Fabric, Power BI, Azure AI & SQL learning event! Join us in Las Vegas from March 26-28, 2024. Use code MSCUST for a $100 discount. Register Now

Reply
Bamak
Helper V
Helper V

Question on the size of imported dataset (limitation & compression ratio between different stages)

Hello

I have read that Power BI limits each imported dataset to 1 GB
whatever the license
In my case, I import data from SQL DB Azure
1) Must be based on the size of the pbix file to check this limit
or is it the sum of the size tables that we observe in DaxStudio for example?
2) Are there average ratios of size differences between the different stages?
SQL Data size = Ratio1 * Model size (I read 10 thanks to vertipack)
Model size = Ratio2 * pbix file size
3) About the size in my case I have
Pbix file = 157KB
Size of the model in DaxStudio (all tables) = 4.63MB

By cons I do not understand why management studio shows me his side -> 0.99MB for the model?

And why in Service, I observe 2GB for the dataset in storage management?

thank you in advance for your help
Envoyer des commentaires
Historique
Enregistré
Communauté

2 ACCEPTED SOLUTIONS
GilbertQ
Super User
Super User

Hi there

The imported datasize is based on the PBIX file size.

DAX Studio is the amount of memory it is consuming.

Where do you see the 2GB for dataset storage?

The 2GB could be all of the datasets that have been uploaded.




Did I answer your question? Mark my post as a solution!

Proud to be a Super User!







Power BI Blog

View solution in original post

Thank you Gilbert,

you answered the limited aspect of the deployment by mentioning the size of the pbix file
But I wonder about the different info (on size) that I observe once the deployment is completed (so decompression done pbix --> memory)
a) The size of the model visible in Dax Studio (all tables) is 4.10MB
b) Management studio presents for its part an estimated model size of 0.99MB, and here I do not understand the big difference with what Dax Studio presents, please?  (Info : No System time tables) 
c) The storage management of the service work space (parameters) has a size of 2 MB for the corresponding dataset

So we have 3 different sizes for the same model (Dax studio / Management Studio / Dataset size in service storage management)

 

 

Best regards 

Christophe

View solution in original post

3 REPLIES 3
GilbertQ
Super User
Super User

Hi there

The imported datasize is based on the PBIX file size.

DAX Studio is the amount of memory it is consuming.

Where do you see the 2GB for dataset storage?

The 2GB could be all of the datasets that have been uploaded.




Did I answer your question? Mark my post as a solution!

Proud to be a Super User!







Power BI Blog

Thank you Gilbert,

you answered the limited aspect of the deployment by mentioning the size of the pbix file
But I wonder about the different info (on size) that I observe once the deployment is completed (so decompression done pbix --> memory)
a) The size of the model visible in Dax Studio (all tables) is 4.10MB
b) Management studio presents for its part an estimated model size of 0.99MB, and here I do not understand the big difference with what Dax Studio presents, please?  (Info : No System time tables) 
c) The storage management of the service work space (parameters) has a size of 2 MB for the corresponding dataset

So we have 3 different sizes for the same model (Dax studio / Management Studio / Dataset size in service storage management)

 

 

Best regards 

Christophe

Hi there

The easiest way to understand it is look at the size of the PBIX when using Power BI Pro and uploading to the Power BI Service.

As long as it is less than 1GB you are good to go.

If you start using Power BI Premium then you have to look into the memory size being used.




Did I answer your question? Mark my post as a solution!

Proud to be a Super User!







Power BI Blog

Helpful resources

Announcements
Fabric Community Conference

Microsoft Fabric Community Conference

Join us at our first-ever Microsoft Fabric Community Conference, March 26-28, 2024 in Las Vegas with 100+ sessions by community experts and Microsoft engineering.

February 2024 Update Carousel

Power BI Monthly Update - February 2024

Check out the February 2024 Power BI update to learn about new features.

Fabric Career Hub

Microsoft Fabric Career Hub

Explore career paths and learn resources in Fabric.

Fabric Partner Community

Microsoft Fabric Partner Community

Engage with the Fabric engineering team, hear of product updates, business opportunities, and resources in the Fabric Partner Community.

Top Solution Authors
Top Kudoed Authors