When the management server is upgraded, database(s) from the previous version are not removed as part of the upgrade process. This is by design as you may wish to archive the database in your own time once you are happy that the database upgrade has completed successfully.
Note: For fresh installations, the presence of a previous Sophos database version can lead to installation problems; articles: 114097 and 113946 are examples of this.
Reasons to drop (delete) previous databases would be to reclaim disk space and to stop SQL Server loading databases no longer required.
First seen in
Sophos Enterprise Manager 4.7.0
Enterprise Console 4.5.0
What to do
Determine the database location and SQL Server instance name in use by your installation, if you are unsure please see article 113030.
The next step is to determine the database names of previous versions you are now able to drop (delete). The following article 17323 lists which database name corresponds to the version of the Console.
Important: Unless you have a backup of a database, once the database has been dropped (deleted) it can not be restored. Ensure that you are confident you are dropping the correct database or databases before continuing. Before dropping the databases you may wish to take a backup of the databases first and securely store them. For more information on doing this, see article 110380.
To drop (delete) the previous database(s) after a successful upgrade to a later version, you can run commands such as:
sqlcmd -E -S .\SOPHOS -Q "DROP DATABASE SOPHOS50"
sqlcmd -E -S .\SOPHOS -Q "DROP DATABASE SOPHOSPATCH"
In the above example, the database SOPHOS50 and SOPHOSPATCH, which comprise a Console 5.0 install will be dropped (deleted) from the local SOPHOS named SQL instance. You may wish to do this following a successful upgrade to Enterprise Console 5.1.