Partitioning the ActiveTransfer Database
ActiveTransfer transactional data is stored in the database that is configured in the database component (JDBC pool). Transactional data includes event execution details, file transfer information, and so on. However, if you have large volumes of file transfers or event executions, transactional data can grow quite rapidly and become difficult to maintain.
ActiveTransfer database tables are designed to use the partitioning feature offered by most database types. Database partitioning facilitates better product performance and management of data by storing the data of a single table in separate partitions, which can be managed and accessed independently. For example, the Oracle database supports Interval Partition that allows you to partition data in a table by a specified date range or interval. All ActiveTransfer database tables that store run-time data are equipped with a partition key column or a column that you can used for partitioning. The database tables and their partition key columns are:
ActiveTransfer Table | Partition Key Column | Data Stored in Table is... |
MFTTransaction | TransactionDate | File transfer information |
MFTEventLog | PartitionTimestamp | Event execution details |
MFTActivityLog | PartitionTimestamp | Task execution details associated with a file transfer Task details for each event execution |
MFTActivityLogMessage | PartitionTimestamp | Activity Log messages that are larger than the maximum value permitted in VARCHAR columns |
MFTActivityDetails | EventExecutionTime | Attribute details of agent activities |
MFTAgentEventLog | TimeofExecution | Agent event execution details, at each event execution level |
MFTAgentActivity | PartitionTimestamp | Agent activity details Event execution details at the agent level |
MFTAgentActivityDetails | PartitionTimestamp | Detailed task level information on agent activities |