Welcome to MSDN Blogs Sign in | Join | Help

News

  • All posts on this blog are meant for illustration purposes only and not intended for use in production. The following disclaimer applied to all code used in this blog: Copyright (c) Microsoft Corporation. All rights reserved. THIS CODE IS MADE AVAILABLE AS IS, WITHOUT WARRANTY OF ANY KIND. THE ENTIRE RISK OF THE USE OR THE RESULTS FROM THE USE OF THIS CODE REMAINS WITH THE USER. USE AND REDISTRIBUTION OF THIS CODE, WITH OR WITHOUT MODIFICATION, IS HEREBY PERMITTED.
Minor Changes in Database Configuration Checklist for Dynamics AX

We have made minor but important modifications to the Database Configuration settings, which are still posted under March, 2008 archive.  The archived posting includes the most current recommendations.  We've also posted a Microsoft Word version of the checklist below.

  • Changes specific to Microsoft Windows Server 2008 environments:
    • Max Server Memory for a SQL Server instance does not need to be managed with a custom setting, see KB918483 for details. (Configuration Part 1)
    • Partition alignment on SANs does not have to be performed manually on Windows Server 2008.  The default partition offset is 1024K which is suitable in most scenarios. (Configuration Part 2)
  • We have also modified our recommendations to set Auto Update Statistics Asynchronously to FALSE (from TRUE), which is the default setting.  If you modified this setting, please change it back to FALSE.  (Configuration Part 2)

 

Posted: Tuesday, June 23, 2009 4:24 PM by davidre

Attachment(s): DatabaseConfigurationChecklist_V_1_2.docx

Comments

mikaelsorensen said:

Can you give us any information on why the recommendation for "Auto Update Statistics Asynchronously" has changed?

# June 24, 2009 3:11 PM

davidre said:

There is a particular data access pattern in AX that is negatively affected by this setting.  The pattern involves creation of a temporary dataset in a permanent table, a "delta" dataset, which is subsequently referenced in an update statement.  Examples of this pattern include InventUpdateOnHand and GLPost.  If the async setting is true, the "delta" table appears to the optimizer as if it has zero rows; if the async setting is false, it forces a synchronous stats update and the optimizer then bases its decision on correct cardinalities.  

In other cases, any positive effect was negligible.  

This is the reason for the change in our recommendation to set "auto update statistics asynchronously" FALSE.

# June 25, 2009 4:20 PM

Nathan hintz said:

I have seen these issues mentioned above when dealing with InventUpdateOnHand. Glad to hear of these configuration changes, the "Auto Update Statistics Asynchronously" eliminated the issues I've seen.

<br />

<br />

<a href="http://www.perpetualdynamics.com/"> www.perpetualdynamics.com </a>

# August 5, 2009 10:04 PM
Anonymous comments are disabled
Page view tracker