Forum Discussion
OLE DB or ODBC error with Databricks: Temporary Result File URL Expired
Hi data_msfabric Switching to the Azure Databricks connector might improve stability, as it’s optimized for this use case. You could also break queries into smaller chunks or enable caching to improve performance.You can consult your Databricks admin to see if the TTL for result files can be extended to avoid timeouts.
Thank you for reaching out to the Microsoft Fabric Forum Community.
Hi Akash_Varuna, thank you for your response and for pointing out key directions. Switching to the Azure Databricks connector can indeed improve stability, as it's designed specifically for this integration and handles query execution and result retrieval more reliably than generic ODBC or Spark connectors. Breaking down large queries and considering caching are also helpful suggestions, especially when dealing with performance bottlenecks.
However, I believe the core issue here is related to the expiration of the temporary result file URL provided by Databricks for large datasets. It might also be helpful to use Import mode over Direct Query when feasible, implement incremental refresh for large datasets, or consult with the Databricks admin team regarding the result file TTL configuration.
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you.