User Defined Retention Periods for Restore Points
SQL DW doesn't have the capability to specify longer term retention capabilities as released for SQL DB recently. The workaround is to restore and pause. It would be great to have this capability for compliance and auditing requirements.
Thank you for voting for this feature! We are aware of this scenario and are looking into ways of supporting this. In the meantime, stay tuned for an update and please continue voting for this feature.
Vivek Appala commented
Please provide us the option us to enable Long term retention on Azure Synapse Analytics and Point in Time Restores to 5 minutes as a standard.
John Gult commented
Please allow longer retention
Yes, we need to be able to retain the restore points for longer periods of time than just 7 days.
we want to be able to change the number of days to keep the restoration point.
Christopher Reeves commented
Please allow retention periods to be expanded, or native plug in and support for Recovery Service Vaults
Is there any update or any progress on this ? we would like to have same retention period as Azure SQL server.
Eldho Baby M commented
yes we would like to have longer backup policy at least 30 days for Azure DW
Christopher Mendyk commented
Any progress ? It's a huge limitation when you need to comply with 30 days of daily backup retention policy.
We would like to have max 28 days of retention period fro SQL DW and it should be changeble, thanks!
Masti, Chad (EXT - US/Naperville) commented
YES we would like to have this feature available to us to be able to comply with auditing requirements (SOX, et.al). Such as retaining End-of-month RestorePoints taken monthly every month and retainable for a rolling 3 month period and a final EOY RestorePoint taken and retainable for 13 months until the next new EOY backup kicks in. So forth.... any chance this is coming down the pipe anytime soon? And any suggestions on how to estimate its costs? Until then...any tips on how folks are tackling this situation today, to comply today?
32 days would be great (to cover a month end)
15 days would be much better than 7 days. For weekly processing you may not pick up a problem early enough to know you have a problem.
32 day would cover end of month processing :-)
for our policy the retention is 2 weeks
Vikram Sahadevan commented
Most of the enterprise customer backup policy would be 30 days , if back up retention gets increased then it would be helpful.
Azieb Araya commented
This is such a big limitation compared to Azure SQL. Having a minimum of 30 days backup retention will be great. Also, Adding the long term backup retention similar to Azure SQL is great to have.
Any updates to this feature?
Arun Kanakaraj commented
We would like the option to save more restore points atleast two months worth. As per business requirement.
capabilities to keep the restore point as customers requirement
Debananda Ghosh commented
My customer looking for it in Singapore
Nava Jeevan commented
Currently, we are seeing a major data issue on our production SQL Data Warehouse. Business Analyst team is so confident that this issue did not exist in production 3 months (June) ago. Between June and now we have done 2 major enhancements for adding additional attributes to the DWH. BA team strongly believes that one of the releases may have caused the current data issue. If I get the database backup files prior to those 2 releases then I should be able to validate it.