Database Table Archiving

[Robert_Mee1]

We have a number of tables in our database that have had significant growth.  Some to the point that they are effecting the Database teams ability to run the sampling process. Below are some tables in question. Can anyone share how they are handling archiving?  We do not want to purge this data without archiving to another location outside of the production database first. 

wftransactionlog

wftransactionmsg

transactionxlog

itemdatapage

itemdata

dfcytxlog

wflog

keyitem584

keyitem299

keyitem306

keyitem301

keyitem300

keyitem305

keyxitem125

chartxitemdata

securitylog

keyitem588

keyitem583

keyitem585

[Kevin_Cole]

Hi Paul,

The dialog you indicate purges hsi.wflog

I'm looking for a way to purge hsi.wftransactionlog

Thanks.

[Harry_Siemer]

I agree Kevin. I have also reached out to support to find a way of purging old data from hsi.wftransactionlog and the linked table hsi.wftransactionmsg. We have an environment where system administrators turned on many unnecessary workflow task and rule log events. I have addressed these to prevent ongoing growth of the tables, but would like to reduce the table sizes so that a newly configured watemarking feature on certain queues would perform more quickly in a watermark dashboard. The large table sizes make this painfully slow.

[Julie_Brown]

 @Harry Siemer 

Hi Harry, were you able to find away to purge data from hsi.wftransactionlog?

[Natalya_Svoysky]

here's what we did for archival of history/log tables: we created identical table structures for the tables we want to archive.  Our DBA wrote SQL script to move records to the new tables.  before any custom scripts that manipulate the data can be used Hyland has to review and approve it (lengthy process but gives you flexibility).  then we created dashboard report to present these records to the user.