Dynamics AX Data Upgrade Source Environment Tasks introduction
The High level Steps Performed at Source System are as follow:
Preparing the source database:
This section lists the steps to prepare the source environment database.
Consider implementing trace flag 4199. This flag enables a number of SQL Server performance enhancements that are applicable to Microsoft Dynamics AX. These enhancements should improve the performance of the upgrade readiness and live preprocessing steps of the upgrade. For details about trace flag 4199, review the following KB article: http://support.microsoft.com/kb/974006
Note that trace flag 4199 is available in the following SQL Server builds:
SQL Server 2005 Service Pack 3 Cumulative Update 6
SQL Server 2008 Cumulative Update 7
SQL Server 2008 Service Pack 1 Cumulative Update 7
SQL Server 2008 R2
Consider increasing the frequency of transaction log backups. Also consider increasing the size of the transaction log to support the additional log space required for live preprocessing and live delta processing.
Before the Delta and Single User upgrade steps, increase the max degree of parallelism setting for the server. As a general rule, increase the value to the number of processor cores per processor. For example, on a four-processor server with a total of 24 cores, set max degree of parallelism to 6, as follows.
sp_configure 'max degree of parallelism',6
reconfigure
After the Delta and Single User upgrade steps, return max degree of parallelism to its recommended setting of 1.
sp_configure 'max degree of parallelism',1
reconfigure
Note: Max degree of parallelism is a dynamic setting that does not require a restart of the SQL Server instance to take effect.
During all test runs, use the SQL Server DMVs or Performance Analyzer for Microsoft Dynamics to identify areas where index tuning or code changes are needed. Use the information from those tools to watch for long-running queries, missing indexes, or other index recommendations. Many times, performance can be improved by making changes to the index structure, which only needs to remain modified during the upgrade processing, and can be removed or reset to its original state after the processing is completed.
The following recommendations are based on the assumption that they are applied on a dedicated upgrade AOS instance:
Increase the Maximum buffer size value to 120. This allows Microsoft Dynamics AX to retrieve a much larger set of data with every round trip to the database. Changing this setting enhances the performance of a typical upgrade script, because most upgrade scripts include while select statements that run through entire tables.
This setting particularly benefits the row-by-row operations during the upgrade readiness check and live preprocessing.
Note: If you change the Maximum buffer size setting, you must restart the AOS instance before the change takes effect.
Batch processing changed between Microsoft Dynamics AX 4.0 and Microsoft Dynamics AX 2009. In Microsoft Dynamics AX 4.0, concurrent batch processing is enabled by launching multiple batch clients to process the DataUpgrade batch group. The number of batch clients that can be used varies, depending on the number of cores and processors on the server, and the availability of client resources to run the batch group.
In Microsoft Dynamics AX 2009, the Batch Framework changed to allow AOS to process batch jobs rather than relying on individual batch clients. The number of threads allocated to batch processing can be changed in the Server configuration window found under Administration > Setup inside the Microsoft Dynamics AX client. The number of threads can generally be set to twice the number of cores. For example, with 8 cores, set number of batch threads to 16. However, the performance of AOS and SQL Server should be monitored in order to watch for CPU or I/O bottlenecks, and the number of batch threads should be adjusted accordingly.
Before the Delta and Single User upgrade steps, in the Server Configuration utility, in the Configuration command to run at kernel startup field, add the following command:
-internal=comments –internal=nocursorreuse
Notes:
A change to the AOS kernel startup command requires a restart of the AOS instance to take effect.
The original purpose of the –internal=comments command was to aid debugging by embedding parameter replacement values in the SQL statement string as comments. A side effect of the comments in the SQL text is that they induce a recompile when each SQL statement is executed. Using this command thereby prevents performance issues caused by parameter sniffing.
This section lists the steps to prepare the source environment database.
Consider implementing trace flag 4199. This flag enables a number of SQL Server performance enhancements that are applicable to Microsoft Dynamics AX. These enhancements should improve the performance of the upgrade readiness and live preprocessing steps of the upgrade. For details about trace flag 4199, review the following KB article: http://support.microsoft.com/kb/974006
Note that trace flag 4199 is available in the following SQL Server builds:
SQL Server 2005 Service Pack 3 Cumulative Update 6
SQL Server 2008 Cumulative Update 7
SQL Server 2008 Service Pack 1 Cumulative Update 7
SQL Server 2008 R2
Consider increasing the frequency of transaction log backups. Also consider increasing the size of the transaction log to support the additional log space required for live preprocessing and live delta processing.
Before the Delta and Single User upgrade steps, increase the max degree of parallelism setting for the server. As a general rule, increase the value to the number of processor cores per processor. For example, on a four-processor server with a total of 24 cores, set max degree of parallelism to 6, as follows.
sp_configure 'max degree of parallelism',6
reconfigure
After the Delta and Single User upgrade steps, return max degree of parallelism to its recommended setting of 1.
sp_configure 'max degree of parallelism',1
reconfigure
Note: Max degree of parallelism is a dynamic setting that does not require a restart of the SQL Server instance to take effect.
During all test runs, use the SQL Server DMVs or Performance Analyzer for Microsoft Dynamics to identify areas where index tuning or code changes are needed. Use the information from those tools to watch for long-running queries, missing indexes, or other index recommendations. Many times, performance can be improved by making changes to the index structure, which only needs to remain modified during the upgrade processing, and can be removed or reset to its original state after the processing is completed.
The following recommendations are based on the assumption that they are applied on a dedicated upgrade AOS instance:
Increase the Maximum buffer size value to 120. This allows Microsoft Dynamics AX to retrieve a much larger set of data with every round trip to the database. Changing this setting enhances the performance of a typical upgrade script, because most upgrade scripts include while select statements that run through entire tables.
This setting particularly benefits the row-by-row operations during the upgrade readiness check and live preprocessing.
Note: If you change the Maximum buffer size setting, you must restart the AOS instance before the change takes effect.
Batch processing changed between Microsoft Dynamics AX 4.0 and Microsoft Dynamics AX 2009. In Microsoft Dynamics AX 4.0, concurrent batch processing is enabled by launching multiple batch clients to process the DataUpgrade batch group. The number of batch clients that can be used varies, depending on the number of cores and processors on the server, and the availability of client resources to run the batch group.
In Microsoft Dynamics AX 2009, the Batch Framework changed to allow AOS to process batch jobs rather than relying on individual batch clients. The number of threads allocated to batch processing can be changed in the Server configuration window found under Administration > Setup inside the Microsoft Dynamics AX client. The number of threads can generally be set to twice the number of cores. For example, with 8 cores, set number of batch threads to 16. However, the performance of AOS and SQL Server should be monitored in order to watch for CPU or I/O bottlenecks, and the number of batch threads should be adjusted accordingly.
Before the Delta and Single User upgrade steps, in the Server Configuration utility, in the Configuration command to run at kernel startup field, add the following command:
-internal=comments –internal=nocursorreuse
Notes:
A change to the AOS kernel startup command requires a restart of the AOS instance to take effect.
The original purpose of the –internal=comments command was to aid debugging by embedding parameter replacement values in the SQL statement string as comments. A side effect of the comments in the SQL text is that they induce a recompile when each SQL statement is executed. Using this command thereby prevents performance issues caused by parameter sniffing.
Comments
Post a Comment