Ugrading database without upgrading application code.
rahul_jnk
Member Posts: 61
Hi,
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?
Thanks in advance.
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?
Thanks in advance.
0
Best Answers
-
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
best regards
Robert5 -
HI,
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 + Page5
Answers
-
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
best regards
Robert5 -
HI,
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 + Page5
Categories
- All Categories
- 75 General
- 75 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 610 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 253 Dynamics CRM
- 103 Dynamics GP
- 6 Dynamics SL
- 1.5K Other
- 991 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 28 Design Patterns (General & Best Practices)
- Architectural Patterns
- 9 Design Patterns
- 4 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 77 Testing
- 1.2K Download section
- 23 How Tos section
- 249 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions

