Is anyone running UP_CLEAN_EXTRACTIONS on a regular basis? If so, how far back do you run it for? I don't know how many years it makes sense to save this data.
Thanks
Henry
We don't run UP_CLEAN_EXTRACTIONS itself (which apparently purges data from T_CUST_KEYCODE only) but we do delete all extractions (including but not limited to the rows in T_CUST_KEYCODE) that have a last_extract_dt, and a mail_dt, more than 13 months in the past.
My consortium runs it on a monthly basis and cleans up extraction key codes older than 24 months. We also have a custom report that deletes the actual extractions that are older than 24 months as well. (We do the same thing for older lists, output sets, and report schedules.)
Chris and Katie,
How did you convince everyone that it was ok to delete the old information?
Melissa
> How did you convince everyone that it was ok to delete the old information?
For several years we deleted no Exts, Lists, OB sets, etc., and they all piled up into a great untidy, boundlessly-growing mess. Nearly everything more than a year + one month old (25 months for Lists) had been a.) created by someone who had left the company and/or b.) had outlived its usefulness. At a TUG meeting we agreed on a timeframe, and I implemented a cleanup routine to match. It's been three years, and there've been few regrets.
Orginally my code only considered the last_extract_dt on exts, but later I did add the mail_dt, a.k.a. "delivery date" field as well, so that analysis-only exts (few in number and never promoted) could be preserved, and as a way for folks to update one field and save a favorite (but seldom promoted) ext from the axe.
Our extractions just slowly ground to a halt, culminating in not being able to send the season brochure.
Our consortium discussed it at one of our regular "Operations" meetings, and for the same reasons that Chris mentioned the consortium agreed that it would be easier to use the system if older, unused items weren't cluttering it up.
Our cleanup utilities allow users to flag lists, extractions, etc. that should be excluded from cleanup, and power users review the items that will be inactivated or deleted via scheduled reports before anything is removed.
This is a battle I've been fighting for awhile, thanks for the info. Time to bring it back up!
Love this! Katie, what do you use to allow users to flag lists, extractions etc. to keep them from being deleted?
We use system tables to flag the items, so we have a system table called LTRX_PERMANENT_EXTRACTS (consortium members access the control-grouped view) that offers a dropdown with extraction names. If a user wants to keep their extraction from getting removed by the utility, they just have to add it to the system table.
A few years ago I shared the equivalent list and report schedule utilities to the network. If you log into TASKàShared Reports and search on the keyword “Manage” you should see them. I believe they include the “permanent” system tables as well.
~Katie
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Summer Hirtzel Sent: Tuesday, April 11, 2017 3:07 PM To: Catherine Lachance-Duffy Subject: Re: [Tessitura Technical Forum] Running UP_CLEAN_EXTRACTIONS
From: Katie Lachance-Duffy <bounce-katielachanceduffy1902@tessituranetwork.com> Sent: 4/11/2017 12:03:29 PM
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!