Question 800
An Azure SQL operations team investigates: A restored SQL Server VM database remains in restoring state after all planned logs because final recovery was not issued. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The reported Azure SQL or SQL Server condition is: A restored SQL Server VM database remains in restoring state after all planned logs because final recovery was not issued. The specific supported administrative response is: Apply SQL Server backup restoration in the correct full, optional differential and transaction-log order, using NORECOVERY until final recovery. The technical risk is: Recovering the database too early or restoring an incompatible log backup can prevent remaining backup application. Confirm the correction with: A rehearsed restore applies the intended complete backup chain and opens the database only after final RECOVERY.
The acceptance evidence for this incident (A restored SQL Server VM database remains in restoring state after all planned logs because final recovery was not issued.) is: A rehearsed restore applies the intended complete backup chain and opens the database only after final RECOVERY. It directly tests whether the remediation (Apply SQL Server backup restoration in the correct full, optional differential and transaction-log order, using NORECOVERY until final recovery.) solves the specified issue, instead of proving an unrelated database control works.
Incorrect Answers
Native SQL server full differential and log backups (5.2) addresses another technical failure: An incomplete log chain or wrong recovery model can prevent recovery to the desired point after a failure. The case states: A restored SQL Server VM database remains in restoring state after all planned logs because final recovery was not issued. The most direct paired action and test is: Apply SQL Server backup restoration in the correct full, optional differential and transaction-log order, using NORECOVERY until final recovery.
Azure SQL database active geo-replication (5.3) addresses another technical failure: An asynchronous geo-secondary may lag behind the primary and individual database failover does not automatically coordinate a multi-database application. This choice can be useful for that problem, but it does not establish the Native restore sequence with norecovery and recovery (5.2) control being assessed here.
Monitoring replica health and lag across ha dr (5.3) would demonstrate or implement: Telemetry and a safe failover exercise demonstrate acceptable replication delay, data consistency and application routing. This case instead tests Native restore sequence with norecovery and recovery (5.2); the choice measures or changes another part of the system.