transaction log space issue in mirroring? RRS feed

  • Question

  • In mirroring in principle  database if transaction log size reached to 99%  what happens?
    Monday, February 21, 2011 2:35 PM


  • when it comes to out of space issue then mirroing will get into suspended state . In order to avoid this scenario do a regular log backup and have a statergy in place .

     Database mirroring transfers transaction log records directly from one server to another and can quickly fail over to the standby server. The transaction log records are placed first in a database's log buffer in memory, and then flushed to disk (or 'hardened') as quickly as possible. In database mirroring, as the principal server writes the principal database's log buffer to disk, it simultaneously sends that block of log records to the mirror instance.

    Can you please post all your one linear questions in a single post ! In this way you will have the answers answered in a single thread .

    Thank You

    Thanks,Suhas V

    Monday, February 21, 2011 4:59 PM