SQL Server 2005 log file maintenance in a mirrored environment

  • I have a SQL Server 2005 mirrored environment(Principal, mirror and witness). Periodically I truncate the SQL Server log files(*.ldf). When I attempt to do this to a mirrored database it fails. To perform this regular maintenance on a mirrored database do I have to break the mirror and them re-enable?

    TAS/10.

  • Why are you truncating the t-log's? You should be running periodic t-log backups to manage the size of the t-log files.

  • I do have maintenance plans that take transactional backups every 30 minnutes but the *.ldf file continues to grow.

    Please be patient with me. I am an Oracle dba that inherited several SQL Server 2005 servers.

    TAS/10.

  • The problem with truncating the t-logs is that it breaks the log chain. What other processes are running on the servers? If you are running t-log backups, they shouldn't continue to grow unless they are simply to small for the amount of activity between t-log backups or you have other processes running that is keeping the inactive log records around, such as replication.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply