Microsoft SQL Server Transaction Logs are full or close to being full. (NETIQKB11565)

Microsoft SQL Server Transaction Logs are full or close to being full.

When the transaction log is filling-up, there are two options:

1.  Perform a differential backup.

Backing up the transaction log in SQL Enterprise Manager is called a differential backup.  This option is given to you on your Backup Database tool within SQL Enterprise Manager.  Because the log will grow until it is truncated, backing up the transaction log (to truncate unused transactions) is very important to remember.

a.  Launch SQL Enterprise Manager.

b.  Right-click the appropriate database, then select All Tasks --> Backup Database

c.  In the SQL Server Backup window, choose Database-differential  under Backup.

You will not have the ability to set the options on all of the tabs. 

You only need to keep your differential backups until your next complete backup. 

2.  Make the log big enough to accomodate the transactions.

This should only be done if there isn't enough room to accomodate a differential backup, as the transaction log will continue to grow without bounds.

a.  Launch SQL Enterprise Manager.

b.  Right-click the appropriate database, then select Properties.

c.  Select the General tab.

d.  Click the Database Properties option.

e.  Select the Transaction Log tab.

f.  Click inside the Space Allocated (MB) box of the transaction log file and enter a larger number.

g.  Click OK.

It is possible to set the transaction log to automatically increase in size by selecting the Automatically grow file optioin in the Transaction Log tab.  There transaction log can be set to grow by megabytes, or by a specified percentage.  Be sure careful with this as you can fill-up the entire disk if the transaction log isn't truncated on a regular basis.

Formerly known as NETIQKB11565