Hourly Transaction Log files size not consistent – is this Differential backup file?

All we need is an easy explanation of the problem, so here it is.

I am new to DBA task here.

I am trying to restore database with transactional logs (in SQB file format) that our company get 24 times each hour daily thru FTP site, and then I have to convert them to BAK file format using "RedGate’s SQL Backup" application.

Then, I am planning to restore each transactional log with "NoRecovery" as we would have to restore each hour.

I found there is a pattern of file number "..04" which is really big compared to other hourly transactional logs.

I did not get specific instruction regards to this file "..04" from the vendor’s documentation who provides data.

Hourly Transaction Log files size not consistent - is this Differential backup file?

I am curious whether I should treat this particular file as a regular transactional log or is this like "differential backup file" that I have treat it differently?

How to solve :

I know you bored from this bug, So we are here to help you! Take a deep breath and look at the explanation of your problem. We have many solutions to this problem, But we recommend you to use the first method because it is tested & true method that will 100% work for you.

Method 1

It’s more likely that the log backup occurs after some processes that generate a lot of log records, like index maintenance or any ETL-ish tasks.

You may find some benefit in increasing the frequency of your log backups to every 5-15 minutes so that internal truncation occurs more frequently, since that will likely make the backup size smaller.

Note: Use and implement method 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply