Bad performances upgrading Navision to release 4.0 SP1

fedepol
Member Posts: 4
Hello everybody,
I've upgraded Navision from release 2.60 to Navision 4.0 SP1 on SQL Server database. All procedures, in particulary the posting, are very slow. I try to optimize some keys, to change some properties like MantainSQLIndex, but the result doesn't change. I also didn't understand very well how to corretcly set this properties...
Can someone gives me an idea?
Thanks in advance for all........
Federica
I've upgraded Navision from release 2.60 to Navision 4.0 SP1 on SQL Server database. All procedures, in particulary the posting, are very slow. I try to optimize some keys, to change some properties like MantainSQLIndex, but the result doesn't change. I also didn't understand very well how to corretcly set this properties...
Can someone gives me an idea?
Thanks in advance for all........
Federica
0
Comments
-
1) You need to understand, that 4.00SP1 is slower, because need to do more work than 2.60 (mainly posting dimensions, creating detail entries etc.)
2) You are not talking about HW. Please, specify your HW, DB size, user count...
3) You can read more about the optimalizations and properties connected to this in Troubleshooting guide which is on the MBS Tools CD0 -
yes, i agree with Kamil Sacek.
Navision 4.01 really of checking, especially in posting area.
The hardware also another concern.
Can you give more information regarding your hardware and database size?0 -
nav 4.00 SP1 seems having a performance issue on SQL server. I noticed about that at http://www.mibuso.com/forum/viewtopic.php?p=41548#415480
-
There is also another problem with SP1. There are no Clustered keys in any table. Pervious to SP1 the primary key was the clustered key by default. With SP1 none of the keys are clustered. This is horrible for performance. This is suppose to be fixed in SP2. For right now you have rebuild your keys weekly, or Go at least through you Ledgers objects and assign a clustered key to a good key. Regards.0
-
You can ask MS for a script that sets the primary keys to clustered in the mean time. That was what was suppoed to have happened anyway.0
-
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
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions