How can we improve Microsoft Azure SQL Data Warehouse ?

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.

63 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  AdminSQL DW Team (Feedback, Microsoft Azure) responded  · 

    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.

    12 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Nava Jeevan commented  ·   ·  Flag as inappropriate

        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.

      • Tarun Arora commented  ·   ·  Flag as inappropriate

        The blogpost from your collegues in Azure CAT implies that it's possible to restore SQL DW betwen Azure subscriptions. Which is wrong as it does not work the way the blob projects it does. Can I confirm that SQL DW restore across subscriptions isn't supported today and that this request currently being reviewed will likely enable this functionality?

      • Henrik Kure commented  ·   ·  Flag as inappropriate

        We also have a customer who needs better control over backups (more than 7 days and manual control).

      • Shekhar commented  ·   ·  Flag as inappropriate

        We are using 2 logical sets of SQL DWs with 2 SQL DW in each set. We loaded data in to one logical set in production. We want to take the 2nd logical set also to production and need to take back up of the 1st SQL DW and apply on the 2nd logical set of SQL DW. We need a quiet database backup so that the data is in sync in backup copy. We need the ability to request a back up. At this point, we have to stop production for 12-16 hours. The Production is 24X7 for us.

      • Aya commented  ·   ·  Flag as inappropriate

        My customers want to have a quiesce point of backup.
        Manual backup is required.
        They also want to check the cost of the backup.

      • joeyong commented  ·   ·  Flag as inappropriate

        Hi Greg, LTR and user initiated backup complement each other but also have distinct use cases. Would you kindly create a new suggestion specifically for LTR so we can track that? Thanks.

      • Greg Galloway commented  ·   ·  Flag as inappropriate

        There was a recent announcement of the Azure SQL Database Long-Term Retention feature. Maybe adding SQL DW support to that feature would accomplish this request?

        The current approach long term backup by restoring as a new DW that stays paused was a good idea until the premium storage switch. Now it's too expensive.

      • Patrick commented  ·   ·  Flag as inappropriate

        Currently SQL DW doesn't have the capability to specify longer term retention capabilities as released for SQL DB recently. It would be great to have this capability for compliance and auditing requirements.

      Feedback and Knowledge Base