Hardware Guide for Microsoft Dynamics™ NAV 4.0 (Version 4)

kriki

You guys forget the fifth advice!
5) don't use RAID5!

Waldo wrote:

kriki wrote:

Waldo wrote:

RAID5: the controller has to calculate a parity for each chunk of data.

This means that for each write, FIRST a read must be done on the other disks!

And that's a huge delay ...

Well, you can use it for DB's where almost no writes happen. Like DB's for statistics. In this you won't notice the problem. But if the system gets stressed by writes, your system will have a nervous breakdown very easily!

Administrator

Hardware Guide for Microsoft Dynamics™ NAV 4.0 (Version 4)
The whitepaper provides hardware sizing for Microsoft Dynamics™ NAV (version 4.0) installations.

The whitepaper goes into specific detail as to the exact hardware requirements for a variety of Dynamics™ NAV configurations.

Change log between version 3 and version 4:
• Added information on using multiple *.FDB files on multiple RAID 1’s for large C/Side database.
• Updated references to SATA drives to SAS drives. SATA drives have a top speed of 7200 RPM this is not fast enough. SAS drives have a top speed of 15,000 RPM.
• Included Windows Vista as a supported client platform
• Included the recommendation to use internal server storage for small installs
• Introduced a section on processor cores
• Introduced a section on SQL 2005 Standard Edition vs. Enterprise Edition
• Introduced a section discussing x86 vs. x64 platforms
• Updated the “Server” specs for SQL 2005
• Updated the “Storage” specs for SQL Server
• Introduced a section on Terminal Server sizing

Change log between version 2 and version 3:
• Introduce a recommendation using Small Business Server (SBS) for less than 5 users (SQL 2005 section)
• Introduce a recommendation for installation up to 25 users (SQL 2005 section)
• Update the limitations of Microsoft Dynamics™ NAV running with SQL 2005 with the latest fixes (SQL 2005 section)
• Introduce RAID 10 as an alternative to RAID 0+1 (Storage section)
• Remove references to 18GB disks. 18GB disks can hardly be found (Storage section)
• Increase the size of the disks for the SQL Transaction Log and reduce their number. It aligns the number of disks with the storage bays commonly available (Storage section)
• Introduce a sub-section on configuring Logical Units (Storage section)
• Introduce the Database Resource Kit (References section)

Change log between version 1 and version 2:
• Change the document title to “Hardware Guide”
• Modify the section “Purpose, Terms & Conditions” to add the official positioning for Microsoft Dynamics™ NAV
• Remove the section “Executive Summary”
• New section “Microsoft Dynamics™ NAV Client”
• New section “References”
• Remove the recommendations for above 100 concurrent users - except for Microsoft SQL Server 2005
• Clarify the limitations of the Microsoft Dynamics™ NAV Database Server (clustering, RAM and CPU)
• Clarify the use of dual-core processors
• Increase the memory recommendati ons for Microsoft SQL Server
• Modify the recommended drive letters for storage for all servers
• Modify the RAID recommendations and increase the storage requirements for the Microsoft SQL Server transaction logs (all database sizes)
• Clarify and detail the storage requirements for all servers

http://www.mibuso.com/dlinfo.asp?FileID=587

Discuss this download here.