Dynamics Ax 2012 R3 System Requirements
Ophelia Gurin
This article lists the system requirements for cloud deployments of the current version of Dynamics 365 Commerce. If this step is appropriate, before you install Commerce, you should verify that the system that you're working with meets or exceeds the minimum network, hardware, and software requirements.
It is possible for the Safari browser to show an error during device activation of a Store Commerce for web device due to a Microsoft Entra token being unattainable. You can resolve this issue by utilizing the Microsoft Enterprise SSO plug-in for Apple devices.
Don't calculate bandwidth requirements from a client location by multiplying the number of users by the minimum bandwidth requirements. The concurrent usage of a given location is very difficult to calculate. Customers who are concerned about bandwidth requirements should use a preview version of Commerce.
Commerce requires the Microsoft .NET Framework version 4.7.2 or later for Call ClickOnce applications, such as the document routing agent. For installation instructions, see Install the .NET Framework for developers. For Commerce client components (sealed or legacy installers), we recommend that you always use the latest version of the .NET Framework that is available.
It's critical to perform proper performance testing before going live in production. The following are considered minimum system requirements for applications to function. To achieve desired performance, consider concepts like data volumes, transactional load per hour, and customization impact. Proper performance testing, both early into implementation and again before final testing, allows for any necessary performance improvements to be made and validates that the base solution meets the expected operation times required.
If the self-service component uses an SQL database, we highly recommend that you review SQL Server versions and licenses. We recommend that you use a SQL Server version that is currently still within the mainstream support date. You can search for support dates by product in Search Product and Services Lifecycle Information. SQL databases for self-service components require SQL Server 2017 or later. The SQL Server version used must have the Full-Text Search feature installed. We recommend that you always use the latest version that is available, and install all the latest service packs. By following these recommendations, you can help ensure both compatibility and security. The legacy self-service installers also support SQL Server 2016 with Service Pack 2 or later.
If the self-service component uses a server certificate, it's critical that you manage certificates for expiration. By default, certificates expire after one calendar year (365 days). Self-service components that use a server certificate include Hardware station or Commerce Scale Unit (self-hosted).
The Windows 7 and Windows 8 operating systems aren't supported for anything except security-related fixes. Although Commerce components might work on these operating systems, no bug fix or other technical support is provided.
If an offline database will be used, the computer must meet all system requirements for SQL Server. Additionally, the system must have at least 15 gigabytes (GB) of available disk space. However, we recommend a minimum of 25 GB of available disk space.
Remember that performance testing is crucial to the successful use of Commerce self-service components. Across all components, the following bare-minimum system is supported for testing functionality:
The minimum system requirements for Commerce Scale Unit (self-hosted) describe the bare minimum that are required to function, typically in a test scenario. The requirements that are described here aren't representative of a realistic production environment. It's critical that you do appropriate performance testing and validate that the computer hardware to be used meets the demands of Hardware station, Store Commerce app, Store Commerce for web, and any third-party components that access and use the Commerce Scale Unit (self-hosted) component or computer. Furthermore, we highly recommend that you use a standard licensed version of SQL Server or better (for example, Enterprise version) to take advantage of the full capabilities of the processor and RAM.
As for Commerce Scale Unit (self-hosted), larger, server-grade hardware is often required to handle the throughput of a whole enterprise architecture of legacy POS systems. Nevertheless, here's the absolute minimum that is required to test functionality:
Often (especially in corporate environments), network-related security requires that specific exceptions be noted. In these security-focused networks, Microsoft recommends that you add, at a minimum, the following exceptions to a network-related allow list:
The only supported collation for Commerce databases in the cloud is SQL_Latin1_General_CP1_CI_AS. Ensure that your SQL Server and database collations in development environments use this collation setting, and that any configuration environments that are published to the sandbox have this same collation.
Is there a reason why versions of GP running on SQL Server 7 and 2000 recommended RAID 10 and newer GP system requirements do not? (I see RAID 10 dropping off GP 2010 with SQL 2005/2008 system requirements.)
With the move to virtualized servers, I rarely get asked about physical hardware servers so I'm a bit rusty on RAID configurations. (Most articles about this are several years old. I know the value of SSD, but am fuzzy on the State of RAID.)
The specific query from one of our GP clients is what RAID configuration they should deploy for an HP ProLiant DL380 with P408i-A RAID controller and 480GB SATA RI drives. (They prefer to move away from RAID 5 due to concerns about drive loss during rebuilds.)
I concur with Derek on this one.. Personally I'd guess that those specs were inherited from the old days where you still had 'physical' HW for your servers running SQL & GP, thus it make big sense to use RAID disks.. Nowadays with virtualization, not so much anymore.
But the true point is what Derek emphasized on: the partition setup for the SQL server databases.. I see too many customers that don't pay attention to those little details and setup their enviornment with only 2 disks: 1 primary for the OS and 1 large (usually 1TB) for the SQL databases.. It certainly is going to work, but you run your production on a risky setup (single data structure from the OS perspective) that might break in case something goes havoc on the OS side (thruth be told, I've never seen it ever since I started using virtualization)..
Microsoft's recommendation about seggregation of data disks is more about avoiding your disks getting filled out by TempDB overflow of Transaction Logs that grew out of control due to improper backup settings or jobs (could simply be failing without being noticed).
PS: not saying RAID isn't used anymore today, but it's handled by the underlying host infrasctructure that manages all your disks (SAN, NAS, whatever you call it). Certainly disks are still redundant today, but no longer does the OS have to deal with it using dedicated RAID controllers and drivers (which was another point of failure)
It is recommended to always isolate the Microsoft Dynamics GP database log files on a dedicated RAID 1 or RAID 10 volume. This is to ensure that SQL Server can always write to the log file as fast as possible with no contention from the MDF Input/Output (I/O) activity. This will have a positive impact on the performance of SQL statements (inserts, updates, deletes) in the database because SQL Server can continue to the next statement as soon as the log is written.
It is recommended to always isolate the Microsoft Dynamics GP database data files on a dedicated RAID 5 or RAID 10 volume. Ensure you have adequate disks to handle your I/O load, otherwise latency will increase once the disks are saturated.
It is recommended to always isolate the TEMPDB database files (MDF and LDF) on a dedicated RAID 1 or RAID 10 volume. Performance may also benefit by creating 1 data file per CPU for TEMPDB as recommended in the article below.
For all of you out there who are curious about the needs for the latest version of Microsoft Dynamics GP 2010 here is the post that will help you decipher the requirements chart from Microsoft. In the requirements table they break everything down by what they term customer profiles. This is the attempt at best fitting the needs for GP based on what your organizations plans are for the software.
There are a few new customer profiles for 2010 that will help place you into a comfortable server spec for running Microsoft Dynamics GP 2010 successfully in your organization. They are shown below as profiles 1-4, and this will allow you to easily see the specs that are suggested based on your concurrent number of GP users and expected system transaction volumes.
This profile will be the option if you have 20-60 concurrent users and process 1,000-4,000 transactions per day, have data importing such as through eConnect, Integration Manager or other reporting or happen to be using terminal services with GP.
As a matter of practice you should also understand that these are rated as the minimum requirements from Microsoft. More memory never hurts so adding a little more is always better. Another note for the listed Microsoft SQL requirements is that if you plan on using the SQL Server 2008 Express Edition or the SQL Server 2005 Express Edition it can be installed on a non-server operating system. However, it is recommended by Microsoft that you install it on a server operating system.
Dear Sir,
I want to know if there is any impact on the performance of the software if I operated the server with NIC 100 Mbps
will the performance increase if I used NIC 1000 Mbps with switch that supports this speed??
3. When you deploy a system in a virtual environment, make sure that you have
sufficient hard disk space to avoid performance problems. Each computer that you deploy in a virtual environment should meet or exceed the random access memory (RAM) requirements and the hard disk space requirements. For more information, click the following article number 897615 to view the Support policy for Microsoft software running in non-Microsoft hardware virtualization software.