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...
When we restore a Fabric SQLDB it changes the database names which break the ETL and all customers connecting to it.
We then have to ge everyone globally to change the connection string, which means a restore has customer downtime of days.
Can you fix this so that a restore keeps the original database name and doesnt break the connection string ?
Ideally a restore shoudl restore "as was" unless we choose to restore to a different Artefact Name or workspace.
- akatesmith
Microsoft Employee
Status changed:NewtoUnder Review
