Thanks very much.
Original Message:
Sent: Jul 24, 2025 04:49 AM
From: Seetharamaiah Uggirala
Subject: Archiving of Catalog request history
Yes, Patrick, it is possible to generate the report on request history by updating the db queries with the new archived table names.
For Example:
Before archiving, all the request data is stored under usm_request table
The archive request data is stored under usm2request table.
Thanks,
Seetharam
Original Message:
Sent: Jul 24, 2025 03:01 AM
From: Patrick_Price_10294
Subject: Archiving of Catalog request history
Thank you Seetharam,
From an audit perspective, customers may want to report on request history - the details of who requested a certain service in the last 5 years - as an example. If the request data is archived, will this still be possible?
Regards,
Patrick
Original Message:
Sent: Jul 24, 2025 01:47 AM
From: Seetharamaiah Uggirala
Subject: Archiving of Catalog request history
Hi Patrick,
We can achieve this by archiving historical data. Please refer to the tech doc link below for more information:
https://techdocs.broadcom.com/us/en/ca-enterprise-software/business-management/ca-service-management/17-4/administering/administering-ca-service-catalog/archive-and-purge-historical-data.html
Regarding your question about whether there are tables that can be archived without compromising audit reports: Could you please provide more details? From my understanding, once the data is archived, it will be stored in separate tables, which will improve performance.
Important Note: Please do not purge the data. Once data is purged, it will be permanently removed from the table.
Thanks,
Seetharam
Original Message:
Sent: Jul 23, 2025 03:23 AM
From: Patrick_Price_10294
Subject: Archiving of Catalog request history
Hello all,
is there a recommended 'best practice' process for clearing up the USM tables? Some of my tables have millions of records which is impacting performance.
Are their tables that can be archived without compromising audit reports?
Thanks, Patrick