Technical Upgrade from 4.00 to 4.03 (SQL)
ta5
Member Posts: 1,164
Hi
I know this has been discussed in some kind before, but I would like to have some pros and cons for a discussion:
As far as I understand there are 2 options to do a technical upgrade. Its with SQL-Server 2000.
1) Create new Datatabase and restore a backup from the 4.00 DB
2) Just install the new clients and do the conversion on the production DB upon first connection (of course taken a backup first)
What are the pros and cons for these 2 options? By the way: Would the answers be the same if native database were used? Many thanks in advance.
Thomas
I know this has been discussed in some kind before, but I would like to have some pros and cons for a discussion:
As far as I understand there are 2 options to do a technical upgrade. Its with SQL-Server 2000.
1) Create new Datatabase and restore a backup from the 4.00 DB
2) Just install the new clients and do the conversion on the production DB upon first connection (of course taken a backup first)
What are the pros and cons for these 2 options? By the way: Would the answers be the same if native database were used? Many thanks in advance.
Thomas
0
Comments
-
I don't see much difference in upgrading in both ways. If you upgrade from Native you must first convert dates.0
-
Thanks nuno.
Anybody else with a comment? I'm looking for a kind of "best practice".
Thomas0 -
ta5 wrote:Hi
I know this has been discussed in some kind before, but I would like to have some pros and cons for a discussion:
As far as I understand there are 2 options to do a technical upgrade. Its with SQL-Server 2000.
1) Create new Datatabase and restore a backup from the 4.00 DB
2) Just install the new clients and do the conversion on the production DB upon first connection (of course taken a backup first)
What are the pros and cons for these 2 options? By the way: Would the answers be the same if native database were used? Many thanks in advance.
Thomas
For a major upgrade I would do 1/, but for a routine Service pack update, or from a version to another that I know works OK, I would do 2. But always do a DB test afterwards. If you don't have enough experience to know which versions are risky, then best not take that risk, so...
If you are asking BEST PRACTICES, then I would always recommend the backup restore path, (1) since its the proper way.David Singleton0 -
Just one comment.
During a very few upgrade from 3.70 to 4.0 SP3, conversion had hanged during upgrade. In those migrations I had take the second option.
That I also recommend following David advice and always doing first in a test DB to ensure everything is done properly.0
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