---
title: History Versus Snapshot Tables
slug: rdb/essentials-guide/history-versus-snapshot-tables
createdAt: 2026-11-05T09:24:42.125Z
---

Reporting Database snapshots the device information regularly; depending on the export schedule. If run every six hours, then every six hours, Reporting Database creates the following set of snapshot tables:

- mi\_device (the main one)
- mi\_device\_ios
- mi\_device\_android
- mi\_device\_windows\_phone
- mi\_user, mi\_user\_ldap\_attr
- mi\_user\_ldap\_group

When Reporting Database imports the data, it:

- Replaces the snapshot tables on Reporting Database with this latest imported tables from VSP
- Inserts the imported tables to history tables (mi\_device\_hst, mi\_device\_android\_hst, et cetera). Each snapshot in the history table is distinguished by the etl\_run\_ts (this is the export run time) column.

For example, if Ivanti EPMM has 10,000 devices, the snapshot table **mi\_device** should only have 10,000 rows (devices), but **mi\_device\_hst** would contain as many snapshots as Reporting Database ever takes. In our example, if Reporting Database runs every six hours, after one day, **mi\_device\_hst** would contain 4 \* 10,000 = 40,000 rows. If these settings are in effect for one month, the **mi\_device\_hst** table would contain 40,000 \* 30 days = 1,200,000 rows.

You can use the history tables to create some "stats over time" types of reports:

- Blocked or not compliance devices over time
- Number of devices haven't checked in for the last 4 hours of time"
- Number of devices by their status over time

The history tables do not have many entity relationships to their main tables; **mi\_device\_hst** is a superset of **mi\_device**, **mi\_device\_ios\_hst** is a superset of **mi\_device\_ios**, et cetera.

:::hint{type="info"}
When creating your reports, ignore all tables with a \*\_stg suffix and with a number suffix like \*.1.
:::

