Specify the number of days to keep log entries in the table before they are deleted.
This property only applies to Transformation and Performance logging types.
If you find that data in the log table is not deleted as expected, see Log table data is not deleted in Troubleshooting for best practice information.
| | Log size limit (in lines) |Enter the limit for the number of lines that are stored in the LOG\_FIELD. PDI stores logging for the transformation in a long text field (CLOB).
This property only applies to the Transformation logging type.
| | Fields to log | Select the fields you want to log in the **Fields to log** pane. | ## Dates tab Use the **Dates** tab to configure date ranges and limits for this connection.  This tab includes the following options: | Property | Description | | --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Maxdate connection | Get the upper limit for a date range on this connection. | | Maxdate table | Get the upper limit for a date range in this table. | | Maxdate field | Get the upper limit for a date range in this field. | | Maxdate offset (seconds) | Increases the upper date limit with this amount. Use this for example, if you find that the field DATE\_LAST\_UPD has a maximum value of 2004-05-29 23:00:00, but you know that the values for the last minute are not complete. In this case, simply set the offset to -60. | | Maximum date difference (seconds) | Sets the maximum date difference in the obtained date range. This will allow you to limit job sizes. | ## Dependencies tab Use the **Dependencies** tab to specify all of the dependencies for the transformation.  The **Dependencies** tab allows you to enter all of the dependencies for the transformation. For example, if a dimension depends on three lookup tables, make sure that the lookup tables have not changed. If the values in these lookup tables have changed, extend the date range to force a full refresh of the dimension. Dependencies allow you to determine if a table has changed when you have a "data last changed" column in the table. Click **Get dependencies** to detect dependencies automatically. | Property | Description | | ---------- | ------------------------------------------------------------------------------------------------- | | Connection | A dropdown to select a database connection that has already been created for that transformation. | | Table | A specific table from the selected database connection. | | Field | A specific field within the selected table. | ## Miscellaneous tab Use the **Miscellaneous** tab to configure buffer and feedback size and performing various administrative tasks.  This tab includes the following options: | Property | Description | | ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Number of rows in rowset | Allows you to change the size of the buffers between the connected steps in a transformation. Do not change this parameter unless you are running low on memory, for example. | | Show a feedback row in transformation steps? | Controls whether or not to add a feedback entry into the log file while the transformation is being executed. By default, this feature is enabled and configured to display a feedback record every 5000 rows. | | The feedback size | Sets the number of rows to process before entering a feedback entry into the log. Set this higher when processing large amounts of data to reduce the amount of information in the log file. | | Make the transformation database transactional |This allows you to open one unique connection per defined and used database connection in the transformation. Enabling this option is required to allow a failed transformation to be completely rolled back.
Enabling this option is also necessary when trying to alter connection settings before a query using an "Execute SQL script" step. (See also the Advanced section in the Database Connection dialog box "Enter the SQL statements (separated ...) to execute right after connecting")
Further information can be found in Database transactions in jobs and transformations.
Note: A transformation wide commit for all steps is done when the last step finishes. When the transformation fails, a rollback is done. It is not necessary to set any commit sizes since they are ignored.
| | Shared objects file | Specifies the location of the XML file used to store shared objects like database connections, clustering schemas, and more. | | Manage thread priorities? | Allows you to enable or disable the internal logic for changing the Java thread priorities based on the number of input and output rows in the "rowset" buffers. This can be useful in some situations where the cost of using the logic exceeds the benefit of the thread prioritization. | ## Monitoring tab Use the **Monitoring** tab for enabling and disabling step performance monitoring and setting related performance parameters.  This tab includes the following options: | Property | Description | | ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Enable step performance monitoring? | This activates performance monitoring for transformation steps. It shows how many rows of data are being written, read, inputted, or outputted for each step. These metrics can be viewed on the **Performance Graph** tab that’s part of the**Execution Results** panel below the canvas. | | Step performance measurement interval (ms) | This is the interval in milliseconds used to take a snapshot. Example: 10 ms | | Maximum number of snapshots in memory | Sets the maximum number of measurement snapshots that can be held in memory during runtime. | --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.pentaho.com/pdia-data-integration/archived-merged-pages/transforming-data-with-pdi-archive/work-with-transformations-cp/configure-transformation-properties.md?ask=