Hello! Simply for the purposes of easing navigation of the TR_WEB_SOURCE_NO table within Tessitura's System Table Maintenance window, we're contemplating deleting inactive rows that haven't been updated recently. I imagine best practice is simply to leave the rows inactive and just get over it, but are there any technical reasons why a mass deletion like this would be inadvisable?
Thanks for your time and advice!
I do it monthly. I call a stored procedure via SQL Agent that looks at TR_WEB_SOURCE_NO and deletes any row where the end_dt isn't null and more than 3 years old (regardless of if it's inactive or not). I also then update TR_WEB_SOURCE_NO for any row older than a year where the end_dt isn't null and inactive = 'N'. I set those so inactive = 'Y'.
It's hard to open the system table in Tessitura if there are thousands of rows <shrug>.
Thank you both!