Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 304 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Upgrade Large Database TO NAV2013 R2
detlef
Member Posts: 38
When you upgrade a large database, increase the SqlCommandTimeout in the CustomSettings.config file of the NAV server.
After you import the new 2013 R2 objects, the NAV server is still performing tasks on the SQL server (creating indexes). The default SQLCommandTimeout is 20min. 20 minutes is not enough. Every time we started the RTC, the NAV Server started building indexes on SQL and after 20 minutes it rolled everything back. After increasing the timeout to 24 hours, the NAV server actually completed the SQL tasks after 2 hours and the RTC was able to connect. Our database is 150GB.
After you import the new 2013 R2 objects, the NAV server is still performing tasks on the SQL server (creating indexes). The default SQLCommandTimeout is 20min. 20 minutes is not enough. Every time we started the RTC, the NAV Server started building indexes on SQL and after 20 minutes it rolled everything back. After increasing the timeout to 24 hours, the NAV server actually completed the SQL tasks after 2 hours and the RTC was able to connect. Our database is 150GB.
0
Comments
I did an upgrade of a 170GB customer database and did not have any timeouts. Maybe the timeout is for one individual statement and not the entire transaction? That means you had one index that took 20 minutes to rebuild?
What hardware did you use? I used a really fast server since I want to measure timing during the testconversion to know the downtime during the final cutover.
Will keep you posted.
After aplying the new Cumulative Update 6 for Microsoft Dynamics NAV 2013 R2, I just only can say that upgrading to NAV 2013 R2 from NAV 2009 R2 is, as a developer with more than 20 years experience, the worst exprerience of my life.
Could somebody please, tell me THE ONLY RIGHT WAY to successfully upgrade a SIMPLE Spanish 2009R2 Database to NAV 2013R2?
Thank you.
Gunnar has a blog entry on this:
http://www.dynamics.is/?p=1840
with best regards
Jens