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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Performance issue with create on-hand counting journals

(0) ShareShare
ReportReport
Posted on by 338

Hi All,

When we are creating on-hand counting journals we observed a lot of performance issues as time increases, please find the path::

Inventory management--->Journals-->Item counting-->counting --> create new(select all dimensions) --->click Lines ---> go to create--->on-hand(selected max no. of lines == 1000 as we require more records).

At starting that is 6 months back for creating on-hand counting journals it used to take 5 mins now it is taking 50mins for the same 1000 records, tried with adding indexes on inventsum and inventdim tables but there is no change.

Did anyone faced the similar issue and can you help me to improve performance as it is impacting more?

Do we have any hot fix for the same issue?

 Thanks in advance.

Regards,

Srikanth

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Vilmos Kintera Profile Picture
    46,149 on at

    Are you doing regular database maintenance (index, statistics update)? Do you have the correct disk layout for your SQL Server? Have you added additional TempDB data files to avoid contention? Did you set up Trace Flags for SQL recommended for Dynamics AX?

    I have mentioned many of those in my Database health blog post, and also have a look at the link there for the Microsoft PFE blog:

    [View:https://www.daxrunbase.com/2016/05/11/ax-database-tuning-and-maintenance/:750:50]

    You might also find relevant hotfixes on the Dynamics LifeCycle Services issue search, did you check there?

    [View:https://lcs.dynamics.com/v2:750:50]

  • Srimdax Profile Picture
    338 on at

    Thanks for the reply.

    The above mentioned all are installed in our server and our team said that MS doesn't recommend additional TempDB data files to avoid contention.

    Could you let us know which we can figure it out from application end?

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

    In most of the cases when people say we have done all of the above, at least half of the steps are missing of our performance recommendations, based on past experience, so allow me to be doubtful here. About TempDB data files your team is simply wrong, just check the documentation and industry experts. Since AX is heavily reliant on using TempDB for temporary tables, I already have identified a bottleneck in your system without having a look.

    [View:https://technet.microsoft.com/en-us/library/dd309734.aspx:750:50]

    [View:https://technet.microsoft.com/en-us/library/ms175527(v=sql.105).aspx:750:50]

    From application end you would have to capture a server- and client-side trace, and then analyse it with the AX Tracer Parser to identify what is the root cause. It could be a number of issues, in majority of the cases it is related to slow SQL statements (missing covering index, DB maintenance problems, incorrect execution plan), high number of tier boundary calls (client to server), or large number of recursive calls. Not cached, or high number of display methods on grids could also be bad.

    So the recommended steps: go through all of the above recommended typical configuration and maintenance problems, identify any bottlenecks outside of AX (TempDB contention, Disk I/O, CPU, internal and external SQL memory pressure, Trace Flags, Index/Statistics update) and if all of them are correct and you still face the issue, then collect a trace, check it, and keep us posted on your findings.

  • Community Member Profile Picture
    on at

    There are some conditions where you can face performance issue:

    1: No Indexing at table level

    2: At the time of transaction other users are also doing transaction with same item/s

    3: DB Sync issue

    As per my experience if you will do re-indexing then this issue will resolve your problem.

    For this time just used Inventtrans also for keep activity safe side.

  • Community Member Profile Picture
    on at

    Hi Vinodax,

    We have similar problem when creating on-hand counting journals for some locations. Sometimes it takes 30min+ for some of our locations, even tho location only contains 5-10 lines of raw materials. What I noticed, when it generates the journal - loading screen stops on one or two part numbers that not even in that location you stated prior creating the journal, so if you try to exclude the part number prior generating the journal - it generates on-hand counting journal within minute or two. However I don't know what's the route cause for it.

    Regards,

    V

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
CP04-islander Profile Picture

CP04-islander 16

#2
GiacomoRovai Profile Picture

GiacomoRovai 4

#3
Douglas Noel Profile Picture

Douglas Noel 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans