Allow SQL databases to be shutdown
Now that we can shutdown SQL Data Warehouses I'd like to be able to shutdown a SQL database. Even if there are multiple SQL databases on a server, I'd like to shutdown the databases individually since that's what I'm charged for. Just like with VMs I would expect to only be charged for the storage when the database is shutdown.
As a bonus, shutting down the entire SQL Server would be great too, but I really only care about shutting down a database.
With the introduction of the serverless option, you can have SQL DBs be paused when not in use.
I have a serverless SQL DB of 1 table and 1 row, and I dont connect to it for a week, I still see plenty of CPU activity charges every day.
I could imagine neccessary maintenance and optimization jobs, but 1 table with 1 row, charging at 5-10$ daily for a serverless SQL DB that is not used? I cannot justify that.
I can understand that you still charge certain amount to keep the serverless DB in a "hybernated" state, that is OK. But then there should not be any CPU charges.
Can we have an update on this suggestion please? Its been under review for more than 2 years now. It will be great to have this feature especially in lower environments (DEV, SIT, etc) to keep the costs down.
Chris Bailiss commented
Exporting/importing is a killer. It fails after running for several hours, about one in four times recently, forcing the whole thing to be done again.
Frankly, I don't see why we should have to push the data temporarily to a logical format and then re-import it. Slow, inefficient, , inflexible, expensive.
Johan Bennink commented
Could be made similar to Take offline for a database
Matt Moore commented
We have dev and test databases we want to turn off easily, and just pay for storage, just like a VM. It would be great if MS can add this ability rather than having to go through exporting/importing every time we want to use the DB's.
Jeff Dodds commented
I too would like to see this and just came from two related feature requests, one of which was falsely stated as completed via the availability of import/export to blob storage and another that was flat out denied.
Thank you for taking the time to post this suggestion. This suggestion will be reviewed and discussed for a future planning cycle. If the proposed change meets the bar for approval, I'll provide an update on the status in this User Voice item.
Joe Sack, Principal Program Manager, Microsoft