# Enable Deduplication for Individual Index Jobs

To enable deduplication for individual indexing jobs, use the `KillDuplicates` action parameter in the `DREADD` or `DREADDDATA` index actions.

You can use the `KeepExisting` action parameter when directly indexing data into the IDOL Content component with deduplication to reduce the indexing load.

You can use the following action parameters to move duplicates to a specified database.

- `KillDuplicatesDB`
- `KillDuplicatesDBField`
- `KillDuplicatesMatchDBs`
- `KillDuplicatesMatchTargetDB`
- `KillDuplicatesPreserveFields`

You can use any of the deduplication options with `DREADD` and `DREADDDATA` actions. When you use either of these actions:

- The `KillDuplicates` setting specified in either action overrides the same setting in the `KillDuplicates` configuration parameter.

- If you do not specify the `KillDuplicates` action parameter with either of the actions, the setting in the `KillDuplicates` configuration parameter is used.

Related Topics

- DREADD: Index IDX and XML Files Directly

- DREADDDATA: Index Data over a Socket

- Use KeepExisting to Minimize the Index Load

- DREADDDATA Parameters

- Deduplication Options—KillDuplicates

## Use KeepExisting to Minimize the Index Load

If you set `KillDuplicates` to `Reference` or `FieldName`, you can use the `KeepExisting` action parameter to minimize the indexing load on Content when deduplicating.

Set `KeepExisting` to `True` to reverse normal deduplication and discard the document it has received for indexing and keep the existing matching document that it already contains instead.

_FT_HTML5_bannerTitle.htm