Deduplicating VMI Data

Deduplicating is a process of removing the VMI data when the data is processed twice in Voice Server and Engage. The data deduplication is done on the basis of client ID.

If any alert is sent from an Engage appliance through VMI to Voice Server, the data is processed twice. For example:

Engage LDG tables—Engage adapter inserts data.
VMI tables—Voice Server pipeline inserts data.

Data deduplication is managed at the database level on the basis of client ID, that is provided during VMI configuration. In Vocera Analytics, dimvmiclients table contains the client ID for which data has to be deduplication. By default, the dimvmiclients table contains two client IDs VMP and ENGAGE. There is no restriction on the number of client ID configurations.

Adding a Client ID

To add a client ID, perform the following tasks:

Connect to Vocera Analytics database as an authorized database user such as analyticsuser using tools such as HeidiSQL, workbench.
Check the data present in the dimvmiclients table using the following query:
```
SELECT * FROM vocera_analytics.dimvmiclients;
```
Add a new client ID using the following query:
```
INSERT INTO vocera_analytics.dimvmiclients(Id, ClientId) values (<Id>,'<ClientId>');
```
where <Id> is the next incremental value and <ClientId> is the name of the client ID that requires data deduplication.

Note: Ensure that you provide the exact name of the client ID to filter data.

Deduplicating Data

If data is already loaded into Engage LDG database and VMI tables, then you must manually clear the data from the vmiAlerts table to perform data deduplication.

Clear data from the vmiAlerts table using the following query:
```
TRUNCATE TABLE vocera_analytics.vmialerts;
```
Database events ensures that data deduplication is complete by using dimvmiclients table.
Note: It is recommended to add the client ID before starting VRS or Engage data migration.