Forum Discussion
Continued ContributorSQL Endpoint lakehouse: Intermittent error in the Refresh SQL analytics endpoint activity
Thank you for all the responses, going down the full api/notebook route is too much of an overhead for us at the moment. It would require us to set up a service principal, api keys etc, which we (don't) have (yet) (very small team :-) )
We do know from experience that a 5-minute wait in our pipeline, though ugly, solved the issue. Endpoints would have synched by then.
(The only time that did not work flawless was on 1 pipeline that ran at 130 am in the morning, when the lakehouse was well deep asleep. I solved that by running a dummy script against the endpoint...select top (1) from etc etc.
With that in mind I would think that (in our situation) "on completion" would be safe?
CheersHans
Continued ContributorThank you for all the responses, going down the full api/notebook route is too much of an overhead for us at the moment. It would require us to set up a service principal, api keys etc, which we (don't) have (yet) (very small team :-) )
We do know from experience that a 5-minute wait in our pipeline, though ugly, solved the issue. Endpoints would have synched by then.
(The only time that did not work flawless was on 1 pipeline that ran at 130 am in the morning, when the lakehouse was well deep asleep. I solved that by running a dummy script against the endpoint...select top (1) from etc etc.
With that in mind I would think that (in our situation) "on completion" would be safe?
Cheers
Hans