Notifications
Announcements
No record found.
Hello
Is it possible to rename the model database?
*This post is locked for comments
The model database is not specified in the system so it is expected to be name <originaldbname>_model.
So the answer is yes you can rename it but the AOS will not start afterwards.
.søren
Haha, but I need the AOS running ;-)
OK, if it's not possible to rename the model database I'll let it be...
Thank's for your help
There is ModelDatabase key in Windows registry (under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Dynamics Server\6.0\02\{Config name}), but I've never tried to change it. You may experiment, if you really want.
There's only a key called "ModelDatabase_Baseline".
I created "ModelDatabase" manually, renamed the module database and restarted the AOS but that doesn't work.
Seems like there's no possibility to change the module database name....
But thanks for your help and input.
It does exist in my installation, as well as in the virtual machine from Microsoft, but I have no idea how and whether it is used. And I'm not going to investigate it.
I would strongly recommend to stick with the naming convention and pattern used by the installer, DATABASENAME_model. There might be a lot of places in various tools that depends in this naming convention (ie AxUtilLib), so breaking this pattern would be a bad idea.
The AXUtil's /db parameter takes the name of the model database so I am pretty sure that it will work with a changed name.
The question is why you would like to change it. Moving it to another server?
There's no reason to change the name. ;-)
I was just wondering.
I saw it's possible to set the name of the AX and baseline database and I just asked myself if it's also possible to change the name of the model database. If there's no chance to rename the model database it's not a problem for me. It only makes no sense that I can rename the AX and baseline database but not the model database...
Well, in an upgrade from AX2012 RTM to AX2012 R2, you have the option of pointing the baseline to the original database. So having the option to point the baseline to nothing or something can be usable.
As for the model database, it is tightly coupled with the business database. You should almost think of them as one, they are heavily dependent on each other. In fact, if you install two seperate AX2012 installations, you won't be able to take one model database and use it against the other business database. The element IDs and handles will most likely mismatch.
So I would argue "stick with the naming convention". ;-)
You can move a model database between different environments (e.g. Dev -> Test). Either through export/import of the modelstore or a backup/restore of the model database.
But when doing it between different installations besides that you should be careful though.
Having the databases separated gives you a lot of options in this area when model moving is not enough.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Martin Dráb 4 Most Valuable Professional
Priya_K 4
MyDynamicsNAV 2