Most of the data in DTP database is retained permanently unless it is intentionally deleted. Some data is deleted automatically by DTP, and some can be deleted manually.

In this section:

Automatic Deletion and Retention

Test, Coverage, and Metrics Build Details 

By default, DTP database keeps ten builds' worth of metrics data and two builds' worth of test results and test coverage data. The data related to these practices are referred to as "build details" and are used to populate their respective explorer views. When a new report is sent to DTP, the details for the oldest relevant build are deleted if the limit is exceeded. Each build details type, however, is stored independently so that exceeding a build details type's limit does not affect other build details for the same build.

For information on how to change the default settings, see Configuring Data Collector.

Manual Deletion and Retention

Archiving Builds

You can archive a build to save the XML report files associated with a build ID, including the test, coverage, and metrics build details. By archiving a build, you prevent DTP from automatically deleting the build details for the selected build.

For more information on how to archive a build, see Using Build Administration.

Deleting Builds

You can delete unwanted or old builds and most of the data associated with those builds manually. Deletion cannot be undone, so check twice before deleting builds.

For more information on how to delete a build, see Using Build Administration.

Deleting Project Data

You can delete unwanted projects and all data associated with that project. Deletion cannot be undone, so check twice before deleting projects.

For more information on how to delete project data, see Deleting Project Data.

Deleting Static Analysis Data

After deleting builds, there may be static analysis findings in the DTP database that are not associated with any builds. If you want to delete this data, you can use the DTP Database Pruning CLI from the Parasoft Marketplace. Running this tool can result in significant decrease in the size of the database for several tables, which will decrease the amount of time needed for database updates like update 284 in DTP version 2022.2.