Azure SQL PiTR - Option to disable or set to 1 day retention
We currently have an SQL managed database, which we use for development purposes.
We are developing how our data ingest will work, currently we drop the tables every day, and re-load all the data. As of the 31-AUG we started getting charged for PiTR which we didn't know about, until PiTR started costing us upwards of $120 per day.
What I found out is after the initial backup (free) any changes were replicated to 6 regions (GRS storage) and set to 35 days retention period. These are backups we don't want or need, as data is ingested from the Datalake. Currently there is no option to turn this feature off, and the min number of days retention is 7 days.
Cloud being pay for what you use, and use what you want. There is no way to avoid these charges, unless we pay for provisioned SQL via the DTU model where PiTR is not charged. But we are using the serverless feature of vCores.
Please provide an option to turn off PiTR or set it to 1 day.
Anonymous
shared this idea
Thank you for the feedback. We are planning to relax the minimum retention from 7 days to 1 day.
8 comments
-
Brian McAuley
commented
This is a prohibitive problem for us as well. What is the anticipated timeline?
-
Matt Chance
commented
We are eager to see this option implemented as soon as possible.
-
tunbridge wells taxi
commented
You can get our taxi organization for whatever time span that you need in a day at hourly rates (least 4 hours booking required). Day secure organizations spread all territories inside central London in a manner of speaking. It is the most adored and supportive way for voyagers.
http://www.twexpresscars.co.uk/ -
Anonymous
commented
Any updates on when this is Planned/Scheduled for?
-
Danny Diaz
commented
we are waiting this option in place to save costs and avoid the space use in non-production data.
-
Austin Deal
commented
Thank you for the feedback. We are planning to relax the minimum retention from 7 days to 1 day.
To give some additional context on why the minimum is 7 days: in order to perform point-in-time restore, a full backup is required followed by a sequence of log backup(s). If a differential backup is relevant to the requested point-in-time, the service will utilize it in order to reduce the time of the restore operation.
Azure SQL DB takes automated full backups of each database every 7 days which limits the minimum retention that is allowed to be configured.
-
Will
commented
this setting will benefit MS by not having client store data on MS infrastructure servers saving valuable space for those clients that need it, and benefits the client who doesn't want to do backups at all and save the cost. Only reason I see this strict setting is currently in place is to withdraw as much money from the client as MS can.
-
Nigel Rablin
commented
This is important to have the option. For our non-production workloads this is costing us when we really do not need to recover at point in time. For production workloads we also need the option to decide whether each database is important enough to keep a PIT.