Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Learn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
In Power Query for Oracle DB queries involving fields with the DATE type all filtering through query-folding is using the TO_TIMESTAMP function. As incremental refresh is implemented, we cannot use SQL statement option.
This causes issue as Oracle invokes internal function on date field used in filter to match timestamp. This is problematic as for large tables the quesry goes for full table scan instead of using index created on date field. This results in performance issues and the refresh failures invloving fact tables with huge data.
Index is consider if TO_TIMESTAMP is replaced with TO_DATE function
Is there a way to avoid TO_TIMESTAMP function being called here?
Thanks,
Vishal
Hi @Anonymous
Is the Native query from View Native Query in Power Query Editor? You apply filter on datetime column with GUI?
Regards,
Community Support Team _ Jing
Hi,
Yes the native query is from View Native Query in Power BI, and filter is applied on datetime column.
Thanks,
Vishal
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 16 | |
| 12 | |
| 10 | |
| 7 | |
| 6 |