4.03 versus 5.xx regarding SQL performance

Roelof

Would an executable upgrade from 4.03 to 5.xx be an option if it comes to SQL performance? Currently we have a customer using NAV, version 4.03 (SQL) and has some performance issues. We went already over the basic SQL tuning steps, server hardware, clients hardware, memory, drives (raid), etc etc...

bbrown

That's really going to depend on the specifics of the performance issues. Regardless, I would not expect it to be a magic "fix all the problems" solution.

davmac1

One of the big differences is the SIFTs are in managed views instead of SIFT tables.
This should make transaction processing a lot faster and reporting slightly slower.
If your client is in a transaction processing heavy environment, it is worth looking at.
I have also seen in the past that a number of customers are running 32 bit SQL Server because that is what Microsoft supplied when bought with NAV. With a larger number of users, the SQL performance suffers typically, especially when not carefully tuned.
You can get away with a lot of sins in a mid-size implementation with a 64 bit SQL Server and 16GB RAM on the server.

Alex_Chow

Why not to NAV2009R2?

davmac1

Even better if you replace a couple of matrix forms that don't work.

Roelof

Would that be a total conversion or just the executables to make that improvement?

davmac1

Just the executables - last release you can do this with since NAV 2013 does not support classic forms, reports, and dataports.
Just make sure whichever NAV version you use is compatible with the SQL Server version the user has installed unless you plan to upgrade it too.
Remember all the clients need to be upgraded at the same time. If you have a good network person handling the client site, they can handle the rollout for you.