March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
Register NowGet certified in Microsoft Fabric—for free! For a limited time, the Microsoft Fabric Community team will be offering free DP-600 exam vouchers. Prepare now
Hello,
i run a pipeline that executes a stored procedure in my warehouse (same workspace) one time a day. Last week, i got the following error on two days:
Execution fail against sql server. Please contact SQL Server team if you need further support. Sql error number: 42109. Error Message: The SQL pool is warming up. Please try again.
does anyone know what this could be?
Thanks!
Solved! Go to Solution.
Hi @cw88
Thanks for using Microsoft Fabric Community.
Apologies for the issue that you are facing here.
The error you're encountering ("42109: The SQL pool is warming up") is likely a transient error, meaning it should resolve itself on the next retry attempt. Transitive errors are temporary issues caused by external factors outside your application or data pipeline. In your case, the warming-up SQL pool is a common example of a transient error. Retrying the operation after a short delay can indeed be a good strategy, as the pool should be ready by then.
Please refer to the below mentioned document for more details.
Document Link: MSSQLSERVER_42109
If the issue still persists please do let us know. Glad to help.
I hope this information helps.
Thanks.
I have the same problem, during a lookup-activity in a pipeline. Im Lookup to a Warehouse table, when i get the error message.
Hi @cw88
Glad that your query got resolved.
Please continue using Fabric Community for any help regarding your queries.
Thanks.
@v-cboorla-msft : Thanks for your reply.
I will try to fix it with the retry option of the pipeline activity.
Hi @cw88
Thanks for using Microsoft Fabric Community.
Apologies for the issue that you are facing here.
The error you're encountering ("42109: The SQL pool is warming up") is likely a transient error, meaning it should resolve itself on the next retry attempt. Transitive errors are temporary issues caused by external factors outside your application or data pipeline. In your case, the warming-up SQL pool is a common example of a transient error. Retrying the operation after a short delay can indeed be a good strategy, as the pool should be ready by then.
Please refer to the below mentioned document for more details.
Document Link: MSSQLSERVER_42109
If the issue still persists please do let us know. Glad to help.
I hope this information helps.
Thanks.
Hi @cw88
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.
In case if you have any resolution please do share that same with the community as it can be helpful to others.
Otherwise, will respond back with the more details and we will try to help.
Thanks.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
Check out the October 2024 Fabric update to learn about new features.
User | Count |
---|---|
3 | |
3 | |
2 | |
1 | |
1 |
User | Count |
---|---|
12 | |
10 | |
6 | |
5 | |
3 |