|
|
 |
|
|
VerticalSoft Food Manufacturing is based
on industry-standard software by Microsoft Dynamic NAVs. With over
one hundred thousand installations worldwide, Navision is one of the
largest and most robust platforms available. Columbus IT's VerticalSoft Food Manufacturing requires the
following:
Client Installation Requirements
Download Full System Requirements PDF
SQL Server Option for Microsoft Dynamics NAV
Operating System
 |
Microsoft Windows XP SP2 or later (X86 or running 32 bit on X64)
|
|
Microsoft Windows 2003 SP1 or later (X86 or running 32 bit on X64)
|
|
Microsoft Windows Vista (X86 or running 32 bit on X64) |
Hardware Resources
|
Hard disk space:
About 250 MB (full installation incl. two language modules)
About 110 MB (minimal installation incl. two language
modules)
|
|
Memory: 60 MB free memory with default cache settings
|
|
CPU: See operating system requirements |
Other Applications:
|
Microsoft SQL Server 2005 Express is required for Single-User |
|
Installation when selecting SQL Server Option for Microsoft Dynamics NAV. |
|
SQL Server 2005 Express is part of the client installation program. |
Microsoft SQL Server
Operating System:
|
See requirements for Microsoft SQL Server 2000 or Microsoft SQL Server 2005 |
Other Applications:
|
Microsoft SQL Server 2000, SP4 or Microsoft SQL Server 2005 |
C /SIDE Client for Microsoft Dynamics NAV
Operating System:
|
Microsoft Windows XP SP2 or later (X86 or running 32 bit on
X64)
|
|
Microsoft Windows 2003 SP1 or later (X86 or running 32 bit on X64) |
|
Microsoft Windows Vista (X86 or running 32 bit on X64) |
Hardware Resources
|
Hard disk space:
About 250 MB (full installation incl. two language modules)
About 110 MB (minimal installation incl. two language
modules)
|
|
Memory: 60 MB free memory with default cache settings
|
|
CPU: See operating system requirements |
C /SIDE Client for Microsoft Dynamics NAV
Operating System:
|
Microsoft Windows XP SP2 or later (X86 or running 32 bit on
X64)
|
|
Microsoft Windows 2003 SP1 or later (X86 or running 32 bit on X64) |
|
Microsoft Small Business Server 2003 SP1 or later (X86 or running 32 bit on X64) |
|
Microsoft Windows Vista (X86 or running 32 bit on X64) |
Hardware Resources
|
Hard disk space: Space for database
Temporary space equivalent to the size of the largest primary
index
|
|
Memory: Min 30 MB, Max 1 GB
|
|
CPU: The server can only use 1 CPU
|
|
Network: TCP/IP or NetBIOS-compatible LAN
LAN network connection should be 100 Mbit/sec or better
|
Application Server for Microsoft Dynamics NAV
Operating System:
|
Microsoft Windows XP SP2 or later (X86 or running 32 bit on
X64)
|
|
Microsoft Windows 2003 SP1 or later (X86 or running 32 bit on X64) |
|
Microsoft Small Business Server 2003 SP1 or later (X86 or running 32 bit on X64) |
|
Microsoft Windows Vista (X86 or running 32 bit on X64) |
Hardware Resources
|
Hard disk space: 8 MB |
|
Memory: Min 65 MB free memory
|
|
CPU: The server can only use 1 CPU
|
|
Network: TCP/IP or NetBIOS-compatible LAN
LAN network connection should be 100 Mbit/sec or better index
|
Note:
Several performance improvements in the SQL Server Option depend on the amount of memory available to the client program. Adding more memory will increase performance.
Note: If the client program is running in a Citrix/MS Terminal Server environment, the memory consumption of the SQL Server Option clients may increase to about 100 MB.
Server Environment
Operating System
|
Microsoft Windows NT (Intel) version 4.0 or Windows 2000 |
|
IBM AIX version 4.3.3 on IBM pSeries machines (RS/6000) |
SQL Server Option
|
Microsoft SQL Server 2000, SP1 or later |
|
Microsoft SQL Server 7.0, SP2 or later |
Suggested Server Hardware Guide
Navision Server
|
RAM—A rule of thumb to follow, but not absolute is; 1.5 MB of RAM per user + 10 MB of RAM per every 500 MB of database space + 32 MB of RAM for the Operating System. Example of what might be used for a 60 user system with 4 GB database:
[RAM = (1.5 MB/User * 60 Users) + (10 MB/ 500 MB * 1000 MB/1GB * 4 GB) + 32 MB RAM = 202 MB]
The next standard increment of RAM would 256 MB. The Navision Server should be configured with 256 MB of RAM initially. The amount of suggested CACHE would then be set to 202 MB. If the CACHE setting is the same as the system RAM, then set the CACHE equal to the calculated amount minus the RAM required for the Operating System. This value will change as the system is fine tuned for the client.
|
|
Hard Drives—The server is very dependant on disk reads and writes. The faster the disk setup, the faster the performance of the server process. This is probably where the biggest gains in server performance can be had. A RAID 1 array is suggested to be used with the database. RAID 1 provides the best redundancy for the system by duplicating each drive (Mirroring). Because of the way the Database Manager works, RAID 1 also allows the server to strip the data over multiple drives. This permits the server to read and write data over multiple drives simultaneously, which results in better performance throughout. When putting together the RAID 1 array the fastest drives and interface available is suggested. ( ULTRA SCSI 3 15k RPM).
|
|
Processor—The fastest processor that the client can afford is suggested. Multiple processors are not required since the Navision server can not take advantage of it.
Network—A 100 Mb/s or faster network be utilized is suggested. For WAN connections the Citrix or Microsoft Terminal Services is suggested.
|
Microsoft SQL Server
Processor
There are three factors to consider for processing:
1. Number of CPUs
2. Size of Second Level Cache (SLC)
3. Clock rate
|
Number of CPUs—The number of CPUs is by far the most important of the
aforementioned parameters.
Navision Server requires only a minimum of CPU power, and it is possible to use only one CPU. This changes with the
Microsoft SQL Server Option for Navision, as the server can now theoretically be scaled up to 32 CPUs.
The processors should not be loaded more than 80% on average during peak times. If the load is higher,
the system is most likely CPU limited. Large databases can have an impact on the CPU load if extensive reports are carried out. But basically the size of the database has no impact on the CPU load as the table above shows.
|
|
Size of Second Level Cache (SLC)—The amount of SLC has an impact on performance, because of Microsoft SQL Server's enhanced memory utilization. All frequently accessed tables are stored in the memory for fast retrieval. The SLC stores the information that is accessed the most and this access is dependent on the speed of the CPU. Because of the high price of SLC, the selection of a CPU with more SLC should only be considered when it is not possible to add more CPUs
|
|
Clock Rate - The clock rate of the processors is least important, since an increase in the clock rate by 10% will effectively increase performance only 2-3%. Acceptable performance increases can be achieved by using the latest model processors.
|
|
Memory—Microsoft SQL Server is very good at utilizing the available memory. All tables are loaded in memory upon first use. When tables are present in the memory, all read and write transactions are committed to the memory without having to use the slower disk system. Minimizing communication to disks is one of the primary means to obtaining better performance. On checkpoints, Microsoft SQL Server flushes to the disks any changes to the tables in the memory.
The minimum amount of memory is 512 MB. However, the maximum amount of memory that can be afforded should be configured because it increases performance. Reducing the amount of memory will increase the load on the disk system, which will slow down the overall performance.
|
|
Storage System
To ensure acceptable performance at peak times, the storage system should be sized for the maximum workload created by the Microsoft SQL Server Option for Navision. A sufficient amount of memory should be configured before the storage system is designed. If the memory is insufficient, the excessive workload on the storage system will create a demand for a faster and more expensive storage system than needed. The type of RAID protection to use for each file type (Database, Transaction Log, Tempdb, etc.) needs to be taken into consideration. Below is a chart with suggestions for what RAID level to use for each file type used with Microsoft SQL.
File Types RAID 1 RAID 0+1
OS + SQL Server Files XX b
Database Files XX
Log Files XX XX
TempDB XX XX
|
|
Network
The Navision client creates a log of network traffic when it runs on Microsoft SQL Server. The network's limiting factor is the number of packets that can be transmitted per second. A properly segmented 100-Mbit network is suggested. If the Microsoft SQL Server Option for Navision is deployed in a 10-Mbit network, server-based computing should be used to avoid a bottleneck in the network (Terminal Server or Citrix).
|
|
|
