2018.2

Tip
In order to prevent attempts at deleting database objects which might
still be in use, it is recommended that all Minimum time retention values
should always be set to at least the length of your longest job. Preferably
with some extra time added, for good measure.
For example, if your longest job takes 45 to 50 minutes to run, then set
the retention time to 55 minutes (or 1 hour) to ensure that all the
database objects created during job processing survive for the duration
of the job.
l
Minimum time to retain Content Sets: The minimum time a Content Set (and
all the content items it contains) is retained within the database before being
set for deletion.
l
Minimum time to retain Job Sets: The minimum time a Job Set (and all the
jobs information it contains) is retained within the database before being set
for deletion.
l
Minimum time to retain Managed Files: The minimum time file references (to
files such as data mapping configurations and templates) are retained within
the database before being set for deletion.
l
Minimum time to retain other entities: The minimum time any orphaned data
(such as Finishing tables, Media tables, DataModels and Properties tables)
are retained within the database before being set for deletion.
l
Database Partition Settings:
l
Use Database Partitioning: Select to use Database Partitioning.
l
Empty partition count: The number of empty partitions that are created each
clean-up run. This defaults to 24.
l
Partition Size:Enter the length of time before partitions are switched. This can
be entered in minutes, hours, days, weeks or months.
l
File Clean-up Service:
l
Allow file clean-up service: Check to automatically detect orphan files and set
them for deletion. Orphan files could be resources and internal files used by
Connect, but which are not needed by any running job.
Page 89