September 20, 2021 at 4:52 am
Good Morning,
I have read that taking a log backup truncates the log file. In Log shipping, we set up automated log backups. So, my doubt is whether these log backups also truncate log file?
September 20, 2021 at 6:57 am
If you have a database in a logshipping configuration you must stop all other log backups from happening, otherwise you break the log chain and logshipping fails.
If you are using Ola's scripts, they will automatically exclude anything in a logshipping config.
September 20, 2021 at 8:51 am
This was removed by the editor as SPAM
September 20, 2021 at 8:51 am
This was removed by the editor as SPAM
September 20, 2021 at 5:11 pm
Not quite - the transaction log will be truncated after a log backup has occurred *and* there are no open transactions in the previous VLF's. The log also cannot be truncated if you have an availability group - and the transactions have not been hardened on the secondary.
If your question is related to the size of the transaction log then you should know that truncation <> shrink, meaning the log file will not shrink upon truncation. All truncation does is marks a VLF as reusable within the file and SQL Server rolls over to the beginning of the file once it gets to the end. If all VLF's are in use when SQL Server fills up the last available VLF - then the transaction log will grow.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply