GilaMonster (3/27/2012)
Since you're bringing the secondary DB online and making changes, there's no 'go back' after that.
Are you sure? This was something I had done previously (SQL2000 admittedly) with a customised log shipping solution.
Backing up the last transaction log at the primary using WITH NORECOVERY and then restoring that on the secondary keeps the LSNs in sync. That allows you to you to start backing up at the secondary and restoring them at the primary.