I have instituted this process for building a framework to migrate a production database from SQL2000 to SQL2005 without interupting production. Allowing us to test apps and connections 'offline' and then cutover at a planned point in time with a final transaction log restore.

Conceptually, this process is a perfect fit. In practice, everything appears to be working except for the last step. The 'DataMirror' is stuck in restoring mode. Is this what should happen? The dbDataMirror database indicates the bak was verified and applied, then the subsequent trn files. The job fires off every set interval. Why would the destination db still be restoring?

Any help would be appreciated.

Thanks

-Chris