mibuso.com

Hello Experts,

We are going to implement Nav 2009 and to use Sql datatabase. We are reviewing hardware equipment if they support our transaction amount of data

We do every day about 1500 sales orders with 10 lines( in total 15000 lines) and about 100 purchase orders with 30 lines in total (3000 lies).
We have 40 concurrent users.

Is a big amount 18000 lines in a day to be posted in Nav. Does have any problem with the performance (the speed ) of the system this amount of data and 40 concurrent users.

Does support the server HP Proliant Dl 380 g5 Ride 5?


Best Regards

If you search Mibuso you will find lots of post concerning hardware. They will recommend various things, including not using RAID 5. A properly configured and tuned NAV system is well capable of supporting the transaction volume you describe.

The HP DL3XX Line is very popular in NAV implementation. Just not with RAID 5.

Feel free to post additional more specific questions as they arise.

Thank you for your reply,
So you suggest Ride 10? I'm in very confuzed if the Ride5 can do with this volume of data transaction.

Regards.

RAID 10 has better write performance than RAID 5.

Just as important is that the transaction log file is placed on its own dedicated physical disk array (RAID 1 or 10). This means that no other files are ever placed on that array. This includes other transaction logs.

A typical NAV server config with the DL380 might be something like this:

Using 16 - 146 GB 15K SAS disk:

ARRAY 0 - RAID 1 (2*146 GB) - Operating System, Program Files
ARRAY 1 - RAID 1 (2*146 GB) - SQL System databases
ARRAY 2 - RAID 1 (2*146 GB) - Transaction Log - Live DB
ARRAY 3 - RAID 1 (2*146 GB) - Transaction Log - Test DB
ARRAY 4 - RAID 10 (8*146 GB) - NAV Data files

There's some open discussion of the best use for RAID 1. One option is to move the SQL System Databases to Array 4 and use this for backups. Another option is keeping Temp DB here.

I installed a NAV system with several times higher volume with a similar RAID configuration bbrown described. Also had 32 GB RAM. While the log file has to be written right away, SQL Server will make good use of RAM for caching.
There is also a recommendation to have 1 tempdb file per CPU core. Some recommend to put tempdb on its own spindle.
I imagine as NAV moves to SQL Server only, it will make more use of SQL Server features for performance improvement.