Please add ability to temporarily turn off/on SQL Azure server to pause billing for both the primary service admin and delegate admins.
Please add the ability to temporarily turn off/on SQL Azure servers to pause and re-enable billing for both the primary service admin and delegate admins. Make SQL Azure a truly Pay-As-You-Go service.
Thanks for your feedback here. I think we have several ways to achieve what you are looking for.
One is to use the import/export service to export a copy of your DB to blob storage, and another is to change the service tier to Basic to minimize your bill.
I’d love to learn more about your request, if these two options don’t work for you.
Peter de Wit commented
Reading all these Azure SQL database questions makes me very sad. Microsoft asks their users how to improve Azure SQL databases, but when users supply reasonable options, the answer is "it is supposed to work like this", or "By design" or this answer "you can do it this way". This way?? That's totally not what I am asking for, did you really read my question?
Billing is one of the most important parts to keep in mind when using PaaS. Scaling down is definitely not the option in all cases and exporting / importing large databases is really a bad (non workable) suggestion.
Too bad the questions are closed and votes are useless cause of this stupid behavior.
Import/export is not a useful option when we have DB size in Terabytes. Even the basic service tier will not help to has the cost. let's take an example of Legal Host assets where users need DB only for 1 or 2 days up and running the rest of the month it can be shut down.
MI is Amazon RDS is the same but we don't have support Stopping and Starting of Database Instances in Azure. FYI please refer to the Amazon doc. As per my understanding, Azure could introduce the same feature which would help customer to same cost
Another +1 to this feature request. Microsoft markets Azure as "pay only for what you use". We should be able to stop a SQL server, so we only pay for the compute when we are using it.
PS -- the workaround you proposed takes too much time every time a development or test server is stopped / started. This feature request should be implemented just like App Services and VMs are. Simply turn it off.
Hichem BOUSSETTA commented
+1 for this feature. current resolution is not acceptable!
I also disagree with the "resolution". Exporting DB and then re-importing it has its limitations and disadvantages compared to just pausing the serverless SQL DB. I can understand that you still charge certain amount to keep the serverless DB in a "hybernated" state, that is OK.
What I dont understand why when 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.
has this feature been enabled?
I had to delete the one created for POC and had to change my idea of moving to Azure SQL.
Fabiano Simões commented
This is not acceptable. What if I am building my app that will make money for me when going live? What if I depend on that money to pay the services hired with you guys?
This is very bad for developers, as we will surely look for another better way to develop our databases and, when it is ready for shipment, probably won`t look back to choose an Azure SQL Database. We will have everything ready and this product will have no chance to be chosen.
Bad strategy of Microsoft.
LEGRAND Julien commented
Please re-open this request, you cannot leave it this way.
This is the way MS operates. Pathetic , Azure in total should be a well oiled solution and ready to be Productionized. Since working with Azure we had to do so may Workarounds in Blob Storage , Data-Factory, Event-Hub and now Azure SQL , Clone of DB to another does not work properly , Database Security is a joke ( depending on the day the model changed and suddenly you have to redo privileges or drop login and user and recreate to get it to work ) etc... the list goes on and on ..
An now I cannot stop a Azure SQL DB to save cost .... and the response from the "Principal Product Planner" .... Just not good enough.
Busy investigating alternatives. No Way I'm risking my business on a Product that's build on workarounds etc.
This has not been solved so why is this closed?
Dumitru Ozunu commented
Hi, we need this feature for Azure SQL Database (PaaS) and also Azure SQL Managed Instance. Azure SQL Datawarehouse supports this feature, so why not also SQL Database?
I wouldn't consider this problem solved - I completely agree with Joe Martin's comment
as it does not matter whether you are charging or not. (for development purposes)
This official Microsoft response is a joke to all of us developers of its technology! that's how they treat us!
Joe Martin commented
This is a very poor setup. I'm paying $80/month for a test/demo environment that gets used 24-48 hours per month. AWS provides an easy way to shut these down and you only pay for static resources like storage, elastic IPs, NAT gateways, etc. That usually comes to around $5-10 for me. That makes a big difference to a startup which is already running on razor thin margins.
I prefer Azure. It's simple and it works, but this needs to change if you really care about your customer.
Fernando Hidalgo (SWBI) commented
This is the reason Snowflake is waaaaay better than Azure SQL or Azure DW.
3 years passed by and there is no decent option on Azure to pause a database
John Staveley commented
This is a great idea and the MS solution is not acceptable. Customers should be able to pauses charging and pay for storage of their data only
this really needs a good solution. Why shouldn't we be able to turn off an Azure MySQL server? Either let us pause for free, or reduce cost to less than $5 / month for a server that is active for only 24 hours a month.
Ian Newson commented
There definitely should be an easy way to pause billing for databases. Deleting and recreating the database is NOT the same thing.
The ability to pause resources and associated compute billing should be built into all Azure services. As someone else mentioned, being able to click 'pause' on a complete resource group is the most user friendly solution.