Translation Dynamics AX R2 BI Series-Considerations for planning analysis

Https://msdn.microsoft.com/en-us/library/gg731898.aspx

There are a lot of things to consider before you start to implement the analysis features of AX. This article describes the things you must consider and the decisions you must make at each step of the planning process.

1. Verifying Prerequisites 2, defining the topology

To help with your AX implementation plan, identify a topology that supports your organization's needs. When defining the topology, consider the following information.

2.1. Performance Considerations

To ensure that the OLTP (Online Transaction Processing) database for Microsoft Dynamics AX works well, we recommend that you install the Analysis service on a dedicated server.

2.2. High Availability

Availability is a capability to provide minimal interruption of service. You can implement analytics services in a highly available environment by using NLB (Network Load balancing), failover Clustering (Failover clustering) technology, and more.

• Network Load Balancing-you can use Network Load Balancing to increase the corresponding time of the query. Network Load Balancing also becomes scaled out to distribute the load to several small servers.
• Failover cluster-a failover cluster, which is a combination of one or more nodes or servers, with multiple shared disks. A SQL Server failover cluster instance that appears on the network as a single computer. However, the instance has failover capability and can be transferred to another node if the current node is unavailable.

2.3. AlwaysOn

SQL Server AlwaysOn is a highly available and disaster recovery solution (disaster Recovery solution), available in SQL Server 2012 and 2014. You can implement the Analysis Services database in an AlwaysOn environment:

• Reduce the load on the main ax OLTP
• Reduced data latency for cube and cube-based report and KPIs (Key performance indicators)

To implement the Analysis Services database in an AlwaysOn environment, complete the following tasks:

1. Create a read-only copy of the AX OLTP database
2. Analyzes the data source of the service database, pointing to the database created in the first step. You can do this:
   1. In SSMs, connect to your analytics service instance
   2. In the tree chart, expand Databases > Data source Nodes
   3. Right-click on the Dynamics database data source and select Properties
   4. In the connection string line, navigate to text initial catalog=[database name]
   5. Change the database name to the database created in the first step

3. Define whether the cube provided by AX will meet your needs

You can use the cube provided by AX, and you can modify it.

4. Identify which configuration key you will use

AX contains the default cube that requires you to enable a specific configuration key. If you disable the configuration key that cube must have, you must complete the following tasks:

1. Run the Profiling Services Project Wizard to remove measurements, dimensions, and KPIs that are not available (because the configuration keys are disabled).
2. Modify or remove a report that requires this configuration key

5. Understand how data partitioning affects cube deployment

AX R2 and R3 isolate data through data partitioning. For example, an organization has multiple subsidiaries. If the organization manager does not want the employees of this subsidiary to access data from another subsidiary, the data partition can provide the necessary boundaries for data isolation.

If you have multiple data partitions installed in AX, you must deploy cube for each partition. For example, suppose you have two data partitions, partition 1, and partition 2. You must deploy cube for each partition. This means that you have a general ledger cube for partition 1, and another separate general Ledger cube for partition 2.

6. Learning Security Model

The security settings for cube are independent of the security settings of Microsoft Dynamics AX. For users to access cube, you must assign users to the database role of the analysis service.

If you are deploying a cube that is included in Ax, when you deploy cube, the default role is created in the database. These roles correspond to the security roles of the ax audience. For example, if you assign a user to the accountant role in Microsoft Dynamics AX, you should assign the same user to the accountant role in the analytics service.

Focus

When assigning user roles in the analysis service, keep the following information in mind: Role members have permission to browse all the data in the cube that the role can access. For example, if you assign a user to the project Supervisor role, that user will have access to all the data in Project Accounting cube. The default roles created in the analysis service are not synchronized with the security roles of the ax public. For example, if you modify the permissions of the accountant role in Microsoft Dynamics AX, the accountant role in the analysis service is not affected.

7. How long do you want to deal with Cube

A cube contains historical, or cached, data. To refresh the data in the cube, you must process the cube. Define how long it takes to process the cube. Considering these, when a cube is processed, it accesses the data in the AX OLTP database. Therefore, processing may affect the performance of the database.

8, clear how you want to display cube data

You can display cube data in a variety of ways, such as in SSRS reports, KPIs, and Excel.

Translation Dynamics AX R2 BI Series-Considerations for planning analysis