Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Require information on pyretention period & PR_HOURLY_USAGE



User wants to tune the Pega table PR_HOURLY_USAGE by optimizing the property'pyretention' period to lower value, as the default value is increasing the number of records in the audit table, which is causing serious performance issues.

Error Messages

Not applicable

Steps to Reproduce

Not Applicable

Root Cause

As a custom License Compliance rule has not been defined, while rolling out the application to production environment, default values are being used to retain the data in audit table like PR_HOURLY_USAGE, thus increasing the number of records in the table.


Follow the steps mentioned below on a high level to create a Licensing Compliance rule, which will allow overriding the default values: 

1. Acquire a text file from Pegasystems legal department, which would be provided on signing a contract with Pegasystems, in case you do not have it please check the same with your account executive or whosoever is concerned.

2. Create an instance of Data-Admin-License (License under SysAdmin category).

3. Import the data present in the text file to the import tab of license rule by copying the data from the text file to the Import tab.

4. Adding the License rule to Data-Admin-System rule.

Steps mentioned above will provide you the important tasks to be carried out by giving a brief description of them. 

​Ideally these steps should have been carried out before rolling out the application to production, as the huge number of data in hourly audit is inevitable.


Published November 24, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us