Forum Discussion
Lakehouse SQL endpoint
As my issue is ETL / pipeline related, neither of that helps.
What I did now as a soloution until MS releases the API which frithjof_v mentions, is to use the "unsupported script" to update SQL endpoints written by somone at MSFT found here:
What I did, if someone is interested to:
- Rewrote the script to be a bit more robust, with some error handling etc.
- Created it as a wheel, uploaded in a shared lakehouse, call it "own modules".
- Shortcuted into "own modules" in every lakehouse where a notebook updates the data & a sql endpoint needs a refresh.
- At end of each notebook which updates lakehouses, i run the script with error handling & logging, so if the unsupported APIs in the script gets changed/stops working, it won't affect the pipeline run, but I will know from logs.
- Wait for the official API to come.
Best regards,
Alexander
As my issue is ETL / pipeline related, neither of that helps.
What I did now as a soloution until MS releases the API which frithjof_v mentions, is to use the "unsupported script" to update SQL endpoints written by somone at MSFT found here:
What I did, if someone is interested to:
- Rewrote the script to be a bit more robust, with some error handling etc.
- Created it as a wheel, uploaded in a shared lakehouse, call it "own modules".
- Shortcuted into "own modules" in every lakehouse where a notebook updates the data & a sql endpoint needs a refresh.
- At end of each notebook which updates lakehouses, i run the script with error handling & logging, so if the unsupported APIs in the script gets changed/stops working, it won't affect the pipeline run, but I will know from logs.
- Wait for the official API to come.
Best regards,
Alexander
Hi AlexanderPowBI ,
Thank you for providing your insights and workaround. For further assistance, please continue the discussion in the Fabric Community.
Regards,
Yugandhar.