Use the Processing Options tab in
the Delete Service Editor to specify options for deleting archived
data.
You can specify the following options:
- Generate statistical report
- Include statistical information in the process report that may
help you troubleshoot performance.
- Prevent access to tables during processing
- Lock each database table until all rows for that table are processed.
Lock tables to ensure that other database activity does not interfere
with the process and to prevent other users from accessing tables
involved in the process.
- Verify table structure in database
- Verify that, for each table, all columns in the source file match
the columns in the database before deleting a row. If columns do not
match, processing is canceled. When the source file is an archive
file, this check box is unavailable, and selected by default. Columns
match when the number of columns is the same for each table, the names
of the columns are the same, and the column attributes are compatible.
- Commit frequency
- Specify the number of rows (from 1 to 999999) to process before
committing the changes to the database. Frequent commits keep locking
to a minimum, but might slow the process.
- Database connections
- Increase the number of concurrent database connections for the
delete process. Enter an ever number from 2 to 32. Increasing database
connections improves performance when processing large quantities
of data (1000 or more rows) by allowing multiple threads to delete
rows concurrently. Only tables with unique indexes are processed in
parallel and only if Prevent access to tables during processing is
not selected.
- Discard row limit
- Specify the maximum number of rows (from 1 to 999999999) that
can be discarded. The process stops after the specified number is
reached and all rows in the array are processed. The specified limit
is an approximate value due to array processing for the delete service.
For example, assume the discard limit is set to 50 and the array supports
200 rows for a given table. If the first 50 rows fail, the DBMS continues
to process the other 150 rows in the array, before evaluating the
discard limit. The number of rows that can be deleted via one call
to the DBMS depends on the size of the row.
- Delete by RowID
- For use with Oracle only. Enable the Oracle hidden row identifier
to locate and delete rows. For details, see Delete by RowID.
To specify delete processing options:
- Expand a folder in the Directory Explorer that contains
the extract service, expand the Delete Services node,
and double-click the delete service to edit. The
Delete Service Editor opens.
- Select the Processing Options tab.
- Edit the service processing options.
- Save the delete service.