Due to some inactivity, built-in serverless pool goes inactive and comes to active when next activity happens. However, this gives us sql warming up error. MS documentation says, we need to apply the retry mechanism. Where should we use this retry policy?
we have a copy activity which takes data from serverless and moves it to onpremises. Should I set the retry policy at linked service connection string or copy activity retry policy?
I feel setting at copy activity won't work as it will retry irrespective of the error. And also, we tried setting at linked service, which also didn't work.
Is there a way to check the status of serverless pool status (like active, inactive) from synapse pipeline before the linked service connection establishment.