Navision's limit in view of concurent users and databas size

anuragatish

hi friends,

our current client is running nav 3.7 with 155 concurrent users and DB size at 70GB. the database is growing at a fast pace. almost 30GB a year.

G/L entry has crossed 180 million entries..and we have started getting a lot of issues like system getting slow and blocking towards the month end when load on system goes up.

we are suggesting our client to go for 4.0 SP3, but they are reluctant and hesitant to go . they think that the product is not scalable to suite their growing business.

Is performance problem enivitable seeing the DB size and users base.
Is the product really not scalable.

what is the maximum size of implementation u have seen working fine with navision?

regards
Anurag

matttrax

We are also on 3.7 with a 73GB database, using SQL. Only 7.5million ledger entries, though. 200+ users. Don't have any major problems.

kriki

In general, there is a lot that can be done. Starting with some questions:
1)is the hardware sufficient?
2)SQL-maintenance is done sufficiently (SQLstats and indexrebuild/defrag)
3)has Navision been prepared to be used on SQL (Index- and SIFT-maintenance)? For this it is best to do a clientupgrade to 4.00SP3 or 5.00.
4)are there some processes that can be rewritten so they ask less resources or are more performant. (this needs to be analysed)

I have a 80GB DB (3.10 on 4.00SP3 client) and it works like a charm. But it has sufficient hardware, SQL-maintenance happens each night index- and SIFT-maintenance has been done. And some procedures have been changed somewhat to be more performant or ask less resources (like selecting an item from the item list that first took +- 4000 DB-requests for flowfield-calculation and now about 40.

anuragatish

the hardware is sufficient. has been checked several times.

one question friend, how does this changing of client works. what exactly are we changing when we open a 3.10 or 3.7 appl with a 4.0sp3 client.
does it change the way the application talks with sql server(as locking order is changed drastically in 4.0 sp1 onwards) .

bbrown

Are you sure about the numbers? 180 million G/L Entries and only 70 GB seems odd. We have a database with ~10 million G/L records where the database is ~40 GB and the G/L Entry table alone si ~5 GB. I would expect a database with 180 million G/L Entry record to be much larger than 70 GB.

kriki

anuragatish wrote:

the hardware is sufficient. has been checked several times.

one question friend, how does this changing of client works. what exactly are we changing when we open a 3.10 or 3.7 appl with a 4.0sp3 client.
does it change the way the application talks with sql server(as locking order is changed drastically in 4.0 sp1 onwards) .

The objects (=the Navision-programs) remain the same. You only change the client (=the finsql.exe) to a new version. You can keep the locking as before (most of the time I have to set the behaviour as in 3.7 because of blocking/deadlock issues).
The newer versions have more possibilities for SQL-tuning then 3.XX-versions.
But of course, before doing it on your live-DB, you have to do a test-upgrade.