1419 Excessive Transactional Log Growth Due to Applying 6.1 SR1 Patch

We have identified a potential issue with database transaction logs growing very quickly after running 6.1 SR1 and applying the patch.

Environment:

All windows environment, SES database configured with full recovery model

Symptoms:

After applying the patch,the transaction log for the SES database will generate large amounts of transaction logs.

Details:

SQL Full Recovery is a database option, which allows for recovery of the database in the event of a hardware failure. SQL Full Recovery along with a database backup allows for a database to be restored to the point of failure by restoring the backup and replaying the transaction logs to update the database prior to the failure event.In this mode, any updates to the database create a corresponding transaction log.The log can be removed once a full database backup occurs.

An alternative to SQL Full Recovery is Simple Recovery. This allows restoring of the database to the last full backup.In this model, no transaction log is generated and it is up to the administrator to perform regular backups of their database.In this mode, this article does not apply.

After applying the 6.1 SR1 patch, a component in SQL server, (SQL Service Broker), is generating large amount of transaction logs, up to a few gigabytes of logs per hour. Thecause is under investigation by Microsoft.In the meantime, there are two options to control the growth of logs:

Instructions:

1. Switching the database into simple recovery mode.
   a. Launch SQL Management Studio,
   b. Create a new query, and paste in the following contents.
   c. Replace all instances of "DATABASENAME” with the SES database name.
   d. Execute the query.
   USE [DATABASENAME]
   GO
   --Set database to simple recovery mode
   ALTER DATABASE[DATABASENAME] SETRECOVERY SIMPLE
   GO
   
   Additional information or considerations of switching to simple mode can be found here:
   http://msdn.microsoft.com/en-us/library/ms178052(v=sql.105).aspx
2. Setup a regular backup schedule for the database.
   The frequency of the backup is dependent on the size of the disk space you’ve allocated for the database transaction files.
   IE: A disk with room for 200G should be scheduled with daily backups. A 100G disk should be scheduled with backups every 12 hours.
   Additional instructions on how to automate and considerations can be found here: http://msdn.microsoft.com/en-ca/library/ms191304(v=sql.105).aspx

2013/03/26 Update:

This issue is addressed through the patch previously communicated. Please re-apply the patch to correct the problem. Information on where to download and how to install the patch can be found here: https://www.winmagic.com/knowledgebase/article.php?id=297

Custom Fields

• Version: SecureDoc 6.1