I have a log shipping pair set up which is great for cataclysmic failure of the primary machine however I wish to perform a point in time restore on the Primary machine and see that reflected on the secondary.
Eg. If a developer mistakenly removes a table which them gets shipped to the secondary unnoticed.
When I've tried this it seems the secondary server does NOT restore any logs after you restore the primary as the transaction log sequence is out of order.
Is there a quick fix around this apart from either:
1. Restoring the secondary from same backups I used on the primary
2. Deleting the secondary database and running the entire Database Maintenance Task wizard to restart the process.
Thanks