This problem statement only applies if you are upgrading from ePO 5.3.3 to ePO 5.9.0 or later. After you have upgraded to ePO 5.9.0 or later, the ePO DB schema has been migrated. Subsequent upgrades do not require the tables in question to be updated.
A pre-upgrade check during the ePO 5.x upgrade displays a warning message similar to the following:
The SQL database needs more free space or setup will fail.
It needs two times the current database size to continue.
The ePO 5.x installation makes a schema change on these tables. This change could take up significant more disk space on the SQL Server, and migrating this data could take a long time to complete.
The ePO 5.x installer looks at the size of unbounded tables in the ePO database.
When you upgrade from the 5.x version, it verifies only a subset of the following tables. But, when you upgrade from earlier 4.x versions, it includes checks for all following tables:
- EPOEvents
- EPOProductEvents
- EPORollup_Events
- EPORollup_ProductEvents
- OrionSchedulerTaskLogDetail
- OrionAuditLog
NOTES:
- If the ePO installer changes any of the tables listed above, and they have over one million rows, a warning message is displayed before the installation starts.
- The SQL Server needs significant reserve disk space to apply the schema changes to these tables.
- The changes take significant time to complete, which causes the ePO upgrade to potentially run for many hours or fail.
IMPORTANT: Create a full backup of the ePO server and database as directed in the release notes.
The time and space needed are directly proportional to the number of rows in the table.
Supporting data:
The following data comes from our internal testing of the ePO 5.x table schema upgrade.
SQL Server specifications:
- Single SATA 2 spindle
- 4 Core 2.8 GHz Xeon
- LDF and MDF on the same disk. The MDF file is the primary file in SQL Server database. The LDF is a supporting file.
Test |
Table |
Row
Count
(million) |
Time |
MDF
Growth |
LDF
Growth |
Large Client Event count. Modify Identity column while preserving time stamps. |
EPOProductEvents |
60 |
2 hours 15 minutes |
15 GB |
36 GB |
Large Audit Log count. Addition of int column with default constraint. |
OrionAuditLog |
14.5 |
23 minutes |
5 GB |
5 GB |
Let the installation continue after the warning:
- When you have performed the steps above
And
- Have adequate disk space on the SQL Server for the upgrade to occur