With DynamicsPerf 2.0 , we made schema changes to better support multiple databases and environments. This change includes AOTEXPORT class that provides table and index schema from Dynamics AX into the DynamicsPerf database.
The new AOTEXPORT class now writes data directly to DynamicsPerf. What this allows you to do that you really couldn’t do before is to compare multiple environments. This is one of those things that always comes up when there is a performance issue. Is production the same as QA or Dev? By installing the AOTEXPORT class into each environment and exporting data to the same DynamicsPerf, you can now compare that data. This is limited to AX Table properties and AX Index properties. So this is not a complete code compare or configuration compare between the two environments.
For those customers that have multiple AX deployments, say for multiple subsidiaries or regions, this will be a great way to ensure that basic schema is consistent across those deployments. When you have separate Models/Projects for each sub, it’s not always easy to ensure that common schema customizations are always deployed in each environment. Even with a single model deployed to each configuration, it’s still possible for customizations to cause variances between them.
These new sample scripts will be part of the next build of DynamicsPerf 2.0 called beta 1b.zip. You have download the previous beta, there is a fix script to update your DynamicsPerf schema. You can just unzip the new download over top of your previous install and run the Beta 1 Fix SQL script. The new sample queries are part of 3-Analyze AX configuration.sql script.
Try out this new capability and let us know how it helped you in the DynamicsPerf 2.0 Feedback blog post.
Rod “Hotrod” Hansen