You’re offline. This is a read only version of the page.
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!
*This post is locked for comments
Hey Heather - thanks again. Yeah... the more I ponder the thought, the more I figure the database objects aren't really hurting anything. It's probably more of an OCD thing on my end, and I think it would be a lot of work for little reward. My main concern was not upgrading a module from 2010 to 2013/2016, then deciding that we 'do' want to use it in 2016 down the road. I was worried about being settled in 2016 and having issues upgrading. If that makes sense...
Thanks again for your advice!
Hi Nicole
I have never gone down the track of removing them from the database. We only ever install basically the core from the install CD as a lot of the components are just not relevant for our clients.
The other option you could consider is to leave the database as is, (because in general it doesn't really impact anyone except the dbo's), and just unregister all the other pieces in the registration window (Tools --> Setup --> System --> Registration).
In this window you can "untick" the modules that you don't use. This takes is out of the user interface and unclutters the front end environment, but still leaves the products in the system. It means everything will go through upgrade processes etc no issues and if you want to have a look at using any of the components, you simply tick the box.
Can't help any further with the full removal option.
Cheers
Heather
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (