Forum Discussion
Post PatronRedshift views incremental refresh possibility in power bi
Hi Koritala ,
The reason View Native Query is still greyed out is because your Redshift view is a bit complex, and Power BI is not able to fold the query automatically, this is very common with views. To get incremental refresh working, you can follow a simple approach that is switch your table to Import mode (or Hybrid if you have Premium), then create a materialized view in Redshift with the same logic. After that, connect to this materialized view directly from the navigator without using any custom SQL. Once you apply the RangeStart/RangeEnd filter step in Power Query, the 'View Native Query' option will become active and incremental refresh will start working properly.
Materialized views behave just like normal tables in Power BI and almost always fix this issue.
Hi Koritala ,
I hope the information provided above assists you in resolving the issue. If you have any additional questions or concerns, please do not hesitate to contact us. We are here to support you and will be happy to help with any further assistance you may need.
Post PatronHi sshirivolu,
Still I couldn't see the native sql option.
Regards,
Sri
Hi Koritala ,
The reason View Native Query is still greyed out is because your Redshift view is a bit complex, and Power BI is not able to fold the query automatically, this is very common with views. To get incremental refresh working, you can follow a simple approach that is switch your table to Import mode (or Hybrid if you have Premium), then create a materialized view in Redshift with the same logic. After that, connect to this materialized view directly from the navigator without using any custom SQL. Once you apply the RangeStart/RangeEnd filter step in Power Query, the 'View Native Query' option will become active and incremental refresh will start working properly.
Materialized views behave just like normal tables in Power BI and almost always fix this issue.
Hi Koritala ,
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you
- Koritala
Hi v-sshirivolu,
Thanks for your follow up.
I am bit confused witht the following statement "switch your table to Import mode (or Hybrid if you have Premium), then create a materialized view in Redshift with the same logic."
Are you suggesting first create a table and then create the materialized view as well? Also, as you suggested import the table, in my case table data is having huge volume and unable to load into the memory as we are using PPU license.
Can anyone suggest in this case how to overcome my problem?
Thanks,
Sri.
Thanks,
Srinivas.
Hi Koritala ,
No, You don’t have to create a separate physical table first. You can directly create a materialized view in Redshift using the same logic as your existing view. Since a materialized view stores data physically in Redshift, it reduces query complexity and performs better than a normal view.
For the large data volume and PPU memory limitation, instead of loading the entire history into Power BI, it’s better to limit the data at the Redshift level itself, for example keep only the last 1–2 years using a date filter. After that, use Incremental Refresh with RangeStart and RangeEnd in Power BI so that only recent data is refreshed, not the full dataset. This way, most of the heavy processing stays in Redshift, Power BI imports only the required data, and incremental refresh becomes practical even with PPU memory limits.