Azure Synapse SQL pool is warming up error

Burak YOLERİ 20 Reputation points
2023-08-09T11:12:21.18+00:00

I created a pipeline package on Azure Synapse and set it to run automatically every day. But this stream is getting an error on the first CopyData step. I am sharing the error code below. By the way I am getting this error both in dev environment and live environment. The db in the live environment never shuts down. So I do not apply a resume pause. In the dev environment, I set it to run the stream after I resume. In both cases I get the same error. When I run it again as soon as the error is received, things work without error. What can I do as a suggested solution?

Error:

Operation on target 'MyTableName' failed: Operation on target Copy data1 failed: ErrorCode=SqlFailedToConnect,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Cannot connect to SQL Database. Please contact SQL server team for further support. Server: 'tryksynapse-ondemand.sql.azuresynapse.net', Database: 'trykods', User: ''. Check the linked service configuration is correct, and make sure the SQL Database firewall allows the integration runtime to access.,Source=Microsoft.DataTransfer.ClientLibrary,''Type=System.Data.SqlClient.SqlException,Message=The SQL pool is warming up. Please try again.,Source=.Net SqlClient Data Provider,SqlErrorNumber=42109,Class=20,ErrorCode=-2146232060,State=1,Errors=[{Class=20,Number=42109,State=1,Message=The SQL pool is warming up. Please try again.,},],'

Azure Synapse Analytics
Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
4,473 questions
{count} votes

Accepted answer
  1. BhargavaGunnam-MSFT 27,656 Reputation points Microsoft Employee
    2023-08-09T18:24:58.2+00:00

    Hello Burak YOLERİ,

    Welcome to the Microsoft Q&A forum.

    The start-up time for SQL Pool includes recovering all databases.

    You will see this error when you connect to Serverless Pool after a long period of inactivity. It can be a week of inactivity or less; there’s no specific time this can happen. This is the reason for the error message in the first run.

    The more databases you have, the warm-up time will be longer.

    I hope this answers your question.

    Please let me know if you have any further questions.

    1 person found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful