Professional Documents
Culture Documents
Environment
McAfee ePolicy Orchestrator (ePO) 5.x
The database often reaches a practical limit at just under the stated size limit for SQL Server. The limit for SQL
Server 2005 Express and SQL Server 2008 Express is 4 GB. The limit for SQL Server 2008 R2 Express and SQL
Server 2012 Express is 10 GB.
Solution
Remove older events to create space within the ePO SQL database.
The following steps are an occasional way to clean up the ePO database. They do not replace the purge functionality
provided by ePO. For more details, refer to the ePO product documentation.
NOTES:
Take a full backup of the ePO database before you make any changes. For instructions, see KB66616.
If Application Control is installed, any events that have not been remediated are removed from both
the ePO_event and scor_events tables.
Where ePO_<servername> is used in the following steps, substitute the name of the ePO database
without the chevrons (<>).
You can obtain the server, instance, and database name information required from the ePO
configuration page at: https://localhost:8443/core/config-auth.
1. Remove older events from the database with the following case-sensitive OSQL commands:
NOTE: Ensure that you change yyyy-mm-dd to the appropriate date; everything earlier than
the date you specify will be deleted.
d. If applicable, launch SQL Server Management Studio or SQL Server Management Studio
Express installed and log in with Windows Authentication.
e. Expand the DATABASE node in the Object Browser window, click the ePO database,
click new query, and paste the appropriate query below. This deletes the events without filling
up the log file if hard drive space is low.
IMPORTANT: Ensure that you change yyyy-mm-dd to the correct date; everything earlier than
the date you specify will be deleted.
NOTES:
a. Shrinking the ePO database is not specifically recommended or required for ePO to function.
b. Shrinking the database files (.MDF and .NDF) can increase index fragmentation and cause
queries to run slowly.
c. After you shrink the database files, if the database needs to expand to accomodate new data,
the SQL server will lock the files for the duration of the growth. This can result in performance
issues with the application that uses the database while the new data is inserted.
a. Type the following command and press ENTER:
osql -E -S <servername\instance>
b. At the command prompt, type each of the following commands and press ENTER after each:
WARNING: The SQL transaction log (.ldf file) can grow up to five times the size of the
database while running the command. Ensure that you have sufficient free disk space
before you use this command.
b. To determine the amount of free space within the database, you can use the following command
from SQL Server Management Studio on the ePO database: Exec sp_spaceused.
For additional details on the sp_spaceused command, refer to SQL Server Books Online
documentation.