Hello Database Managers!
I'm starting to go through the v16 customizations check report. We've been on Tess since 2005 and have a lot of old custom reports and associated procedures that are no longer in use. I'm wondering what y'all recommend for notating that these are no longer in use so that future DBAs will know that they don't need to bother with these? Should I delete them? Feels scary to me...
I will typically export the SQL object to a file (with the rows if it's a table) using the context menus in SSMS, then store them somewhere with some documentation (although I try to keep some documentation. It can be an arduous task to ensure that you can disentangle the objects from other working objects, though, and this has prevented me from doing it as much as I would like to.
Tessitura's stance is generally, "Whatever, it's fine, just leave it in there" but I find all those extra tables and configuration rows really annoying to have to scroll past, much less having to remember what is something I have to consider (i.e. in this precise case of assessing customization incompatibilities) and what is really deprecated.
Gawain Lavers said:Tessitura's stance is generally, "Whatever, it's fine, just leave it in there" but I find all those extra tables and configuration rows really annoying to have to scroll past,
Once a year I look at custom tables in particular, move any I no longer recognize to another database (just in case), and, if nothing breaks and no-one barks, I delete it a few weeks later. Keeps that huge scrolling list of "LT..." tables a reasonable length!