We have a client with about 150 users (potentially) simultaneously working in Navision (3.60) in one hardware server. Besides quantity of BOM = 50000 quantity of Routings = 50000 Average number of lines in BOM = 20 Approximately quantity of Items = 2400000 Approximately quantity of Warehouses 170 Average number of Production Orders simultaneously opened = 20 Average number of lines in Production Orders = 6000 Average number of Movement per day = 400 Average number of lines in Sales Order and Movement = 20 Periodicity of manufacturing plan calculation = 1 week Average number of Purchase Orders per day = 100 Average number of lines in Purchase Order = 50 AND WE DO NOT SURE THAT ATTAIN(with Microsoft SQL Server) CAN PROVIDE FAST WORK(and no sql bugs) FOR USERS. IS IT BETTER TO USE Microsoft Navision Attain Database Server??? OR AXAPTA???
i think SQL could manage this database without problems. we upgrade our navision to SQL just because we are around 110 users and so many sales orders are opened at the same time. we work with serial nos., we post the orders making shipments and invoices, we also have a lot of new tables that are updated continuously… and SQL server never falls. the database grows quickly, so take care about this (disk space, transaction logs, backup policies…) hope this could help… be happy & yourself mck
When I first saw Navision really showing its colours during our implementation, I thought it was the fastest database I’d seen importing hundreds of thousands of items. Since then, I’ve never been disappointed. Sure, if you bog down the system with so many users, you are going to take a performance hit, but Navision is still one of the fastest databases around, imho. You definitely want the SQL option. I would recommend SQL on any installation over 50 simultaneous users. Cheers!
The proof of the pudding lies in eating. We wanted to prove to one of our prospect that navision does deliver on performance. A publishing house with 1 million customers. We created 1 million customers in database( C000001,C000002…) and then posted posted 1 million sales transaction( for the same item). It did not crash and executed all of them. One thing we did not test is the concurrusers thing. Try it yourselves. Write a batch job to create all the records you want( BOM header, BOM lines, items etc) and do the postings. Seeing is believing!!!
Hi, As i am reading all the replies mostly everyone suggests to use the SQL server. Why that ??? Our Navision System 2.01b (hopefully we will upgrade in the near future, to use the great new debugger [:D]) with 80 users and an actual database size of 10 GB using the navision native database, runs without any performance problems. The only thing i am missing sometimes is the record lock feature. To do the same with an sql database would be very expensive for us. Till now we are very happy with our system, maybe this will change, if our system will get bigger ?
we have two servers (IBM RS6000) with Navision-DB. One with 79 and one with 122 licenced users. In this situation we have a running problem with table-locks as on both servers most users mainly accessing only a few tables (Sales Line, No. Series, …). Now my question: Did anyone of you chanched from Navision-DB to SQL-Server and had before a problem (more or less) with table-locks? Is it truely better on SQL-Server?
Hi Uwe,
quote:
In this situation we have a running problem with table-locks as on both servers most users mainly accessing only a few tables (Sales Line, No. Series, …).
as i wrote, the only thing that is missing in the native navision DB is record locking. It would be realy great to know if those table lock problems are dissapearing when switching to SQL