With some versions of SQL, it's possible to partition your database. This option basically splits the database into multiple data files, which can enhance performance.
If you install ePO 5.10 to a version of SQL that supports partitioning, the ePO installer automatically partitions the Events database into 12 separate data files. Each file represents one of the 12 months out of the year. You can also manually partition your database.
NOTE: Issues can occur if you try to move a partitioned database to a version of SQL that doesn't support partitioning. All current
SQL Enterprise Editions support partitioning, but some versions of SQL
Standard Edition don't. For example, SQL
2014 Standard and earlier don't support partitioning.
ePO does not currently support the following:
- Converting a partitioned database into a non-partitioned database
- Converting a non-partitioned database into a partitioned database
Moving a partitioned ePO database to a version of SQL that doesn't support table partitioning is also
not supported. For example, if you're using ePO 5.10 on an SQL
2012 Enterprise edition, the Events database is likely to be partitioned. It isn't possible to move the ePO database to an SQL
2014 Standard edition server because SQL 2014 Standard doesn't support table partitioning. The only solution is to upgrade to an SQL Server using a version that supports table partitioning, for example,
SQL 2016 SP1 Standard Edition and later.
