Antivirus and Security Software from Sophos

Psst, Mac user! We have a free Mac anti-virus just for you.

Online support

Product maintenance

Contact support

Support services

Resource centers

UK IT Security Events

Get the low-down on our cup winning security solutions to provide you with a defence dream team

Sophos Enterprise Console: sophos3_log or sophos4_log files have become too large

Issue
The SOPHOS3_log.ldf or SOPHOS4_log.ldf SQL transaction log files have grown too large, which may also cause performance issues in Enterprise Console. These are the transaction logs for the SOPHOS3.mdf or SOPHOS4.mdf.

Sophos product and version
Sophos Enterprise Console 3.0, 4.0

Operating system
Any supported platform.

Technical Information
This issue may be due to the fact that the database has been installed to an instance that is using the Full recovery model. It should be set to Simple, as per the Sophos installation default.

What to do

Ensure that you have a recent full backup of SQL Server before proceeding with this.
You will need to use the SQL Server Management Studio Express which can be downloaded from here:
http://www.microsoft.com/downloads/details.aspx?FamilyId=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en

You can shrink the LDF files by using SQL Express Studio as follows:

  1. In the Object Explorer, right-click SOPHOS3 (or SOPHOS4) under Databases.
  2. Select Tasks|Shrink|Files.
  3. Change the file type to Log, and select a Shrink action type.
    • Option 1, 'release unused space' is the safest and recommended option as it will shrink the log to the smallest size possible. Always use this option first.
    • It is possible that you may have to highlight option 2, 'Reorganize pages before releasing unused space', then enter a desired value. If Option 1 does not shrink it to an adequate size as this will also re-organise the pages.
  4. Change the recovery model, which should be set to Simple. For details of how to do this, refer to http://msdn.microsoft.com/en-us/library/ms189272.aspx

NOTE: for information on how to stop this happening again, refer to the Microsoft knowledgebase article: http://support.microsoft.com/kb/873235

If you need more information or guidance, then please contact technical support.