MysteryJimbo (9/11/2012)
This is why logshipping is a better method of migrating/update database server as there are no restrictions. Logshipping is also guaranteed not to have an impact on the production server where as mirroring potentially can in a high TPS environment.
Sorry, I may not be following you correctly. Do you mind elaborating your statement a bit more?
I do not see how Mirroring can affect during a migration. Assuming the login(s) were created already and SIDs reset on target, it may take just seconds to move the database. I actually done this myself several times with databases between 500GB and 1TB of size.
Both requires good bandwidth, for sure. On both, we need to re-create login(s) and reset SIDs, target instance. But after the Mirror failover, the db is up and running. Using Tlog shipping additional steps are required.
I see myself Mirroring as a Tlog shipping with steroids. And Tlog shipping more data recover oriented, like on a different data center as warm standby.