In 2005 Standard Edition you get single REDO thread (Enterprise gives one thread per 4 CPUs) andSafety is always ON. On principal server do transactions wait for mirror to commit ? If network has unexpected latency do inserts/updates/deletes on principal experience problems? Would inserts take much longer, with rows locked until mirror responds ? Is that 10 seconds maximum ?
Your question are covered in Microsoft article below http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx Regards Sat
To addup more: http://msdn2.microsoft.com/en-us/library/ms187465.aspx and in case you are worried about latency, you should continue analyze the network between principal and mirror. Also better to keeup the transactions in smaller batches for a better commit process. By default all the transactions are constantly being applied to the mirror when you are running Database Mirroring. Instead of spawning multiple threads to handle this, there is a single thread allocated on the mirror to handle the inbound transactions from the principal.
