HI everyone
I'm doing some year-end housekeeping. In particular, I'd like to tackle the TR_WEB_SOURCE_NO table which is where you link your Source No for an offer to a user-friendly Promo code for use in TNEW. This table has never had anything deleted in over 10 years. Some entries have been inactivated, but there are many still active from previous years which are no longer in use as they relate to past seasons/events.
What's best practice for managing these? Do you delete entries or just inactivate them? I'd like to delete the really old ones and just inactivate the more recent ones. The documentation for this table does not cover inactivation or deletion. I'm assuming it does not affect reporting as this is usually by Source No/Name rather than promo code.
Any thoughts/reassurances welcome!
Many thanksBest wishes
Dawn
Hi Dawn,
We delete all show-specific offers from the TR_WEB_SOURCE_NO once the show has gone. This keeps it manageable, and we’ve never had any problems with reporting.
We always put the show title in the Text 1 field and can therefore filter by the show name which makes it easier than remembering which source is which.
I've been thinking about this again of late. I think I would generally like to keep the data, so I'm inclined to create a Local Reference Table (LTR_ARCHIVE_WEB_SOURCE_NO or the like) and then perhaps annually copying over values while deleting them from TR_WEB_SOURCE_NO. Inactivating still leaves the table with a lot of cruft to potentially scroll through, and when tables get large enough even creates performance issues. We'd probably keep at least one or two seasons in the original table for quick reference?
Thanks Don and Gawain, very helpful. I always think the missing bit in the documentation on system tables is how to manage them - they all have Delete functionality, but just because you can. doesn't mean you should, is always my mantra!
We keep them all, but inactivate once the promo is passed. We like to be able to look back at what promo codes and what help text was used. It is simply second nature to sort by the "inactive" column the moment that table is loaded when building new promos. We have experienced no noticeable performance issues thus far.
That said, Gawain Lavers's local table back-up idea has a lot of merit to it. I may consider.