Forum Discussion
Redshift and Gateway issue
Then the pbix file is so big that it cant be published.You can bootstrap the incremental refresh partitions to keep the original size under 10 GB. Then use XMLA refresh to fill each partition separately. This will then allow you to load datasets that are half the size of your capacity, and supposedly even beyond.
Hi lbendlin ,
no gaps in any primary key column. I have tried with remove empty in power query but still get the same error.
Also, in other attempts I was deleting the primary key column to reduce size, since its not needed, but still no luck.
I have tried various incremental refresh setttings, from trying to pull the entire dataset with a setting like
bring data from last 5 years and refresh last 10 days, to last 3 months and last 5 days for example.
I'm trying to load a single table. I'm using it's datetime column.
Instead of a dataflow try using a dataset with incremental refresh.
The issue with a dataset lbendlin is that incremental refresh doesn't seem to work with Amazon Redshift. Then the pbix file is so big that it cant be published. And if it is in a publishable size, again the first refresh will fail with similar errors from the gateway.
Then the pbix file is so big that it cant be published.You can bootstrap the incremental refresh partitions to keep the original size under 10 GB. Then use XMLA refresh to fill each partition separately. This will then allow you to load datasets that are half the size of your capacity, and supposedly even beyond.
Thanks for this suggestion lbendlin , I have managed to do that with SSMS and ALM Toolkit.
The big issue now is that the data are not accurate. For some reason its like it duplicates the data of the last month and it may have small differences elsewhere.
Any ideas on how to deal with this, I have refreshed several times and the issue persists.