Invoke-DbaDbLogShipRecovery enhancements...

[Crucial2K]

Invoke-DbaDbLogShipRecovery has missing features.

invoke-DbaDbLogShipRecovery only checks for a recent copy of a transaction log before recovering the target. To have a more complete tool ideally there should be options to:

• Take a final tlog backup;
• Copy/restore the final backup to the target;
• Once complete disable transaction log shipping at the source (therefore include the target) and delete all LS% jobs.

[sanderstad]

The command was originally written for the situation that you have to fail over because the primary is not available.
I wonder in which situation you would want to use it in a way that the primary is still active? Maybe in a migration scenario?