I have been getting below error randomly / intermittently, but frequent i.e. every after 3-4 days. I have just one pipeline that runs once a day only. In that pipeline I have one Stored Procedure activity that runs in the last and auto creates external tables based out of data-lake .parquet files structure.
"Execution fail against sql server. Sql error number: 42109. Error Message: The SQL pool is warming up. Please try again."
How to avoid this or fix this issue permanently ? Is there a way to add an intermediate activity (like via an API endpoint call similar to how we resume/pause SQL dedicated pools ?) to ping/initialize Serverless pool and wait until it's up & running and then run the SP activity ??
Of course, I can setup retry + retry interval settings in the SP activity. However, would like to understand why it's happening randomly and frequently and if there's a better way to handle it ? Had also checked Azure service availability (Synapse serverless pools) around same time of the error, but couldn't find any issues in any region.