Optimize database

Use the Maintenance > Optimize database feature to optimize Ivanti EPMM database performance by cleaning up fragmentation in the database. Fragmentation of the Ivanti EPMM database can lead to Ivanti EPMM performance degradation. The System Manager display for optimizing the database to clean up fragmentation makes it easy for you to improve Ivanti EPMM performance.

This section includes the following topics:

Optimizing the database

Ivanti EPMM services stop when you optimizing the database. Therefore, MobileIron recommends running database optimization during a maintenance period. See Stopped Ivanti EPMM services for a list of all the services that are stopped when you optimize the database.

After the optimization is completed, Ivanti EPMM services are restarted.

Optimizing the database can take a long time. The duration can depend on:

  • the size of the database, which depends on number of users, devices, apps, policies, and so on, in Core.
  • the level of fragmentation that you specify.
  • the number of tables that exceed the fragmentation level you specify. and their level of fragmentation.

Do not reboot Ivanti EPMM while database optimization is running

Rebooting while database optimization is running can result in a corrupted database. Do not reboot. If you believe that the optimization run is not ending (hung), contact MobileIron Technical Support.

Optimize the database after deleting retired devices

You can delete retired devices in the Admin Portal in Settings > System Settings > Users & Devices > Delete Retired Devices or by using the Ivanti EPMM web services API. Deleting retired devices removes device records from the database. If the action deletes many retired devices, significant disk space is freed, which means a database optimization will reduce fragmentation and improve Ivanti EPMM performance.

Therefore, MobileIron recommends that if you have a large number of retired devices to delete, delete them during a maintenance period, and follow the action with database optimization.

Optimizing the database


  1. Log into System Manager.
  2. Go to Maintenance > Optimize database.
  3. Set Optimize Table Fragmentation Level to a value between 10% and 60%.

    The fragmentation level indicates the percent of disk space allocated for a database table that is not in use (free table space / total table space). A higher percentage means higher fragmentation.

    The screen displays all database tables with a fragmentation higher than the specified value.

    Set a higher level, such as 60%, to display, and then optimize, only the most fragmented tables. Use a lower level, such as 10%, to display, and then optimize, all (or almost all) tables.

    See Optimization tables table for details.

  4. Click Run Now to clean up fragmentation in the displayed tables.

    The display indicates:

    • Do not reboot Ivanti EPMM while the optimization is running. A reboot during optimization could corrupt your database. The optimization can take many minutes, even hours. You can monitor the process by selecting View Status Logs.

      Contact MobileIron Technical Support if the optimization does not finish.

    • Running database optimization stops Ivanti EPMM services.

    When the optimization completes Ivanti EPMM services are restarted.

    The display updates the list of tables and their fragmentation information.

After optimizing the database, smaller tables sometimes still show a significant fragmentation level. This fragmentation level is normal. It occurs because of the small size of the table and the minimum allocation size for tables.

Optimization tables

The following table summarizes the fragmentation options.

Table 42.   Fragmentation Level Optimize Table



Allocated Size (MB)

The total amount of disk space that is allocated to the table.

Free Size (MB)

The amount of the disk space allocated to the table that is not in use.

Fragment %

The percent of disk space allocated to the table that is not in use (Free Size / Allocated Size). A higher percentage means higher fragmentation.