A quick question, is it ok to upgrade database without upgrading application code?
I mean i need to upgrade NAV from 2013 R2 to 2016, so are there any chances of getting problems in future?
It is possible, that this will work, but I would not suggest that. There are different changes of Dynamics NAV, which can be a problem. I would suggest, that you try this with your database.
- SQL DB Backup
- Restore DB Backup in new SQL DB
- Convert it to nav 2015
- Convert it to NAV 2016
- start nav 2016 nst
- process schema snyhc (with check / not force, because of dataloss)
- start windows client and check data and functionality
I would suggest to do a data migration from NAV 2013 R2 and NAV 2016. To me it will be a simple merge and auto merge utilities can be used to merge objects.
There are changes between these version one of most known is removal of approval and is now a part of workflow.
There are some new features added in NAV 2016 objects like -
1. Events in standard Nav.
2. New Tables introduced.
3. Some tables discarded.
Have a look in the upgrade Toolkit objects to understand all the changes in standard application between NAV 2013 R2 to NAV 2016.
It is possible, that this will work, but I would not suggest that. There are different changes of Dynamics NAV, which can be a problem. I would suggest, that you try this with your database.
- SQL DB Backup
- Restore DB Backup in new SQL DB
- Convert it to nav 2015
- Convert it to NAV 2016
- start nav 2016 nst
- process schema snyhc (with check / not force, because of dataloss)
- start windows client and check data and functionality
I would suggest to do a data migration from NAV 2013 R2 and NAV 2016. To me it will be a simple merge and auto merge utilities can be used to merge objects.
There are changes between these version one of most known is removal of approval and is now a part of workflow.
There are some new features added in NAV 2016 objects like -
1. Events in standard Nav.
2. New Tables introduced.
3. Some tables discarded.
Have a look in the upgrade Toolkit objects to understand all the changes in standard application between NAV 2013 R2 to NAV 2016.
Answers
- SQL DB Backup
- Restore DB Backup in new SQL DB
- Convert it to nav 2015
- Convert it to NAV 2016
- start nav 2016 nst
- process schema snyhc (with check / not force, because of dataloss)
- start windows client and check data and functionality
best regards
Robert
Robert's Dynamics NAV Blog - Vom NAV Entwickler für NAV (Navision) Interessierte
I would suggest to do a data migration from NAV 2013 R2 and NAV 2016. To me it will be a simple merge and auto merge utilities can be used to merge objects.
There are changes between these version one of most known is removal of approval and is now a part of workflow.
There are some new features added in NAV 2016 objects like -
1. Events in standard Nav.
2. New Tables introduced.
3. Some tables discarded.
Have a look in the upgrade Toolkit objects to understand all the changes in standard application between NAV 2013 R2 to NAV 2016.
I would recommend to do a object merge.
Thanks & Regards,
Saurav Dhyani
Do you Know this About NAV?
Connect - Twitter | Facebook | Google + | YouTube
Follow - Blog | Facebook Page | Google + Page