Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K 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
- 298 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Close Income Statement - Performance issues
Kaetchen
Member Posts: 106
Hi,
I have started in a company who hasn't closed their fiscal years on a regular basis. I closed off the first year and tried to run the Close Income Statment Batch Job. After 8 hrs it still wasn't close to the last GL No. The G/L Entry Table has 3,7 Mio records and the size of the DB is 33 GB. We logged a support request with our local consultant and got the following answer:
Does anybody else had the same issue? I have worked with Navision before and never had a problem with this particular task and also had to redo a few years.
Thanks,
Kate
I have started in a company who hasn't closed their fiscal years on a regular basis. I closed off the first year and tried to run the Close Income Statment Batch Job. After 8 hrs it still wasn't close to the last GL No. The G/L Entry Table has 3,7 Mio records and the size of the DB is 33 GB. We logged a support request with our local consultant and got the following answer:
This batch does not normally consume a lot of system resources or table locks. This when the batch has been run regularly.
I am not sure in your case. It might be taking long since it is the first time after so long. You may find that when you do the next year in line it will be quicker.
It might be an idea to do it after hours in the live system.
Does anybody else had the same issue? I have worked with Navision before and never had a problem with this particular task and also had to redo a few years.
Thanks,
Kate
0
Answers
I know a customer who had the same problem. They were running NAV 3.70 native, and use lots of dimensions for reporting. The solution was to make an update for the Close Income Statement batch and CU411 (and some tables, 353 and 7135) from version 5. This worked well and solved the performance problem. And it didn't take long, less than a day.
with best regards
Jens
We have forwarded your reply to our consultant and they passed it on to Microsoft. At present we working with 4.0 SP1 on SQL Server.
I will let you know what they going to reply
Our consultant sent us an upgrade of several objects and it works fine now.
Thanks again for your help
Kate