Managing the Size of the Log

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

The logging service sends large amounts of data to the logging database. You should check your logging database regularly to make sure that it has sufficient disk capacity for the data. If you find that the amount of data is excessive and that your reporting needs do not require some of the information, consider setting SQL Server filters to reduce the log files to only store the logs that you need. For instructions on filtering logging information, see Help for SQL Server Enterprise Manager.

If your organization decides that it does not need to keep the logging data forever, you can write a SQL script that will either archive to another database or delete permanently data that is older than a certain date.

If you find that your logging database is growing too large for the available disk space, you can move the logging database to a different server, as described in “Relocating the Logging Database” later in this subject.


You should also use System Monitor to regularly monitor the size of the outbound logging-message queue. If the queue size grows substantially, verify that the logging listener service is operating correctly. For more information about using System Monitor, see Windows Server 2003 Help and Support Center.