Report "Inventory Valuation"
Rene70
Member Posts: 25
Hi,
we made the change from native database to SQL-Server two weeks ago.
Up to the point of change the report "Inventory Valuation" needed about 45 minutes for calculation.
When I'm starting the report now it needs round about 18 hours.
Is there a solution for this problem? Is there some else, who has this problem too?
We are using finsql.exe 4.0 SP2 and Navision 3.70b Code
I looked into the 4.0 SP2 original programm code, but for this report, no changes were made. So I think this is still a problem when we would make an update.
Thanks for help
René
we made the change from native database to SQL-Server two weeks ago.
Up to the point of change the report "Inventory Valuation" needed about 45 minutes for calculation.
When I'm starting the report now it needs round about 18 hours.
Is there a solution for this problem? Is there some else, who has this problem too?
We are using finsql.exe 4.0 SP2 and Navision 3.70b Code
I looked into the 4.0 SP2 original programm code, but for this report, no changes were made. So I think this is still a problem when we would make an update.
Thanks for help
René
0
Comments
-
My guess is that there is a index problem on the value entries but it is very hard to tell without monitoring the process.
SQL Tuning can be very timeconsuming.0 -
OK that might be. Is there someone out there, who has no problems with this report on an SQL-Server? :-k
From the code of the report I cannot imagine that.0 -
Mark Brummel wrote:My guess is that there is a index problem on the value entries but it is very hard to tell without monitoring the process.
SQL Tuning can be very timeconsuming.
It appears that the report can be timeconsuming as well. *grin, duck*Kristopher Webb
Microsoft Dynamics NAV Developer0 -
Rene70 wrote:OK that might be. Is there someone out there, who has no problems with this report on an SQL-Server? :-k
From the code of the report I cannot imagine that.
I was working recently for a company in Hamilton, Canada, where we were attempting to upgrade their Navision backend to SQL as well. We were informed by Microsoft to use SQL2005 with NAV 4.00b executibles. The code was the old v2.60 code. The installation there is quite large (120GB native database) and that particular report always seemed to run a bit longer anyways. But one key thing that Microsoft suggested was the SQL2005 to eek out some more speed from your system.Kristopher Webb
Microsoft Dynamics NAV Developer0
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
- 1.9K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 250 Dynamics CRM
- 102 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
