We are looking at implementing large Navision solution for one of our customers. Information: NF 3.7 MSQL if needed. 70 companies in a single database each company with approx 15 users (total 1050 license users 50% concurrent). Peak activity each company doing about 200 sales a day concentrated to 3-4 hours with average 20 sales lines. (total 14000 sales of 20 lines). Single Sales invoice could have 2000+ sales lines but will be handled off peak hours. Estimated annual database (native) grouth per company approx 3-4GB total 210-280gb per year. Keeping history in seperate database to prevent database growing to much beyond that. I would like to hear all comments and learn from others experience of installations of this size. How do 210-280 native gb translate to SQL GBs? Are we being unrealistic in our expectations to Navision? We could split the database if needed. Look forward to hearing from you. Best regards, Gardar Runolfsson
For a solution this large I’d just get on the horn with Microsoft’s BS Department and see what assistance they’ll offer you. I’m sure they want your business.
quote:
Originally posted by herdis
We are looking at implementing large Navision solution for one of our customers. Information: NF 3.7 MSQL if needed. 70 companies in a single database each company with approx 15 users (total 1050 license users 50% concurrent). Peak activity each company doing about 200 sales a day concentrated to 3-4 hours with average 20 sales lines. (total 14000 sales of 20 lines). Single Sales invoice could have 2000+ sales lines but will be handled off peak hours. Estimated annual database (native) grouth per company approx 3-4GB total 210-280gb per year. Keeping history in seperate database to prevent database growing to much beyond that. I would like to hear all comments and learn from others experience of installations of this size. How do 210-280 native gb translate to SQL GBs? Are we being unrealistic in our expectations to Navision? We could split the database if needed. Look forward to hearing from you. Best regards, Gardar Runolfsson
Hi Herdis, this is a very interesting project. Tell me more [:)] First comment would be that distributing the processing amoung many servers will probably be a requirement, thus implying SQL to tie them all together.