How safe using Azure Managed SQL database with auto-pause option?

[keremkambur]

Greetings,

we have an on Production CMS solution powered by Umbraco and we are currently quite happy. MS SQL is a great database but also not the cheapest one. Especially in managed cloud solutions, prices are even higher. Meanwhile, Azure also aims to help reducing costs when the resources have lower traffic or idle. Azure SQL offers an option called auto-pause. In serverless model, when there is no activity on DB for a predefined amount of time (minimum is 1 hour). However, waking up a SQL instance is not as seamless as spinning up applications. Microsoft documented expected timeouts and exceptions to be thrown by database adapter. Please see here for the expected behavior and recommended retry logic for database connectivity.

We currently avoid using auto-pause because we can't foresee its possible effect on

• SQL distributed cache
• Umbraco's behavior on first failure on auto-resuming

What is your opinion? Should we prevent auto-pause or is it safe to go with it?

[bergmania]

I have never tested, but I would expect the background jobs to keep it running anyway. Umbraco have background jobs checking for scheduled publish and the distributed cache instructions. Those run way more often then the minimum 1 hour.

[keremkambur]

Thank you for the reply, I guess it wouldn't make sense to enable it. Hope one day soon PostgreSQL will be supported as well 🤞

[nul800sebastiaan]

Thanks for the question but do note that the Discussions section is only meant for raising feature requests. Questions on how to use Umbraco should either go to:

• Our forum: https://our.umbraco.org
• The Umbraco Discord Server: https://discord.umbraco.com

Additionally bugs can be reported on the GitHub issue tracker: https://github.com/umbraco/Umbraco-CMS/issues

Thanks!