Yes, "Only" 500 users maximum.What kind of project are you facing, because if there is a need for >500 concurrent users, then you might want to look at solutions scaled for large companies, like AX (or if you hate your customer: sap (this might be a bit biased)).

NAV is aimed at small to medium enterprises, the most implementations have <20 concurrent users, others go to about 100-200 maximum (with some exceptions)

Of course, this "500 limit" is just number somehow created on some tests. Of course, you can have more users, but all depends on specific solution. Some solutions could be used with problems with few users like 20, and some solutions will not have problem with 900 users.

And of course it depends also on what those 900 users do.If they are all 900 users entering sales lines at the rate of 1 line per second, you have a problem (=900 inserts in "Sales Line" per second). If they are all entering sales lines at the rate of 1 line per hour (=900 lines per hour=15 lines per minute) and for the rest they sleep , NAV can handle a lot more users.

It also depends on the number of companies. If you have only 1 company for those 900 users (at 1 line per second), you have a problem. If each of them is working in its own company, it is not a problem.

Thanks for the reply, I really appreciate all of that, I talked to one of MS evangelist for dynamics and they claimed that the largest installation of NAV is 1000+ concurrent user and it's currently in europe.

the industry is remittance(money transfer) and cargo..I have in mind that each branch will have treated as 1 company.

say I have 900 branches it means 900 company in 1 database, this will prevent me from locking issue right? ofcourse infra issue regarding network(bandwidth) and hardware.

in each branch there are 3 users. 3 * 900 = 2,700 concurrent users. the transaction will be sales and collections only on the site. main requirements is real time.

900 companies in one DB have another problems. Each company will include all tables from NAV, even they are empty. Each change in design of a table in NAV will need to change 900 tables on SQL, it will take time. Even backup this DB with many tables could be hard (900*around 1100 tables per company in W1 = nearly one million of tables...).

900 companies in one DB have another problems. Each company will include all tables from NAV, even they are empty. Each change in design of a table in NAV will need to change 900 tables on SQL, it will take time. Even backup this DB with many tables could be hard (900*around 1100 tables per company in W1 = nearly one million of tables...).

Mark Brummels trick for that is to put DataPerCompany=FALSE for tables that are not used. That is a lot of work to do, but it also diminishes a lot the no. of tables in the DB.

Yes, but you must be sure what you are doing that the table will be restored to correct state when someone from one of the 900 companies will start using some new functionality, which was never used before...

Who is online

Users browsing this forum: Google [Bot] and 7 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum