I have a small db at my client site (SS2012,MS Server 2008) with an Access front end. It does some importing through Access (imports Excel workbooks created by the corporate server....) These are necessarily big, and they are replaced into a table on each import because the corporate server doesn't provide a key column. No big deal, I work through it, but I can't quite figure out why my log file is so big....
On Mondays, the log file should get big, because all the imports are run on Mondays. But then, every morning at 3 AM, I have a backup sequence that backs up the entire instance, then (I thought...) truncates the log files. Yet, here it is Tuesday and the log files are huge (twice the size of the db....)
My best guess is that I never truncate the space occupied by the logs, just delete the logs themselves.... I guess that's OK, but it seams like a lot of wasted space....
Log file...6330 MB, DB file...3682 MB
Backiup script (SQL Server Agent Job...)https://picasaweb.google.com/lh/photo/2rlN0nnxNR-sWWefPJZkudMTjNZETYmyPJy0liipFm0?feat=directlink