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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Year end closing takin...
Finance | Project Operations, Human Resources, ...
Suggested Answer

Year end closing taking long time in ax 2009

(0) ShareShare
ReportReport
Posted on by Ashutosh Kumar 55

Hi,

Year end closing taking long time in ax 2009, It is running since last 88 hours.

Can any one suggest, how to speed up?

Can anyone replaced "insert" to "insert_recordset"  in LedgerTransferOpening class, which used in year-end closing process or any other solution.

Thanks,

I have the same question (0)
  • Suggested answer
    André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 301,119 Super User 2025 Season 2 on at

    Hi Ashutosh,

    I have written a blog about rebuild or recalculation of balances. This blog was written for AX 2012 and talks about some performance issues and mitigations: Rebuild balances in AX 2012 (dynamicspedia.com)

    Note that the way how to recalculate the balances after deleting previously created opening transactions is different between AX2009 and AX2012. It might be that some logic in AX2009 was causing more delays. I can remember I did a customization in the past to limit the recalculations to one year or one period only, but that was on an AX4 environment. I think also in AX2009 it will recalculate all balances and not only for one fiscal year.

    I don't have a running AX2009 environment to check the logic and give a direct full recommendation. I do hope the blog and my comments above will give some starting points to investigate for similar issues and probably change some logic to improve the performance by e.g. change the recalculation to calculate for only one year.

  • Acer Profile Picture
    Acer 75 on at

    We had the same issue and fixed it.

    Make sure you dont have the "optimize for unknown" flag set on the SQL Server (4136).

    This will surely park you AX and make everything run slow.

    Often it has been implemented to fix parameter sniffing, but it is way better to identify the few places you find these issues and fix it by changing that code, index turning or simply add a plan guide (we have about 15 plan guides on our database and are not seeing these issues anymore).

    If you don't have the 4136 flag set  (check by running  DBCC TraceStatus()  on the database )

    Our result on a well functioning, fully upgraded AX2009 with SQL Server 2012 SP4

    1117

    1118

    1224

    2371

    4199

    7646

    All enabled globally

    Then you may have to look at the numbers of threads it can start up.

    But first. Let me know what flags you have enabled.

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 451 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 428 Super User 2025 Season 2

#3
BillurSamdancioglu Profile Picture

BillurSamdancioglu 239 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans