MODULE 1: INFRASTRUCTURE AND CAPACITY

PLANNING FOR MICROSOFT DYNAMICS AX 2012

Module Overview
This module provides the high level information that is required for an
administrator to perform sizing for an instance of Microsoft Dynamics® AX 2012.
To perform this sizing, an administrator must combine his or her understanding of
the Microsoft Dynamics AX 2012 architecture, and the performance characteristics
with relevant information on how Microsoft Dynamics AX 2012 will be used. In
this module, you learn the fundamentals of the Microsoft Dynamics AX 2012
system architecture. Sizing guidelines and benchmarks are included to use as
references. Additionally, the guidelines and benchmarks are provided with a
sample set of questions to ask a company that relate to performance.

Objectives

The objectives are:

• Review the Microsoft Dynamics AX 2012 system architecture.

• Explore the frequently asked questions when sizing hardware.
• Describe the performance benchmarks to use when planning for
performance.

Microsoft Official Training Materials for Microsoft Dynamics ® 01 - 1

Your use of this content is subject to your current services agreement
SQL Optimization for Microsoft Dynamics® AX 2012

Microsoft Dynamics AX 2012 Architecture Review

Examining the Microsoft Dynamics AX 2012 architecture is the first step in
planning the infrastructure. This lesson provides a high-level overview of the
system architecture as it relates to performance planning.

System Architecture

The Microsoft Dynamics AX 2012 system architecture includes several server

components that are necessary to plan the infrastructure. Depending on the
technical requirements, some components can be deployed. Additionally,
components can exist on a single physical server or across multiple physical
servers.

For information about how to understand the minimum requirements

for Microsoft Dynamics AX 2012, refer to the Microsoft Dynamics AX 2012
System Requirements documentation.

http://go.microsoft.com/fwlink/?LinkId=286895

For more information about the Microsoft Dynamics AX 2012

architecture and planning the infrastructure, refer to the Microsoft Dynamics
AX 2012 Implementation Planning Guide.

http://go.microsoft.com/fwlink/?LinkId=286896

The Logical view of the Microsoft Dynamics AX system architecture figure

provides a logical view of the system architecture and how each component
interacts in the environment.

01 - 2 Microsoft Official Training Materials for Microsoft Dynamics ®

Your use of this content is subject to your current services agreement
Module 1: Infrastructure and Capacity Planning for Microsoft Dynamics AX 2012

FIGURE 1.1: LOGICAL VIEW OF MICROSOFT DYNAMICS AX 2012

ARCHITECTURE

Three-Tier Architecture

Microsoft Dynamics AX 2012 supports a three-tier architecture that segregates the

database, the application, and the client. The SQL Server database exists on the
data tier and stores the application’s data in tables.

The Application Object Server (AOS) exists on the application tier and is
responsible to run the business logic that is contained in application objects, such
as table methods and classes.

The client exists in the presentation tier and displays application objects that are
related to the user interface (UI) and includes forms and reports.

Data Tier

In Microsoft Dynamics AX 2012, several required database components exist on

the data tier.

Microsoft Official Training Materials for Microsoft Dynamics ® 01 - 3

Your use of this content is subject to your current services agreement
SQL Optimization for Microsoft Dynamics® AX 2012
The Microsoft Dynamics AX 2012 Database

The Microsoft Dynamics AX 2012 database is a relational database that is built on

the Microsoft SQL Server platform. This is the primary database that is used to
store both transactional and referential data.

The Model Store

The model store is a SQL Server database that is used to store all models that have
application elements and customizations. The model store replaces the
Application Object Data (AOD) files that are in the application folder in earlier
versions of Microsoft Dynamics AX 2012.

Note: In Microsoft Dynamics AX 2012 R2, the model store is moved from the
Microsoft Dynamics AX 2012 database to its own database instance. The naming
convention for the model store is the name of the Microsoft Dynamics AX 2012
database plus “_model”.

The Reporting Services Database

The Report Server database stores the metadata and object definitions for
Microsoft SQL Server Reporting Services reports in Microsoft Dynamics AX 2012.
The Report Server includes two separate databases named “reportserver” and
“reportservertempdb.” These databases store permanent and temporary data.

The Analysis Services Database

The analytical features, such as Online Analytical Processing (OLAP) cubes and Key
Performance Indicators (KPIs) for Microsoft Dynamics AX 2012 are stored in the
Microsoft SQL Server Analysis Services database.

The Enterprise Portal Database

Enterprise Portal requires the content and the configuration of the databases for
Microsoft SharePoint® products.

Application Tier

The application tier contains many components and services that are responsible
for running business logic for Microsoft Dynamics AX 2012.

Application Object Server (AOS)

The AOS manages the communication between the clients and the database. The
AOS also hosts services, such as the workflow system, and it performs security and
runs the business logic for Microsoft Dynamics AX 2012. The AOS can effectively
balance the client load across multiple AOS servers or instances.

01 - 4 Microsoft Official Training Materials for Microsoft Dynamics ®

Your use of this content is subject to your current services agreement
Module 1: Infrastructure and Capacity Planning for Microsoft Dynamics AX 2012
Enterprise Portal

Enterprise Portal is a set of websites that are used to access Microsoft Dynamics
AX 2012 data and business processes by using web-based forms. Enterprise Portal
is hosted on Internet Information Services (IIS) and Microsoft SharePoint
Foundation 2010 or Microsoft SharePoint Server 2010.

Reporting and Analytics

Microsoft Dynamics AX 2012 uses Microsoft SQL Server Reporting Services (SSRS)
and SQL Server Analysis Services (SSAS) to create traditional and online analytical
processing (OLAP) reports to view data and analyze business trends.

Workflow

Workflow lets users define the flow of a business process through Microsoft
Dynamics AX. The workflow system is included in the AOS installation process.

Services and Application Integration Framework (AIF)

Services and the AIF let other internal and external systems communicate through
XML with Microsoft Dynamics AX 2012.

Help Server

The Help system hosts product documentation on a dedicated server component

and displays the Help information to the client.

Presentation Tier

The presentation tier provides a client application or interface to Microsoft

Dynamics AX 2012.

Microsoft Dynamics AX 2012 Client

The Microsoft Dynamics AX 2012 Client is a native 32-bit program that is used to
access all forms, reports, and queries in Microsoft Dynamics AX 2012.

Enterprise Portal

Users who do not require access to many features that are available in the
Microsoft Dynamics AX 2012 Client can use web-based forms that are hosted on
the Enterprise Portal.

Microsoft Official Training Materials for Microsoft Dynamics ® 01 - 5

Your use of this content is subject to your current services agreement
SQL Optimization for Microsoft Dynamics® AX 2012
External Applications

Third-party applications can interact with Microsoft Dynamics AX 2012 by using

services and the AIF.

Reporting Architecture

The Reporting Architecture figure shows the architecture of the reporting

functionality in Microsoft Dynamics AX 2012.

FIGURE 1.2: REPORTING ARCHITECTURE

When a report is created, the following actions occur:

1. A user requests a report.

2. Reporting Services receives the request and asks the Microsoft
Dynamics AX server for the report data.
3. The Microsoft Dynamics AX server receives the request and sends the
report data back to Reporting Services.
4. Reporting Services creates the report and sends it to the Microsoft
Dynamics AX client.
5. The report is displayed to the user.

01 - 6 Microsoft Official Training Materials for Microsoft Dynamics ®

Your use of this content is subject to your current services agreement
Module 1: Infrastructure and Capacity Planning for Microsoft Dynamics AX 2012
Enterprise Portal Architecture

Microsoft Dynamics AX provides a set of websites that give you access to data. On
these sites, you can also participate in business processes by using web-based
forms. These combined websites are called the Enterprise Portal. The Enterprise
Portal requires Internet Information Services (IIS). IIS is a feature of Windows
Server, and either Microsoft SharePoint Foundation 2010 or Microsoft SharePoint
Server 2010.

The Enterprise Portal Architecture figure shows a high-level overview of the

Enterprise Portal Architecture.

FIGURE 1.3: ENTERPRISE PORTAL ARCHITECTURE

Microsoft Official Training Materials for Microsoft Dynamics ® 01 - 7

Your use of this content is subject to your current services agreement
SQL Optimization for Microsoft Dynamics® AX 2012

Sizing Questions
A basic set of questions for the administrator to ask when he or she performs
hardware sizing for an instance of Microsoft Dynamics AX 2012 is available.
Although this is not a complete list of questions, it is a good way to start.

Every implementation has unique characteristics that you must consider when you
perform hardware sizing. The administrator is responsible for performing
hardware sizing, and should continue to ask questions until he or she understands
the system requirements. By doing this, the administrator can use his or her
knowledge of the Microsoft Dynamics AX 2012 architecture, sizing guidelines, and
benchmarks to create an acceptable hardware plan.

What is the Maximum Transaction Volume Expected in an

Hour, During Peak Season?

All components of the Microsoft Dynamics AX 2012 architecture must be

designed to handle the largest number of transactions a company will process in
the busiest day and year of the hardware’s expected lifetime.

All transaction types should be considered including, but not limited to, the
following:

• Sales order lines

• Purchase order lines
• Production order lines
• Inventory transfers and adjustments
• Financial postings
• Other transactions

What is the Record Count for Master Data?

The current number of records for master data should also be measured to help
estimate the initial size of the Microsoft Dynamics AX 2012 database. For most
implementations, transaction volume will be an important element in determining
the overall size of the database. However, if there is significant master data such as
four million customers, this will significantly affect the starting size of the
database.

01 - 8 Microsoft Official Training Materials for Microsoft Dynamics ®

Your use of this content is subject to your current services agreement
Module 1: Infrastructure and Capacity Planning for Microsoft Dynamics AX 2012
Master data can include, but is not limited to, the following:

• Customers
• Vendors
• Products
• Zip codes
• Other

Which Modules will be Used in the Microsoft Dynamics AX

2012 Application?

Take an inventory of the modules and the processes that will be used after the
Microsoft Dynamics AX 2012 deployment, to assess the hardware that will be
required to configure the environment.

Examples can include Accounts Receivable, Sales order processing, the General
Ledger, and so on.

If Role Centers or Enterprise Portal will be deployed, a web server that runs
Internet Information Services (IIS) will be required.

Each module that is used increases the over transactions that are processed and
the complexity of the system. These must be considered when you perform
hardware sizing.

Will any Add-on to Microsoft Dynamics AX 2012 be used?

There are many companies that have customized Microsoft Dynamics AX 2012.
These customization’s or improvements increases the complexity of the code base,
and you must consider them when you perform hardware sizing.

Will Microsoft Dynamics AX 2012 have to Integrate to

Third-Party Systems?

Understanding the integration projects that are related to the Microsoft Dynamics
AX 2012 deployment is important when you plan the hardware.

Microsoft Official Training Materials for Microsoft Dynamics ® 01 - 9

Your use of this content is subject to your current services agreement
SQL Optimization for Microsoft Dynamics® AX 2012
The following questions can help determine the hardware requirements for the
correct integration with Microsoft Dynamics AX 2012:

• What systems will be integrated with Microsoft Dynamics AX 2012?

• What is the expected transport method?
o The transport method for the integration document can help
identify any additional servers that might be required. For
example, use of the File system adapter to an external system
might require an FTP server to securely store the file for transport.
However, use of Application Integration Framework web services
will require a web server that runs IIS to host the services. If high
transaction volume is expected, an enterprise service bus such as
Microsoft BizTalk Server might be necessary and will also require
additional hardware.

• Should the communication method be synchronous or asynchronous?

o If documents must be sent or received in a particular order, the
integration point might require synchronous communication not
to send another document until the previous document is
received.

Are there any Major Customizations that must be Created?

Most companies have unique characteristics that help them differ from their
competition. Many of these unique characteristics must be included in the
Microsoft Dynamics AX 2012 implementation so that it runs efficiently. Including
these unique characteristics requires that modifications be created, and these
modifications can have a significant effect on performance.

List any major customizations that are planned. Also list the general method that
will be used to perform the customizations if this data is available when hardware
sizing is performed.

How Many Users Will Access the Microsoft Dynamics AX

2012 System?

Ideally, you will want to know how many users will be accessing Microsoft
Dynamics AX 2012. Although it is not as important to know the user count as it is
the transaction volume when planning the number of Application Object Servers
(AOS) to deploy, it is especially useful when planning processor requirements for
the Enterprise Portal. Enterprise Portal offers several self-service type tasks.
Therefore, you should understand the expected concurrent user sessions during
peak hours to handle the workload accordingly.

01 - 10 Microsoft Official Training Materials for Microsoft Dynamics ®

Your use of this content is subject to your current services agreement
Module 1: Infrastructure and Capacity Planning for Microsoft Dynamics AX 2012
When you identify the number of total and concurrent users, consider each
connection type, and include the following:

• Microsoft Dynamics AX 2012 Client

• Enterprise Portal websites
• Devices or external applications through AOS services or the Business
Connector

Will Users Access the Microsoft Dynamics AX 2012 Client

over a Wide Area Network?

We do not recommend that you access the Microsoft Dynamics AX 2012 Client
over a Wide Area Network (WAN) without an application sharing program such
as, Remote Desktop Services. Remote Desktop Services can provide users’ access
to the Microsoft Dynamics AX Client that is installed on a Windows-based server
that is located on the Local Area Network. This is where the Microsoft Dynamics
AX 2012 server components are located. An additional server is required to host
the Remote Desktop Services feature for Windows Server 2008.

If Remote Desktop Services is required, consider the number of users who are
required to connect to the Microsoft Dynamics AX Client through the terminal
server. General memory and processor requirements can be identified based on
user counts.

Note: If latency on the network is greater than 50 milliseconds (MS), use of

Remote Desktop Services is also recommended.

Are There Significant Enterprise Portal Requirements?

The Enterprise Portal can be used to display role centers in Microsoft Dynamics AX
2012, provide the time and expense entry for a whole organization, or provide a
portal in Microsoft Dynamics AX 2012 for vendors.

Each of these scenarios present a different type of workload and require different
sizing requirements.

For example, a vendor portal must be available through the Internet, expense and
time entry systems will be busy two days a month and idle otherwise, and role
centers will present a smaller consistent load.

Microsoft Official Training Materials for Microsoft Dynamics ® 01 - 11

Your use of this content is subject to your current services agreement
SQL Optimization for Microsoft Dynamics® AX 2012
Are There Significant Processes Run in Batch Mode?

Processes such as sales order invoicing can require significant resources to run
efficiently. You must understand any required batch processes to correctly
allocate Application Object Servers (AOS) that are designated to run batch jobs
and the number of available threads for each AOS.

When you access the processor and memory requirements for batch servers,
identify the maximum duration that is allowed for the process to complete (batch
window characterization) through performance testing and benchmarks.

For multiple batch processes or processes with multiple threads, try to cluster
AOSs to support the many workloads. Critical batch processes should be allocated
across AOSs through Network Load Balancing to guarantee high availability.

Does the Company Want a Dedicated Load Balancing AOS?

Microsoft Dynamics AX 2012 provides the option to dedicate the AOS to just load
balancing. Load balancing can be achieved without a dedicated server, and has
minimal effect on AOS performance. Dedicated load balancing servers should be
used only for companies who have user counts in the thousands.

For more information about dedicated load balancing AOS’s, refer to

the AOS Clusters with a Dedicated Load Balancer TechNet article.

http://go.microsoft.com/fwlink/?LinkId=286904

How Many Environments Will be Used for the

Implementation?

For a typical implementation, the Development, Test, and Production environment

are deployed. However, sometimes many additional environments are required.

When you plan the architecture for Microsoft Dynamics AX 2012, include the
hardware that is required to run all environments, not just production. Some other
environments that might be useful in an implementation are described in the
following table.

Name Description
Training The environment that is dedicated to training users, and
does not have the data or code changes that are
associated with the test environment during the
implementation.

01 - 12 Microsoft Official Training Materials for Microsoft Dynamics ®

Your use of this content is subject to your current services agreement
Module 1: Infrastructure and Capacity Planning for Microsoft Dynamics AX 2012
Name Description
Base The environment that has only Microsoft Dynamics AX
2012 and no customizations or third-parties. This is
useful to identify issues, and how the environment
originally worked.

Staging Staging is a direct copy of the production environment

that is used for code promotion to production.
For more information about how to use the staging
environment to move code to production, refer to the
Deploying Customizations Across Microsoft Dynamics
AX 2012 Environments white paper.

http://go.microsoft.com/fwlink/?LinkId=286897

Performance The environment that is dedicated to the initial

performance testing.

ProductionCopy The environment that is a frequently restored copy of

the production environment that is used to review data
issues.

Does the Company Need High Availability for its AOSs?

Microsoft Dynamics AX 2012 can connect to another AOS if the first AOS is
unavailable. However, to do this, the company must have multiple AOS servers. An
N+1 methodology should be applied when high availability of AOS servers is
required, where N is the number of server or instances recommended. For
example, if three AOS servers are required to handle day to day volume, than four
AOSs would be required to handle day to day volume and provide high
availability.

For information about how to configure AOSs for redundancy, refer to

the Microsoft Dynamics AX 2012 Server Configuration (form) page.

http://go.microsoft.com/fwlink/?LinkId=286905

Microsoft Official Training Materials for Microsoft Dynamics ® 01 - 13

Your use of this content is subject to your current services agreement
SQL Optimization for Microsoft Dynamics® AX 2012
Does the Company Need High Availability for IIS?

IIS can be used by Microsoft Dynamics AX 2012 to host web services, help server,
and the Enterprise Portal. If any of these components requires more availability,
then the N+ 1 methodology should be applied when there is an increase for IIS,
where N is the number of servers or instances recommended. For example if
three IIS servers are required to handle day to day volume, than four IIS servers
would be required to handle day to day volume and provide high availability.

The Configuring a Web Farm by Using the IIS Shared Configuration

webpage includes a video that contains detailed information about how to
set up a web farm by using IIS and Network Load Balancing.

http://go.microsoft.com/fwlink/?LinkId=286898

Does the Company Need High Availability for Remote

Desktop Services?

Terminal Services Session Broker Load Balancing can be set up for Remote
Desktop Services. This provides high availability and load balance between
Remote Desktop Services servers. An N+1 methodology should be applied when
high availability of Remote Desktop Services servers is required, where N is the
number of server or instances recommended.

For example, if three Remote Desktop Services servers are required to handle day
to day volume, than four Remote Desktop Services servers would be required to
handle day to day volume and provide high availability.

Refer to the TS Session Broker Load Balancing Step-by-Step Guide for more
information about how to set up Terminal Services Session Broker for Load
Balancing.

http://go.microsoft.com/fwlink/?LinkId=286900

Is Database Failover Required?

If Microsoft Dynamics AX 2012 must be continuously operational, database

failover must be configured. AlwaysOn Failover Cluster Instances that use
Windows Server Failover Clustering (WSFC) provides the foundation for failover
for applications such as Microsoft SQL Server 2012.

WSFC and SQL Failover Clustering can automatically transfer the application from
one cluster node to another to provide high availability and minimize disaster
recovery scenarios. Consider the additional hardware and software licensing that
is required.

01 - 14 Microsoft Official Training Materials for Microsoft Dynamics ®

Your use of this content is subject to your current services agreement
Module 1: Infrastructure and Capacity Planning for Microsoft Dynamics AX 2012

For more information about high availability solutions for SQL Server
2012, refer to the High Availability Solutions (SQL Server) webpage on the
Microsoft Developer Network (MSDN).

http://go.microsoft.com/fwlink/?LinkId=286906

What Level of Disaster Recovery is Required?

All Microsoft Dynamics AX 2012 deployments should include a disaster recovery

plan. In the event the database or server fails, you must be able to recover the
information and bring Microsoft Dynamics AX 2012 back online.

Although database failover can reduce the risk of a full blown disaster, additional
decisions should be made to create an acceptable plan to recover from a loss.

The following questions can help prepare the hardware requirements to support a
good disaster recovery plan:

• What technology will be used to perform the disaster recovery?

• What is the acceptable failover duration (for example, 15 minutes)?
• What is the acceptable data loss (for example, 1 hour)?
o For Microsoft Dynamics AX 2012 systems with heavy order
volume, acceptable data loss might be minimal.

• Where is the disaster recovery site?

o The disaster recovery site should always be a different physical
and geographic location from the primary Microsoft Dynamics
AX 2012 database server, in the event the building is
compromised by a natural disaster.

• What mechanisms will be used to provide disaster recovery?

For more information about disaster recovery for Microsoft SQL Server,
refer to the Planning for Disaster Recovery article on MSDN.

http://go.microsoft.com/fwlink/?LinkId=286907

Microsoft Official Training Materials for Microsoft Dynamics ® 01 - 15

Your use of this content is subject to your current services agreement
SQL Optimization for Microsoft Dynamics® AX 2012
What is the Backup Strategy?

You must have a database backup strategy to recover from a damaged database
or other data loss. A successful backup strategy involves two parts—backup and
restore.

The backup strategy must include the definition of the type of backup (Full,
Differential, or Transaction Log), the frequency of the backup (for example, every
hour), and where the backup will be stored just to name some.

The restore strategy must include the responsible party to achieve the database
restore and outline the criteria to determine a successful restore.

Note: The backup strategy must always include a periodic restore of the
database and the test plan against Microsoft Dynamics AX 2012 to make sure that
a successful restore can occur in a real-life disaster recovery scenario.

Answers to the following questions will help you understand the hardware that is
required to support the speed and nature of the backup strategy.

• How many hours each day is Microsoft Dynamics AX 2012 in use?

Full database backups should be taken either off-peak hours, or from a synchronous
partner in an AlwaysOn availability group.

For more information about taking a backup from a synchronous

partner in an AlwaysOn availability group, refer to the Active Secondary:
Backup on Secondary Replicas (AlwaysOn Availability Groups) article on
MSDN.

http://go.microsoft.com/fwlink/?LinkId=286908

• How much disk space will a full database backup require?

o Estimating disk space for a full database backup might be difficult
before deployment. However, you can use the sp_spaceused
stored procedure to help with the estimation when the Microsoft
Dynamics AX 2012 database is deployed.
o Will compression be used on database backups?

01 - 16 Microsoft Official Training Materials for Microsoft Dynamics ®

Your use of this content is subject to your current services agreement
 Module 1: Infrastructure and Capacity Planning for Microsoft Dynamics AX 2012
• How frequently does the data change in Microsoft Dynamics AX
2012?
o The frequency of data changed, and the importance of that data
will help determine acceptable data loss for the production
database.

• How frequently does the code change in Microsoft Dynamics AX

2012?
o The model database stores code changes should be backed up
frequently to avoid the loss of code changes.

• What is the acceptable data loss?

o The frequency of changes in the database and the acceptable loss
of data should determine the recovery model that is selected for
the backup strategy.

Note: Make sure that the database is set to Full Recovery.

For more information about how to design a backup strategy with

Microsoft SQL Server, refer to the Introduction to Backup and Restore
Strategies in the SQL Server article on MSDN.

http://go.microsoft.com/fwlink/?LinkId=286909

Hardware Sizing Resources

When you plan the hardware requirements, it is important to be familiar with the
general hardware sizing guidelines to accurately configure the Microsoft
Dynamics AX 2012 environment. The hardware sizing guidelines discussed in this
lesson are a baseline used to configure the environment that is based on the
answers to the questions in the earlier lesson.

You can use performance benchmarks to adjust your environments as needed.

Sizing Guidelines

Hardware sizing guidelines can serve as a baseline for the initial configuration of
Microsoft Dynamics AX 2012.

You should be aware that many factors can affect the sizing guidelines that are
provided and can result in additional processor, memory, and, or storage
requirements.

Microsoft Official Training Materials for Microsoft Dynamics ® 01 - 17

Your use of this content is subject to your current services agreement
SQL Optimization for Microsoft Dynamics® AX 2012
Some elements can include the parameter settings that are being used, the
number of customizations made to the base Microsoft Dynamics AX 2012
application, and the additional features that are used in the application, such as
database logging, user alerts, and document management.

Database Server Sizing Guidelines

Note: Database Server Sizing Guidelines can be used as a starting point for
sizing. However, other elements such as modules used, integrations, and
customizations must be considered when you perform sizing.

The hardware sizing for the Microsoft Dynamics AX 2012 database server should
be based on concurrent transaction volume. It is more important that you
understand the transaction workload than the concurrent user count, because
typically the behavior in the user processes differ by user and the transaction
workload usually remains consistent.

The hardware sizing guidelines include the following:

• CPU – The database server should have one core for every 4,000 to
12,000 transactions entered for every hour, with a minimum of four
cores. For example, an organization that enters 48,000 transactions
for each hour during peak hours should have 4 to 12 cores.

Note: The elements described in the beginning of this lesson can significantly
reduce the recommended transaction workload for every core that is outlined.

• Memory – For every core on the database server, 2 to 4 gigabytes

(GB) of memory should be allocated. For example, a database server
that has 8 cores should have 16 to 32 GB of memory.
• Storage – Data, transaction logs, and tempdb should be stored in a
raid 0+1 array. The data drive must be large enough to hold the
production database, and have the disk throughput to handle
Microsoft Dynamics AX 2012 transaction volumes.

Note: An estimate of disk throughput that is required can be found by using

the following formula:

(Adjusted transactions for each second) * 26 = IOPS

Adjusted transactions for each second = (Max of all transactions for each second +
batch jobs) * 1.5

01 - 18 Microsoft Official Training Materials for Microsoft Dynamics ®

Your use of this content is subject to your current services agreement
Module 1: Infrastructure and Capacity Planning for Microsoft Dynamics AX 2012

Note: The minimum IOPS for the data disk is 750, and the minimum IOPS for
the log disk is 160.

• Miscellaneous – The database server should be dedicated to running

an instance of the SQL Server for Microsoft Dynamics AX 2012.
Applications unrelated to hosting the SQL Server database should not
be installed on this server.

Application Object Server (AOS) Sizing Guidelines

Note: You can use the AOS Sizing Guidelines as a start for sizing. However,
other elements such as the modules used, integrations, and customizations must be
considered when you perform sizing.

Just as with the database server, the AOS should be configured based primarily on
concurrent transaction volume, although concurrent user counts should be
considered.

The following guidelines should be used for sizing Application servers:

• CPU – Each AOS should have one core for every 8,000 to 12,000
transactions entered for every hour. Additionally, one core should
exist for every 25 to 100 concurrent users who access the Microsoft
Dynamics AX 2012 system.
• Memory – 4 GB to 8 GB of memory should be allocated to each AOS
instance.

Note: A similar alternative sizing approach is to create standard AOS servers

of 8 GB ram and 4 cores and add an AOS for every 48,000 transactions for every
hour or 250 users.

• Batch Server – AOS servers designated to run batch jobs should have
one to four threads allocated for each CPU core.

Note: Make sure that you have enough CPU, memory, and that threads are
allocated to batch servers to complete jobs in an acceptable batch window.

Microsoft Official Training Materials for Microsoft Dynamics ® 01 - 19

Your use of this content is subject to your current services agreement
SQL Optimization for Microsoft Dynamics® AX 2012
Enterprise Portal Sizing Guidelines

Note: You can use the Enterprise Portal Sizing Guidelines as a starting for
sizing. However, other elements such as the modules used, integrations, and
customizations must be considered when you perform sizing.

More attention should be given to user concurrency when sizing your Enterprise
Portal web server. Typically, users access the self-service features of the portal at
peak times, such as for the Time and Expense entry at the period end. This usually
results in more user traffic.

Also consider transaction volume and transaction complexity based on

performance benchmarks and internal testing in addition to concurrent user
counts.

Note: If an enterprise portal server is deployed this is frequently a good place

to locate help and perform an enterprise search.

Recommendations for the Enterprise Portal include the following:

• CPU – The Enterprise Portal web server should have 2 to 16 cores,

depending on the user count and the transaction volume/complexity.
Generally, one core for every 40 to 120 concurrent users should be
added.
• Memory – 1/2 GB to 2 GB of memory should be allocated for every
core.

Note: A similar alternative sizing approach is to create standard IIS servers of

8GB ram and 16 cores and add an IIS server for every 800 users.

• Network – Enterprise Portal web servers should be equipped with

Gigabit Ethernet Network Interface Cards and exist on a Gigabit
network.

Integration Server Sizing Guidelines

Note: You can use Integration Sizing Guidelines as a start for sizing. However,
other elements such as the modules used, integrations, and customizations must be
considered when you perform sizing.

01 - 20 Microsoft Official Training Materials for Microsoft Dynamics ®

Your use of this content is subject to your current services agreement
Module 1: Infrastructure and Capacity Planning for Microsoft Dynamics AX 2012
Depending on the integration method, hardware sizing and requirements can
differ. If you are using the File system adapter or Message Queuing (also known
as MSMQ), use a fast disk subsystem to handle the load capacity for file-based
integrations. Additionally, make sure that disk drives use RAID 1 or RAID 0+1 to
guarantee the high availability of the files.

For more information about standard server requirements, refer to the

Microsoft Dynamics AX 2012 System Requirements white paper.

http://go.microsoft.com/fwlink/?LinkID=244192&clcid=0x409

MSMQ can show an improved messaging performance by storing messaging files

on multiple physical disks. If the integration server will host the Message Queue
Server, configure the drives so that the MSMQ information store (MQIS), message-
logger files, and the transaction-logger files are on separate drives.

Refer to the “Deploying MSMQ on TechNet” chapter for more

information about the correct MSMQ configuration.

http://go.microsoft.com/fwlink/?LinkId=286899

Terminal Server Sizing Guidelines

Note: You can use the Remote Desktop Guidelines as a start for sizing.
However, other elements such as the modules used, integrations, and the
customizations must be considered when you perform sizing.

When sizing the Remote Desktop Services, consider the number of client
connections to expect to determine memory requirements. The terminal server
might host additional applications and user controls, such as Microsoft Office, and
this could also increase memory usage for every client.

Base configuration requirements for the Terminal Server include the following:

• CPU – A minimum of two cores should be allocated for the base

Terminal Server.
• Memory – A minimum of 4 GB of memory should be installed in the
base Terminal Server. In addition, 100 Megabytes (MB) to 200 MB of
memory should be allocated for every client connection.

Microsoft Official Training Materials for Microsoft Dynamics ® 01 - 21

Your use of this content is subject to your current services agreement
SQL Optimization for Microsoft Dynamics® AX 2012

Note: A similar alternative sizing approach is to create the standard Remote

Desktop Services server of 32GB ram and 16 cores. And, you must add a Remote
Desktop Services server for every 150 users who use the Microsoft Dynamics AX
2012 client and Office Add-ins and 175 users who just use the Microsoft Dynamics
AX 2012 client.

• Network – If latency on the Local Area Network is over 50

milliseconds or access to the Microsoft Dynamics AX 2012 Client is
required over a Wide Area Network, Remote Desktop Services should
be used.

Benchmarks

Microsoft has released several performance benchmarks. These benchmarks will

help organizations understand the different throughput and response time
measurements for functional processes that run on a specific hardware
configuration. Some processes include Sales order header and line creation,
Purchase order invoicing, and General ledger journal line posting in the Microsoft
Dynamics AX Client, in addition to creating and submitting timesheets through
the Enterprise Portal.

You can use performance benchmarks as additional guidelines for hardware

planning by referencing benchmark statistics against the predicted transactional
volume to make informed decisions about the hardware requirements.

Note: Performance benchmarks are already performed against the base

Microsoft Dynamics AX application in a controlled environment. Any
customizations made to the application or additional applications that run in the
environment can significantly reduce individual results from the statistical data that
is outlined in the benchmark.

Benchmarks whitepapers

http://go.microsoft.com/fwlink/?LinkId=286901

Day in the Life Benchmark

The “Day in the Life” benchmark for Microsoft Dynamics AX 2012 focused on
measuring the base application for performance and scalability. Several functional
processes were applied to determine the average throughput and response time
based on the scenario.

Microsoft used a mixed workload. The workload consisted of Microsoft Dynamics

AX Client simulations, Enterprise portal tasks, Workflow submissions, transaction
imports through AIF services, and batch server processing to demonstrate whether
the application and its supporting architecture could withstand the intense

01 - 22 Microsoft Official Training Materials for Microsoft Dynamics ®

Your use of this content is subject to your current services agreement
Module 1: Infrastructure and Capacity Planning for Microsoft Dynamics AX 2012
workload. A total of 5,135 simulated, concurrent users and associated processes
averaged over one million transactions for every hour. The results from the “Day
in the Life” benchmark are helpful to organizations. The organizations can use the
valuable data to determine the hardware sizing requirements for their database
and application servers.

Enterprise Portal Benchmark

A separate benchmark, implemented for the Enterprise Portal for Microsoft

Dynamics AX 2012, included the simulation of 10,000 concurrent users performing
several tasks such as, time and expense entry, and purchase requisitions. The
throughput and response times measured for the individual tasks were performed
on the Enterprise Portal.

The Enterprise Portal benchmark showed more than 741,587 lines for every hour
were possible on an architecture that consists of two load-balanced AOS instances
servicing ten Enterprise Portal web servers. The hardware configuration and
results for the Enterprise Portal benchmark are also excellent resources for
organizations to help determine application tier hardware requirements.

Details of the Enterprise Portal benchmark results can be found in the

Microsoft Dynamics AX Enterprise Portal benchmark results white paper.

http://go.microsoft.com/fwlink/?LinkID=245627

Hyper-V Benchmark

Knowledge of the unique hardware requirements for virtual servers is an

important step in planning a Microsoft Dynamics AX 2012 virtual environment.

Microsoft released a virtualization benchmark to help ease the process. The

benchmark consisted of 300 simulated, concurrent users who performed several
functional tasks through the Microsoft Dynamics AX Client, the Enterprise Portal
Website, and .NET Business Connector.

The benchmark tested a combination of physical and virtual servers to determine

response time, CPU usage, and throughput of the many configurations. The
results showed different performance degradation scenarios, depending on the
servers in the Microsoft Dynamics AX architecture that were virtualized.
Referencing the Hyper-V benchmark cannot only determine hardware
requirements for virtual servers, but make informed decisions on the components
that should remain on a physical server.

Microsoft Official Training Materials for Microsoft Dynamics ® 01 - 23

Your use of this content is subject to your current services agreement
SQL Optimization for Microsoft Dynamics® AX 2012

For more information about the Hyper-V benchmark results, refer to

the Microsoft Dynamics AX virtualization benchmark results white paper.

http://go.microsoft.com/fwlink/?LinkId=245625

High Volume Inventory Benchmark for Retail

Environments

The “High Volume Inventory Benchmark for Retail Environments” was performed
to demonstrate that Microsoft Dynamics AX 2012 can handle high transaction
volumes.

The benchmark simulated an inventory workload of more than 4.96 million

transaction lines. This included the import of point of sale transactions into
Microsoft Dynamics AX, the physical transfer of inventory to stores, and the arrival
of new inventory. A total of 3.68 million Inventory journal lines were created and
posted in less than one hour.

Using the performance benchmarks for the retail scenario can provide the
awareness of the hardware requirements for other integration projects.

Note: Integrating external systems can have different performance results

than what is stated in the “High Volume Inventory for Benchmark for Retail
Environments” white paper. Always test and perform your own benchmarks to
make sure that performance meets the requirements of the organization.

Refer to the “High Volume Inventory Benchmark for Retail

Environments” white paper for more information.

http://go.microsoft.com/fwlink/?LinkId=266254

01 - 24 Microsoft Official Training Materials for Microsoft Dynamics ®

Your use of this content is subject to your current services agreement
 Module 1: Infrastructure and Capacity Planning for Microsoft Dynamics AX 2012

Moving from Theory to Practice

After learning about the Microsoft Dynamics AX 2012 architecture, collecting
information, and reviewing sizing guidelines and benchmarks, this information
must be collected in a plan. In this lesson, you will combine all the information
into a Microsoft Dynamics AX 2012 infrastructure.

Create a Network Plan

When you perform sizing for an instance of Microsoft Dynamics AX 2012, you
must communicate the findings to other people. To do this, create a network plan.

Some tools available to create a network plan include the following:

• Microsoft Visio
• Microsoft Word
• Microsoft Excel

Visio can be used to create a graphical representation of a network that shows the
relationships between servers. Excel can be used to obtain and keep details in an
organized way. For example, an Excel spreadsheet with columns that include
servers and rows that include components can help maintain the specifics of the
implementation architecture.

Word can be used to combine different types of data, such as images, diagrams,
tables, and formatted text into a single printable document.

After you select a tool to obtain the Microsoft Dynamics AX 2012 network plan, is
it important to make sure that the following information exists:

• Server name
• Server description and role
• Software that is installed
o Operating System, Microsoft Dynamics AX 2012 Component,
Database, and so on
• Hardware
• Relationship to other servers

Microsoft Official Training Materials for Microsoft Dynamics ® 01 - 25

Your use of this content is subject to your current services agreement
SQL Optimization for Microsoft Dynamics® AX 2012

FIGURE 1.4: SAMPLE NETWORK PLAN

How Many AOSs are Needed and How Big Should They
Be?

An AOS in Microsoft Dynamics AX 2012 can both scale up and scale out to
increase throughput.

The following questions help determine the size and count of AOS servers that are
required:

• Does the company want redundant AOSs? If this is the case, then
there must be at least two AOSs dedicated to users.
• Should user load be load balanced between several AOSs? If this is
the case, then there must be at least two AOSs dedicated to users.
• Is the transaction volume associated with the users expected to be
significant? If this is the case, multiple AOSs or large AOS servers
should be deployed. Refer to the Hardware Sizing Resources section
for both AOS sizing guidelines, and the benchmarks to use as the
comparisons.
• Does the company need a dedicated load balancing AOS? If this is
the case, then an additional AOS is required.
• Does the company need AOSs dedicated to integrations? If this is the
case, then additional AOSs are required.
• Does the company need AOSs dedicated to batch processes? If this is
the case, then additional AOSs are required.

01 - 26 Microsoft Official Training Materials for Microsoft Dynamics ®

Your use of this content is subject to your current services agreement
Module 1: Infrastructure and Capacity Planning for Microsoft Dynamics AX 2012
Is a Dedicated Batch AOS Server Required?

If the load that is associated with running batch processes will interfere with the
end-users ability to use the system, then a dedicated batch AOS server should be
considered. If the load associated with this batch server cannot be completed in
the desired time, then larger or additional batch servers should be considered.

Is a Dedicated Server for Integrations Required?

There are several elements that must be considered to determine whether a

dedicated server for integrations is required.

These elements include the following:

• Will the load that is associated with the integrations adversely affect
other processes or users?
• What is the expected transaction volume of the integrations?
• Will separating the integration to the separate server simplify
administration?

Should Virtualization Be Used?

Virtualization is a powerful administration tool that gives administrators significant

flexibility in creating servers, and allocating resources between servers. However,
there is a performance cost that is associated with virtualization that must be
considered, and because of this, SQL Server should be hosted on a physical server
if this is possible.

Additionally, the size and number of physical servers can be different when you
deploy the environment on the virtual or physical hardware.

Note: The “Hyper-V benchmark for Microsoft Dynamics AX 2012” white

paper discussed in the Hardware Sizing Resources lesson provides significant
information on the effect of using Hyper-V virtualization on all components of
Microsoft Dynamics AX 2012.

Failover Cluster Impact

If the SQL Server AlwaysOn Failover Cluster is required, then a second database
server must be added. The secondary database server will have its own memory,
processor, and operating system disks, although the disks associated with SQL
Server will be shared.

Microsoft Official Training Materials for Microsoft Dynamics ® 01 - 27

Your use of this content is subject to your current services agreement
SQL Optimization for Microsoft Dynamics® AX 2012
Does the Company Need a Separate Server for the
Enterprise Portal or Role Centers that Include SharePoint?

Several considerations exist in determining whether a separate server should be

dedicated to hosting the Enterprise Portal. Consider the following:

• What is the load for Enterprise Portal?

• Is the Enterprise Portal going to be accessed by outside users? Does
the company have a current Microsoft SharePoint® Server 2010 farm
that they want to use to host Enterprise Portal?

Does the Company Need an Application Sharing

Technology?

There are several reasons why you should use an application sharing technology.
These include the following:

• Accessing Microsoft Dynamics AX 2012 from a remote location.

• Simplifying administration
• Providing security

If an application sharing technology such as Remote Desktop Services is used,

then this server must be included in the network plan.

What is the Required Database Size?

To size a database for Microsoft Dynamics AX 2012, an administrator should

estimate the initial size of the database, and the size of the transactional records
added each year. The initial size of the database will combine the size of the
database that is associated with the model store, and the master data information.

If there is significant master data, such as millions of customers, then this affects
the initial size of the database.

As Microsoft Dynamics AX 2012 processes transactions, additional records are

added to the system.

Use estimated transaction volume, hardware sizing guidelines, benchmarks, and

experience to estimate future data growth.

For information about how to estimate the size of a database refer to

the Estimate the Size of a Database page.

http://go.microsoft.com/fwlink/?LinkId=286902

01 - 28 Microsoft Official Training Materials for Microsoft Dynamics ®

Your use of this content is subject to your current services agreement
Module 1: Infrastructure and Capacity Planning for Microsoft Dynamics AX 2012
Data storage can be reduced by using database compression. Data compression
reduces data size, and reduces memory consumption. However, it does add to
processor load, and this is available only on the Enterprise Edition.

For more information about Data compression in Microsoft Dynamics

AX 2012, refer to the Tuning data access settings page.

http://go.microsoft.com/fwlink/?LinkId=286903

Microsoft Official Training Materials for Microsoft Dynamics ® 01 - 29

Your use of this content is subject to your current services agreement
SQL Optimization for Microsoft Dynamics® AX 2012

Module Review
In Infrastructure and Capacity Planning for Microsoft Dynamics AX 2012, you
learned about the Microsoft Dynamics AX 2012 system architecture and how each
component is related among the three-tier architecture.

You also learned the types of questions that you can ask to help determine the
appropriate hardware sizing for the infrastructure.

Hardware sizing guidelines and benchmarks are provided to aide in a successful

hardware deployment. Additionally, you learned how to take the information that
is collected and create a plan that applies to real-life scenarios.

01 - 30 Microsoft Official Training Materials for Microsoft Dynamics ®

Your use of this content is subject to your current services agreement
Module 1: Infrastructure and Capacity Planning for Microsoft Dynamics AX 2012
Test Your Knowledge

Test your knowledge with the following questions.

Categorize Activity

Categorize each item into the correct category. Indicate your answer by writing
the category number to the right side of each item.

Categories

1. Data Tier

2. Application Tier

3. Presentation Tier

Items
Enterprise Portal

Reporting Services Database

Analysis Services Database

Client
Model Store

Workflow

Enterprise Portal
Application Object Server

Microsoft Dynamics AX 2012

Database

Help Server

1. List some Questions to ask a company when you perform hardware sizing.

Microsoft Official Training Materials for Microsoft Dynamics ® 01 - 31

Your use of this content is subject to your current services agreement
SQL Optimization for Microsoft Dynamics® AX 2012
2. Should hardware sizing for a company be based only on the basic sizing
guidelines provided in the Hardware Sizing Resources lesson?

( )True

( )False

01 - 32 Microsoft Official Training Materials for Microsoft Dynamics ®

Your use of this content is subject to your current services agreement
 Module 1: Infrastructure and Capacity Planning for Microsoft Dynamics AX 2012

Test Your Knowledge Solutions

Module Review and Takeaways

Categorize Activity

Categorize each item into the correct category. Indicate your answer by writing
the category number to the right side of each item.

Categories

1. Data Tier

2. Application Tier

3. Presentation Tier

Items
3 Enterprise Portal

1 Reporting Services Database

1 Analysis Services Database

3 Client

1 Model Store

2 Workflow

3 Enterprise Portal

2 Application Object Server

1 Microsoft Dynamics AX 2012

Database

2 Help Server

1. List some Questions to ask a company when you perform hardware sizing.

MODEL ANSWER:

2. Should hardware sizing for a company be based only on the basic sizing
guidelines provided in the Hardware Sizing Resources lesson?

( ) True

(√) False

Microsoft Official Training Materials for Microsoft Dynamics ® 01 - 33

Your use of this content is subject to your current services agreement
SQL Optimization for Microsoft Dynamics® AX 2012

01 - 34 Microsoft Official Training Materials for Microsoft Dynamics ®

Your use of this content is subject to your current services agreement