Maintaining the database
Symantec Endpoint Protection(SEPM) supports both the Microsoft SQL Server Express database and the Microsoft SQL Server database. If you have more than 5,000 clients, use a Microsoft SQL Server database.
Symantec Endpoint Protection Managerautomatically installs the Microsoft SQL Server Express database. You can also install SQL Server Express separately. The database contains information about security policies, configuration settings, attack data, logs, and reports. SQL Server Express replaced the embedded database in 14.3 RU1.
After you install
Symantec Endpoint Protection Manager, the management server may start to slow down after a few weeks or a few months. To improve the management server performance, you may need to reduce the database storage space and schedule various database maintenance tasks.
Schedule regular database backups
You should schedule regular database backups in case the database gets corrupted. See:
Optionally, to prevent an automatic sweep of the database until after a backup occurs, you can manually sweep data from the database. See:
Schedule database maintenance tasks
You can speed up the interaction time between the management server and the database by scheduling database maintenance tasks. You can schedule the management server to perform the following maintenance tasks immediately or when users are not on the client computers.
For more information, see:
Periodically check the database file size
Make sure that the database does not reach the maximum file size. The Microsoft SQL Server Express database has a 10 GB size limit. If you install SQL Server Express when you install SEPM, SEPM warns you if you approach the limit. See:
Calculate the database storage space that you need
Before you can decide how to reduce the amount of storage space, calculate the total amount of disk space that you need.
The database storage is based on the following factors:
For more information on how to calculate the hard disk space you need, see the following Symantec white paper:
Reduce the volume of log data
The database receives and stores a constant flow of entries into its log files. You must manage the data that is stored in the database so that the stored data does not consume all the available disk space. Too much data can cause the computer on which the database runs to crash.
You can reduce the volume of log data by performing the following tasks:
Export log data to another server
For security purposes, you might need to retain the number of log records for a longer period of time. To keep the client log data volume low, you can export the log data to another server.
You can configure multiple management servers to receive log data in case one server goes down. See:
Create client installation packages with only the protection that you need
The more protection features that you install with the client, the more space that the client information takes in the database. Create the client installation package with only the appropriate level of protection the client computer needs. The more groups you add, the more space the client information takes in the database. See:
Use the Group Update Provider to download content
If you have low bandwidth or more than 100 client computers, use Group Update Providers to download content. For example, 2,000 clients using a Group Update Provider is the equivalent of using four to five management servers to download content. See:
To reduce disk space and database size, you can reduce the number of content revisions that are kept on the server. See:
Restore the database
You can recover a corrupted database by restoring the database on the same computer on which it was installed originally. Or, you can install the database on a different computer. See:
The information in the database is stored in tables, also called the database schema. You might need the schema to write queries for customized reports. For more information, see: