web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

AOS and SQL high CPU usage

(0) ShareShare
ReportReport
Posted on by

First off, I'm not sure if this is the correct place to be asking this question.

We're running AX 2012 RTM on Windows Server 2012 R2 and SQL 2008 on Windows Server 2012 R2.

Is there a way I can find out what in AX is running that is causing the CPU for both the AOS and SQL to be insanely high +90%?

I noticed over the weekend the CPU went down a lot lower since Monday was a holiday and nobody was here.

I've narrowed it down to something in AX/AOS because once I shut it off, SQL goes back to normal. If I look at SQLs processes it just shows the SQL server process being the culprit.

Every time I have looked in SQL activity monitor I can't find anywhere it's hanging up or waiting, so that hasn't helped figure out the problem.

Has anyone experienced anything like this and what was your solution? I'm sure getting on R3 would be the most ideal thing to do, but currently we cannot get there.

*This post is locked for comments

I have the same question (0)
  • Mea_ Profile Picture
    60,284 on at

    Hi Conficker,

    I think you can start from SQL profiler msdn.microsoft.com/.../ms181091.aspx to see what queries are executed and Dynamics AX trace parser technet.microsoft.com/.../gg731935.aspx to get overview of all processes in AX

    These 2 tools should help you to find a root cause.

    Also you need to check all batch jobs and their recurrence, maybe you have couple of have each minute.

  • Suggested answer
    Vilmos Kintera Profile Picture
    46,149 on at

    Connect to the SQL Server instance where your AX DB is sitting on with SSMS, New query, select the AX database.

    execute sp_axwho

    That will show you what queries are running at the time you gave the command, with CPU cycle count for the individual processes. You can also check the query plans directly in there and see if you have any which has a timeout.

    I also have posted a script on my blog that you could use to find query plans in the cache that are timing out, and that could be a cause of your problems for high CPU, due to the large number of query processor compilations:

    www.daxrunbase.com/.../improve-ax-performace-by-fixing-bad-query-plans

    To address this problem you need to have an AX developer and/or SQL Server DBA who could assist you with understanding Query plans, capturing SQL profiler and AX tracer and checking them for the cause.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Priya_K Profile Picture

Priya_K 4

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#3
Ali Zaidi Profile Picture

Ali Zaidi 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans