Forum Discussion
Warehouse data not refreshing when pulling from Lakehouse
- 1 year ago
Hi marius1106,
Based on my understanding, I recommend first copying the raw data into a Warehouse table and then applying T-SQL transformations using views or additional logic. This approach helps avoid delays associated with the SQL endpoint and ensures that you are working with the most recent data in a stable environment that is optimised for transformations.
Please note that Notebooks may fail, as T-SQL Notebooks rely on the Lakehouse SQL analytics endpoint, which can experience metadata synchronisation delays. These delays may affect timely access to data, even for existing tables.
Other alternatives, such as introducing wait or delay logic, may provide some relief but are not entirely reliable. Similarly, using a view over Lakehouse tables is a potential solution, but it may also be impacted by the same metadata sync issues.
If you find this response helpful, we kindly request you to mark it as the accepted solution and consider giving kudos. This will help other community members who may have similar queries.
Thank you.
Hi ObungiNiels
Between my data-loading process (to the Lakehouse) and the pulling-process from the Lakehouse there are 20 minutes. I dont know if its still the delay to create a table?
In my experience, it does also affect appended/supserted data in existing tables. Since the SQL endpoint is serverless, it doesn't update immediately and I've seen scenarios where the delays surpasses 20 minutes.
I'd give an API call to sync the SQL endpoint after ingesting data to the lakehouse a try. 🙂
- marius11061 year agoHelper II
Okay 🙂
Do I have the same Problem when I pull data from a Lakehouse using a Data Pipeline?