Trouble with differential backups
This would seem to indicate that somewhere I am making 40GB worth of changes between Friday's FULL and Saturday's DIFFERENTIAL but my next FULL will have only increased by 6-7GB (what I expect.)
I have searched and searched and I cannot find any jobs that run only between Friday & Saturday that would cause something like this. My reindex job runs and completes before Friday's FULL backup.
The only thing I have left is to try to examine the DIFF file backup and see what changes are listed (does anyone make a tool for this?) or to cross my fingers and hope that this is a known bug with my version of SQL Backup and only happens on databases larger than 150GB (quite a bit of a longshot.)
Can it be possible that I have to run a transaction log backup after my reindex job and before the FULL backup? I thought that DIFFERENTIAL backups only rely on extent changes within the database and don't read anything from the LOG. Can it be possible that unflushed transactions are causing the database to retain those extent modifications?[/b]