RE: Completely removing modules and tables
Richard,
Next to what Lisa & Steve replied, there are indeed a few KB articles from Microsoft out there to completely remove some module tables. In particular those who could come back and bite during an upgrade, like FA & AA.
In most cases if you take out the modules from the .SET file, the DU000020 & DB_Upgrade tables, then GP Utilities won't try to upgrade those anymore.
GP PowerTools Database validation does offer that option to check on missing modules from the .SET file and remove all references from the system, and even remove tables that are no longer needed, but you need a registered license to do it. Mostly recommended to customers way before they start an upgrade project, so the situation can be assessed long before the upgrade starts.
Like Lisa, I've built over the years a long list of GP module numbers and add-ons from various third party, so I know what it refers to during an upgrade, would it start to fail.
It's a PITA, but most ISV's don't even bother to provide a proper removal script for their SQL objects when un-installing the product.. Sometimes you can get it from their technical setup guides or from the support.
A good idea is to setup a Vanilla GP instance and then trace down with SQL what objects get created during the install process of a new module.. I did that once or twice in the past as I couldn't clearly identify all the created SQL objects and needed to get rid of them.