Hi All,
To share some context, the Prod environment data storage utilization has reached 75%. We’re seeking solutions to either reduce or effectively manage our PEGA data storage usage. After exploring options and using Pega Diagnostic Center to analyze application behavior, We’ve narrowed down the research to three potential approaches, but we need more information on these. Here are the details we’re seeking:
1. Cleaning-up records on pc_data_workattach table:
a. In PDC, under System Resources > Database > Tables > Schema, we noticed a large byte total on the pc_data_workattach table. Our knowledge is that this table stores case attachments. Can we remove case attachments older than a certain period from this table?
b. Is there any PEGA built-in process/policy that allows us to delete some records?
2. Deleting unused table indexes:
a. In PDC, under Database > Tables > Schema > Index Used Info, we’ve identified table indexes unused for at least 20 days. If delete these, what are the implications? Is it possible to quickly re-add/restore them if needed?
3. Implementing a Case Archival Policy:
a. Does transferring case data from Cloud Data Storage to Pega Cloud File Storage incur a cost? What is the approximate cost of using PEGA Cloud File Storage?
Besides the mentioned approaches, are there other methods to reduce or effectively manage cloud data storage?
Any insights on these matters would be greatly appreciated.
Thank you.
@IanKeithT16911417
1. Attachments: Can we remove case attachments older than a certain period from this table? - You need to delete respective files class intances ( Data-WorkAttach-File, Link-Attachment) Pega is providing OOTB for removing attchments like, DeleteAttachment, pzDeleteEmbedAttachment.
2. DB Issues: You can connect with Pega cloud support team to remove Dead Tuples from your tables.
Dead Tuple
When you update or delete any row, internally it creates a new row and marks the old row as unused. The unused rows are known as dead tuples and they will never be removed from the table by itself.
For removing Indexes it would require more analysis using Query Inspector, please use performance tools to identify the db issues,
Reference: Diagnosis of database issues | Pega Academy?
3. Case Archival: Pega Cloud production subscription clients receive 500 GB of file storage to use across all environments in the subscription. Expanded storage capacity can be added as needed (additional fees apply).
Please contact Pega Global Client Support (GCS) team / Cloud Admin for more details.
Archive Improves database performance
Faster processing of database queries reduces the risk of system timeouts and increases the speed of data retrieval and reporting.
Configuring your data retention policy in Case Type. Pega Jobs are responsible for Archive, Index & Purge.
pyPegaArchiver
pyPegaIndexer
pyPegaPurger
Reference:
You can use Repository APIs (D_pxGetFile, D_pxListFiles, D_pxDelete..etc) listed in the Embed-Repository-File for Interacting with your Case files in pegacloudfilestorage (file://pegacloudfilestorage:/)
Additionally you can write Purge Utility (Use Connect-SQL for Delete query) for clearing any Data Table Instances by Configuring your data retention policy in Decision table.