Should we periodically 'refresh' the mirrored copy of a SQL Server database? When you have SQL Server mirroring set up, do you trust that your mirror database will stay the same as the primary, even after months and months of mirroring?&nbsp; I know we all check the status, and of course it says the database is synchronized...&nbsp; but I worry that somehow the mirror might fall out of sync due to network glitches, software bugs etc. and the fault won't be detected.&nbsp; Then one day we need the mirror and we're horrified to learn that it's corrupted.

One thing I could do is periodically refresh the mirror from the primary, since our database is not terribly large.&nbsp; But perhaps I'm being overly paranoid.

I would like to hear from DBAs, either of SQL Server or any other platform, as to whether you share this concern about the integrity of mirror DBs, and if so, what you do to mitigate that concern.&nbsp; Do you occasionally re-copy your primary DB over to the mirror?&nbsp; Do you take other measures to ensure consistency between the two?&nbsp; Thanks for any advice you can provide.
I don't trust mirroring 100%, but I do trust it about 99%, same with everything else. It never hurts to periodically check your mirror database and DR scheme. We test our DR plan across the board several times a year, and it would not hurt your scenario to set aside a DR test time and simulate a failure of your primary database to fully test the mirror if you have concerns.