The ePO database size can grow significantly over time for several reasons, such as:
- Virus outbreaks
- False positives
- Update Errors
- Upgrading
If the ePO database grows too large, ePO might become unusable or unstable until you take the appropriate actions to reduce it.
If the ePO database runs on a SQL Express instance
SQL Express has a hard-coded maximum database size of 10 GB. If you reach this limit, the database can't grow any further, even if you have space available on the storage device that hosts it.
You can address this issue in one of the following ways:
- Create space in the database by deleting old events. See KB68961 for details.
- Move the database to a full instance of SQL, which does not have the 10-GB limit, and allow the database to grow as needed. See KB68427 for details.
If the ePO database runs on a full instance of SQL
The following are the most common causes of database full errors:
- The hard disk or storage device hosting the database files is full.
Either of the following approaches address the issue:
- Make space available by deleting or moving other files on the same device.
- Move the database files to another storage device that has space available.
To learn more about moving databases, see:
- The database has reached its defined maximum size, as set in the properties for the database.
Either of the following approaches address the issue:
- Create space in the database by deleting old events. See KB68961 for details.
- Allow the database to grow by increasing the maximum size of the database files.
- The transaction log has run out of space.
Address the issue as follows:
- Truncate the transaction log. See https://technet.microsoft.com/en-us/library/ms189085(v=sql.105).aspx for details.
- Use the Simple recovery model for your database. The Simple recovery model allows SQL to manage the transaction log for you, avoiding future transaction log growth.
