Comments
Sort by recent activity
Ok, thanks. I'll try that! / comments
Ok, thanks. I'll try that!
Or so I thought ... the log is now back to 3.6 GB!? I've also run a transaction log backup via RedGate SQL Backup again as a test right now and the backup file itself is only 101 KB (the previous backup of the transaction log was an hour ago ... its size is 660 MB though!)
Here are the sizes of the last 10 transaction log backups (in KB; and I'm backup up every two hours during work hours):
101
652697
559566
643
109
367
166
76
121
1404
Some thing still seems wrong ... argh, this transaction log is driving me crazy!?
Anything else I could try?
Cheers!
Jerome / comments
Or so I thought ... the log is now back to 3.6 GB!? I've also run a transaction log backup via RedGate SQL Backup again as a test right now and the backup file itself is only 101 KB (the previous b...
Yes, I have and it works fine! Thanks again. / comments
Yes, I have and it works fine! Thanks again.
Size of the DB: 3.4 Gb
Size of the transaction log (currently): 25 Mb (the 2-hourly transaction log backups vary between 4 and 250 Mb)
SQL Server 2005
DB initial size: 3.3 Gb - autogrowth: 10%, unrestricted
Log initial size: 25 Mb - autogrowth: 10%, unrestricted
Full backup once a night
2-hourly log backups
Thanks for your help! / comments
Size of the DB: 3.4 Gb
Size of the transaction log (currently): 25 Mb (the 2-hourly transaction log backups vary between 4 and 250 Mb)
SQL Server 2005
DB initial size: 3.3 Gb - autogrowth: 10%, unr...
Thanks Chris,
So backing up the transaction log using RedGate Backup regularly will keep the log size down automatically?
How would I better size a transaction log then?
Cheers,
Jerome / comments
Thanks Chris,
So backing up the transaction log using RedGate Backup regularly will keep the log size down automatically?
How would I better size a transaction log then?
Cheers,
Jerome
Update:
I've manually backed up and shrunk the transaction log file using MSSQL Server Management Studio now and that worked.
But the shrinking did not work after a RedGate Backup of the transaction log ... So it seems like I still need to create a maintenance plan to backup and shrink the transaction log from time to time via MSSQL SMS, parallel to my backup schedules in RedGate backup?
That'd be a bit unfortunate since I thought I could do all of this exclusively in RedGate Backup ...
Any comments?
Thanks. / comments
Update:
I've manually backed up and shrunk the transaction log file using MSSQL Server Management Studio now and that worked.
But the shrinking did not work after a RedGate Backup of the transactio...
Thank you for this elaborate answer.
But so there is no way of reducing it automatically?
Using the Maintenance Plans in SQL Server Management Studio I was able to schedule 'shrink database' and thus also get the transaction log reduced in size. Could I still do this even though I'm using the Red-Gate SQL Backup for the actual backup of the databases (and not via a Maintenance Plan)?
Thanks!
Jerome / comments
Thank you for this elaborate answer.
But so there is no way of reducing it automatically?
Using the Maintenance Plans in SQL Server Management Studio I was able to schedule 'shrink database' and th...