- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The 10GB uncompressed data gateway limitation
I am confused.
The amount of uncompressed data on the gateway client has exceeded the limit of 10 GB for a single table. Please consider reducing the use of highly repetitive strings values through normalized keys, removing unused columns, or upgrading to Power BI Premium.
Please try again later or contact support. If you contact support, please provide these details.
I checked the tables in SQl Server Management Studio. The biggest table has a total storage of 8GB, but i am only querying a fraction. The final local compressed pbix is 561mb.
This seems very odd. How can I investigate this further? There is no information in the error message hinting what table i might be.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It is a fact table with mainly numeric data. I did convert a couple of columns of small strings to numeric values but it did not help.
Finally I had som success by reducing the amount of rows imported.
I suspect the data gets quite bloated in the import process, or maybe there still is a limit on the number of rows allowed. 10GB seems like a lot of data when comparing how much data the actual table stores on disk. I wish the process was more transparent so that I didn't have to guess what is happening.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Anonymous,
Do you import all columns of the big table to Power BI Desktop and do you have multiple calculations in the PBIX file?
The above error message indicates that the uncrompressed data size exceeded the 10GB limitation at the time of reading the data during the refresh process, reducing the use of highly constant, long string values and instead using a normalized key or removing the column (if not in use) will help.
There are some discussions in the similar threads below for your reference.
https://community.powerbi.com/t5/Service/The-received-uncompressed-data-on-the-gateway-client-has/td-p/194153/page/2
https://community.powerbi.com/t5/Issues/Knowing-the-uncompressed-dataset-size-on-the-gateway/idi-p/192450/page/2#comments
Regards,
Lydia
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It is a fact table with mainly numeric data. I did convert a couple of columns of small strings to numeric values but it did not help.
Finally I had som success by reducing the amount of rows imported.
I suspect the data gets quite bloated in the import process, or maybe there still is a limit on the number of rows allowed. 10GB seems like a lot of data when comparing how much data the actual table stores on disk. I wish the process was more transparent so that I didn't have to guess what is happening.

Helpful resources
Subject | Author | Posted | |
---|---|---|---|
09-24-2018 11:24 AM | |||
07-01-2024 08:18 AM | |||
05-14-2024 02:00 AM | |||
Anonymous
| 08-20-2024 12:44 AM | ||
03-14-2024 01:07 AM |
User | Count |
---|---|
137 | |
107 | |
84 | |
59 | |
46 |