Improving Navision Posting Speed & Various Server Issues
Modified on: Tue, Dec 13, 2016 at 9:39 AM
|Improving Navision Posting Speed & Various Server Issues
- Network connection
- Data transfer is usually the bottleneck. Get the fastest, most direct connection to the server. A lot of systems have a 10mg network card; try investing in a Gig network card.o Web live music bad.
- Object Cache
- Within Navision 'Tools > Options,' there is a field called 'Object Cache'. This should be set to at least half the ram on the computer.
- When there is more then one program running on a computer, Windows tries to allocate as much memory as possible to the current application. If the user has a process running in Navision and then jumps out of Navision into another program, then the Navision process will be running off minimal system memory. Setting this field will fix the amount of RAM Navision uses so that it does not lose any when the client is multitasking.
- Office Wiring
- This is related to network speed. Verify that client machines are not working off a local router.
- A local router means multiple machines share a single connection to the server. This will drastically increase processing times. One user trying to post a journal will be affected by another user browsing the web.
- System Hardware
- All of the Navision application logic is processed on the client's machine. The server only stores the data and does some base summing functions.
o It is recommended that users that perform calculations/post routines and run large amounts of reports have above industry-standard computers.
- This is especially true for the payroll clerks. Nowhere else in Navision does the system take one journal line (employee hours) and generate many more lines (earnings/deductions/tax), and then post those lines, generating many more lines in multiple ledger tables (Payroll/GL/Bank/Cheque).
- Database Free Space
- Navision is a versioning database. This means that when a change is made to the system data, a copy of the data with the changed values is created. Only after this data is confirmed to be good/valid does Navision then permanently save these changes to the database.
- By following the path 'File > Database > Information' on the database tab, you will want to see at the most 70% 'database used.' The free remaining percentage will be used to create those copies of the data without having to force the server to make room.
- Database Integrity
- There are bottlenecks in the system were certain information is used by multiple Navision areas.
- The General Ledger is an example. Imagine how many areas of the system need to add information to the GL every day, and then think about how many reports are run on the GL every given day. It's a busy place. If you know that payroll will be posting to the GL and that finance will also be posting invoicing to the GL, you may want to work out a plan to have one group wait until the afternoon.
- The GL table is a single table that has to be shared by all users, but only one user can make changes at a time. To allow multiple users to change data at the same time would allow the risk of data corruption by potentially having users overwrite data before other users are aware it ever existed.
o Navision will put users in a queue. Then, user-by-user, each person gets their turn at the table. This way data integrity is maintained, but the user with a five-second posting job had to wait for another user that had a 15-minute posting job.
Did you find it helpful?
Sorry we couldn't be helpful. Help us improve this article with your feedback.