Hello,
I'm in the process of upgrading from 2010 to 2013 (then again to 2016). As we practice this in our DEV environment, I started to think about removing modules/product features that we're not using (nor have we ever used).
I understand we could simply uninstall the feature through the suggested uninstall feature route via application setup file and that, in turn, will update the Dynamics.set file and remove those features. As we upgrade, the install process will ignore those features and we should be fine. But then I start to think about what I 'don't know' about the future (business wise) and should we ever decide to use those modules/product features, we'll have issues because they'll be a few versions behind...
I've read a few blogs about this (there wasn't much I could find) and it seems like we could:
1. Uninstall the product feature via the installer so it updates the Dynamics.set file
2. Run the Dynamics Database Maintenance tool to remove the sprocs, functions, triggers, etc. BUT, the Database Maintenance tool doesn't seem to allow for the removal of Tables.
3. Update the DU and db_Upgrade tables and remove the product features
My ultimate goal is to remove the product features from the Dynamics.set file AND all the database objects - that way, should we ever want to use/install them down the road in 2016, we won't run into any upgrade issues.
Just curious if anyone has any guidance, best practices, suggestions, etc. on what we're trying to accomplish.
Thank you in advance!