Reducing the database size to less than 10 GB before an upgrade to Microsoft SQL Server Express

The default Microsoft SQL Server Express database has a size limit of 10 GB for data files and log data. Data files include items such as installation packages, virus definitions, policies, alerts, and learned applications. When you upgrade from the embedded database (14.3 MP1 and earlier) with a size larger than 10 GB, the upgrade process to SQL Server Express cannot continue. If the Management Server Configuration Wizard detects that the database size is too large, you may see the following message:
The backup exceeds the allowed SQL Server Express 10 GB limit. You must first reconfigure the management server to import less data. Then run the restore again. The estimated data in the embedded database exceeds the Microsoft SQL Server Express limit of 10 GB. To continue the upgrade, the wizard must first reduce the amount of data to less than 10 GB.
You must first decrease the space in the existing embedded database, using one of the following tasks:
  • Click
    Continue
    so that the Management Server Configuration Wizard decreases the database size at the beginning of the upgrade process.
  • Cancel the Management Server Configuration Wizard, reduce the database size yourself, and restart the wizard using the following steps.
To reduce the amount of available database size manually
  1. Step 1: Remove any replication partners that 
    Symantec Endpoint Protection Manager
    does not use
    For detailed information, see:
  2. Step 2: Decrease the size of the logs and learned application data
    For detailed information, see:
    See also:
  3. Step 3: Change the default settings for the database maintenance schedule
    1. Stop the management server.
    2. In the following file:
      C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\etc\conf.properties
      , decrease the number of seconds for the following entries.
      scm.timer.objectsweep=1800
      scm.timer.objectsweep.delay=60
      If these entries are not in the file, add them. This step increases the frequency that the database marks unwanted data as deleted.
      For more information, see:
    3. Restart the management server and wait for several hours or longer. See:
  4. Step 4: Schedule replication between all partners to occur at least once. Symantec recommends that you replicate more often
    For detailed information, see:
  5. Step 5: Wait for several hours after each scheduled replication before you restart the upgrade
  6. Step 6: Rerun the database backup and then try to restore it