When doing restore we always get a new database ID, Physical Name and SqlEndPoint, even if the database logical name is the same (eg restore over the top). This causes a massive increase in RTO...
MDC70
Advocate I
Advocate IPlease enable the "Overwrite the existing database WITH REPLACE" functionality, as we know it from SQL Server. When a restore is performed into a different database, all references in the ETL might have to be adjusted - which is something nobody wants to deal with. Therefore, having the WITH REPLACE option would be very useful
StrahinjaRodic
Microsoft Employee
Microsoft EmployeeHi, MDC70, Thanks for the feedback!
We'd like to understand better this feedback and answering these questions would help us a lot:
- When you say "All references in the ETL" - do you need to restore over the existing database with the same name to preserve downstream ETL references or for something else?
- If restoring to a new database and renaming it was automated and seamless, would that meet your needs? If not, why do you specifically require true in-place overwrite?
- Would you be okay with permanently losing all data changes made after the restore point?
- What are your expectations around downtime and automation for this feature? Would you plan a maintenance window and manually restart ETL jobs, or are you aiming for a near-zero-downtime restore that seamlessly continues ETL without reconfiguring connections?
Thank you,
Strahinja Rodic - PM on Backup & Restore area on SQL database in Microsoft Fabric
