How to use Microsoft Dynamics AX 2012 Trace Parser

How to use Microsoft Dynamics AX 2012 Trace Parser

Song Nghia - Technical Consultant

Noted: You need install trace passer tool when setup or resetup AX 2012

Microsoft Dynamics AX 2012 Trace Parser is a wonderful tool which can help you in identifying fairly good amount of performance problems within your installations. 
So what is Microsoft Dynamics AX 2012 Trace Parser??

Trace Parser provides user interfaces to import, process and render ETW tracing events that produced by Microsoft Dynamics AX. User can then analyze tracing events to identify performance bottlenecks such as long-running X++ methods, slow SQL queries and frequently called RPCs. Features in Trace Parser help users determine the root causes of performance problems.


So how do we install and setup trace parser

Bit of things which we need to note when we do this install

Microsoft Dynamics AX 2012 setup program provides Trace parser as an install. Note that Trace Parser requires .Net Business Connector. In order to run Trace Parser, you also

need access to a SQL Server 2008 instance (Enterprise or Developer edition) with admin permission. Using a local SQL server instance is recommended. You don’t need to use the same SQL instance where the AX DB is installed.

It is quite boring to explain the installation process of any utility so try it yourself and let us know if you have any issues.

So how does it work???

It can be used for collecting and analyzing traces as below.

Start Microsoft Dynamics AX 2012 client and switch to Development Workspace. Open the Tracing cockpit (in the Tools menu) form:

To collect trace:

Click “Start trace”, specify a trace file name. Event tracing is now enabled in AX.
“Replay” the scenario that you are investigating in AX client. Once done, click the “Stop trace” button in Tracing Cockpit a trace file is now created.
You may now click the “Open trace” button to launch a new Trace Parser instance and imports the trace automatically
Please keep in mind when you do a Trace collection:

Keep the trace scenarios as short as possible to ensure that traces are much appropriate.
Open trace tool and import file within senario.

You can import the trace parser results what you had collected from your client as below

result when you see sql and table.

You can excute sql to check why select or query table takes a long time


Previous Post
Next Post

post written by: