Sudhir Dwivedi (9/20/2011)
Your question is quite unclear.
1. What do you mean by pausing?
2. Read from this section from BOL:
If database mirroring is removed completely, the mirror database is in a recovery state and must be restored in order to become functional. The behavior of the recovered database with respect to replication depends on whether the KEEP_REPLICATION option is specified. This option forces the restore operation to preserve replication settings when restoring a published database to a server other than that on which the backup was created. Use the KEEP_REPLICATION option only when the other publication database is unavailable. The option is not supported if the other publication database is still intact and replicating. For more information about KEEP_REPLICATION.
What I mean by pausing is if you run the below on against a mirrored database.
ALTER DATABASE DatabaseName SET PARTNER SUSPEND;
Granted I should have used the word suspend instead of pause.
As the mirror partnership is not synchronised and running in High-safety mode without automatic failover - See the below from BOL from the link i provided with the answer.
All committed transactions are guaranteed to be hardened to disk on the mirror. The Log Reader Agent replicates only those transactions that are hardened on the mirror. If the mirror is unavailable, the principal disallows further activity in the database; therefore the Log Reader Agent has no transactions to replicate.
It is this that the question is refering to. This is however assuming that you haven't enabled trace flag 1448 ;-)
I am the master of my fate:
I am the captain of my soul.