Tail Log Backups

Issues with running backup log with no_log or truncate_only

On my database server I have my databases set to the full recovery model, but the transaction logs get quite big, so I am issuing a BACKUP LOG with NO_LOG. I am not exactly sure if this causes any issues, but I know that I am able to free up space in my transaction log and shrink the file. Is this the correct way to handle this situation?

An easy way to track the growth of your database

This query gives you an idea of the growth of your database over time.

Comprehensive Backup Script

These scripts were generated to standardize our SQL backup environments, and to remove backups from Maintenance Plans.

Reporting on Activity across Multiple Servers using SQL Backup and SQL Multi Script

Rodney Landrum presents a creative solution for dynamic reporting across all of his SQL Servers, based on use of Red Gate's SQL Backup and SQL Multi Script.

Shrink all databases

Procedure changes all databases' recovery mode to simple and shrinks them all (or at least it tries to).

BackUp_DBs.sql

Make backup several databases with a cursor

BackUp database

BackUp database

Backup Stored Proc

Script to backup 2000/2005 databases.

Featured Blog: BACKUP LOG WITH NO_LOG

From one of the SQL Server 2005 storage engine lead developers comes this look at the impact of using the NO_LOG and TRUNCATE_ONLY options.