Am log shipping a large, busy DB from server A (primary) to server B (secondary).
Nightly backups are taken, as well as diffs every X hours, and transaction logs are shipped and restored every 15 mins.
Occasionally I need to dry-run a script on server B, to assess it's impact, before running on server B. Script is often DDL.
I do this by taking server B out of RESTORING mode by manually executing a restore command on a recent transaction log, and testing the script.
However, to then resume log shipping, I have to restore the most recent full db, and diff, before log shipping can resume. This is very time consuming.
On server B, is there any way to instead effectively rollback to a previous transaction log (before I tried the script), and then resume log shipping?
Many thanks
WITH STANDBY = 'c:\blah\MyStandByFileLocation.utf'
docs.microsoft.com/en-us/sql/t-sql/statements/… – Sean Gallardy - Retired User Jan 21 '18 at 15:56