Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Reports running slow
Horse06
Member Posts: 496
Hi experts, we upgraded from 5.0 to 2013. Some of the reports are running very very slow. For example reports 10048(Customer/Item Statistics), 10049(Cust./Item Stat. by Salespers.) and many others. It takes very long time to retrieve the data and some of them will take forever. Any help or ideas on how to improve the performance of the reports will be appreciated.
0
Comments
I don't have with me all the information about this problem but I'll try to explain as much as possible.
First of all if you want to print those reports for example every Customer in your database that is a problem, it's a known issue due to the fact that NAV Client runs on 32 bits while NAV Server runs on 64 bits, that way the Client causes a bottleneck.
It's recomended in cases of reports with a lot of infomation to "break them" in little segments, for example:
-> choose a small group of customers
-> or if you need them all try to make date filters for sets of periods, if you see it's needed monthly, weekly, something like that.
-> If your report have a dataset with a lot of fields try to see if they are all needed, if there isn't something you can remove to reduce the amount of information that you are passing.
-> Beware of pictures if you have them passed for each record in your dataset they can cause a performance issue.
-> There is a value for reports that if you estimate your dataset to retrieve 70k rows you might want to split break it as I told before and make sure the lines returned are reduced.
(you can check your dataset if you use the "about report property" when it's loading and check the lines you are recieving.)
Hope I could give some help about it