WITHERELLScott-6986 avatar image
0 Votes"
WITHERELLScott-6986 asked NavtejSaini-MSFT commented

Azure SQL Managed Instance - General Purpose Gen5 (256 GB, 4 vCores) Cold Start Delay

I have a SQL Managed Instance (General Purpose Gen5 (256 GB, 4 vCores). I want to know if this database has a "Cold Start" delay on the first query after some idle time. If so, How can this be prevented. It sometimes takes over 1 1/2 minutes to return the first query after some period of inactivity. After that first query request comes back in seconds.

In my setup I have an AppServce API making calls to the SQL Managed Instance. We need to find a way to keep the database alive and responsive at all times. Is this possible. If so how would I do it?

Scott Witherell

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

NavtejSaini-MSFT avatar image
0 Votes"
NavtejSaini-MSFT answered NavtejSaini-MSFT commented

Hi Scott

We did check the policy regarding Cold Start with our product group(PG) team and conveyed this should be inspected.

They have suggested to open a support ticket which will be either resolved by CSS team or escalated to PG on-call engineers.

Please do raise the same which will provide insight into your Azure resources and share the SR number so that we can follow up with them to expedite the SR.

Navtej S

· 7
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

The SR is 120060124008247

0 Votes 0 ·
pituach avatar image pituach WITHERELLScott-6986 ·

hi @WITHERELLScott-6986,

Obviously opening a ticket will let the team the option to examine the specific subscription and track any issue if exists in the Azure side...

With that being said, the issue sound very common and i had multiple (tans) or calls from clients about the same issue without any relation to Azure Managed Instance but with all type of databases. The issue which is familiar to me and fit the description is in the application side. Meaning it is not the database that "sleep" but the service of the application (for example the IIS) which sleep

I see no point in your description which point to an issue in the database. Please confirm that this happen if you try to connect to the database using SSMS or only when you use your application. My guess at this time (without any base) is the the issue is not related to the Azure SQL Database but to the application - in this case we can solve it fast (probably)

0 Votes 0 ·

For example IIS has built-in configuration to make the Application Pool alive: Open IIS Manager and browse to Application Pools. Right-click on a particular Application Pool and click Advanced Settings. In the "Process Model" section, change "Idle Time-out (mintues)" to a value of your choice. A value of 0 will disable the timeout.

0 Votes 0 ·

This is a Azure SQL Managed Instance. I don't think IIS is involved at all. This is a PaaS.

0 Votes 0 ·
Show more comments

Thanks for sharing. Checking more regarding this.

0 Votes 0 ·