Forum Discussion
Immense SQL endpoint lag with external data share
Have you had a look at the latest blog post from Mark with regards to only being able to sync certain tables via a notebook? I think this might help your situation due to the fact that you do not have to wait for the sink for the entire lacasse, but you can do it for specific tables. Another thought is also to make sure that you are doing the maintenance on your lake house tables as that potentially there could also be another issue as to our the sink is taking so long.
https://medium.com/@sqltidy/md-sync-just-got-better-refresh-only-the-tables-you-want-dd17f8410ec1
Hello and thanks, good tip. Refreshing specific tables works and is faster, albeit only proportionally. One table ~40s, the whole 16 necessary in 7min, all in all we have maybe 200 tables mirrored/shortcut-linked; these are small tables!
We can't do lakehouse maintenance, because the source is a mirrored lakehouse where (as far as we know) this isn't available.
While the refresh runs, there are a lot of warnings(?) like this:
