June 17, 2013 at 4:20 pm
Hi, hoping someone with some experience can help me to decide what to do with the log of an AlwaysOn secondary database.
We are backing up the primary database including its log file but the active read only secondary which is used only for reporting has a log that keeps on growing. I can't set the secondary to simple recovery so I can't shrink the log. I don't want to do log backups on the secondary as we are already backing up the primary. I noticed this issue when the log for the secondary filled the entire drive.
Is there a solution to this?
June 18, 2013 at 6:00 am
The transaction log of you seconday database is a reflection of your primary database.
Shrink the log on the primary database and it will reflect on the secondary database.
That being said, the best and preferred method to approach this is to maintain a decent sized log of the primary by regular log backups etc..
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply