locked
High TempDB Usage for DB Mirroring Monitor Job RRS feed

  • Question

  •  

    We occassionally see a phenomenon with the database mirroring monitor job where it will run for an excessive length of time, usually over 5 minutes, and consumes many gigs of tempdb log space.  In several cases this has caused tempdb's log to fill, and subsequently the db mirroring monitor job will fail.  On the next run of the job, it's back down to sub-second run times.

     

    The servers we've seen this on are on SQLServer 2005 SP2.

     

    Has anyone encountered this condition?  Is there any explanation for this behavior or any way to prevent it?

    Friday, November 21, 2008 4:10 PM

All replies