The auditing database fails to be purged by the Sophos Management Service

  • Article ID: 118860
  • Updated: 31 Jan 2013


The "SophosSecurity" database introduced in Enterprise Console 5.2 is not purged by the Sophos Management service as part of its 24 hour purge task.

The result of which are as follows:

  1. The table dbo.ErrorLog in the SophosSecurity database has a number of records written to it every 24 hours due to the failure to purge the tables of the database.
  2. The purge task fails to purge the database by the pre-configured history length of 24 months.  

    Note: For more information on configuring the purge of the SophosSecurity database, see article 118827.

Note: Manually running PurgeDB.exe to purge the data will work providing the user executing the task has sufficient 'Execute' rights.

First seen in

Enterprise Console 5.2.0


The Sophos Management Service should obtains the necessary rights (EXECUTE) to purge the data in the SophosSecurity database by being a member of the "Sophos DB Admins" group.  The scripts to create the SophosSecurity database does not grant this right.

What To Do

The attached SQL file should be run against the SophosSecurity database to grant the necessary EXECUTE rights to 'Sophos DB Admins'.  To do so, follow the steps below:

  1. On the computer hosting the SQL Server instance in use by Enterprise Console download the file FixSophosSecurityPurgeRights.txt to 'C:\FixSophosSecurityPurgeRights.txt'.
  2. In a command window with sufficient rights over the database run the following command:
    SQLCMD -E -S .\SOPHOS -i C:\FixSophosSecurityPurgeRights.txt

    .\SOPHOS represent a local SOPHOS named SQL Server instance (default).  

    Note: For details on how to establish the SQL Server instance in use by your installation see article 113030.


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

Rate this article

Very poor Excellent