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)

Changing table type from Regular to TempDB for customer account statement report will it improve performance? AX 2012 R2

(0) ShareShare
ReportReport
Posted on by 1,813

Hii,

Our AX business users complain a lot that when they run 

Accounts receivable > Common > Customers > All customers. On the Action Pane, on the Collect tab, click Statements.

SSRS Reports\Reports\CustAccountStatementExt

This report takes long time to display and AX client hangs. Sometimes we need to restart AX to recover it. We restart report server but no improvement.

As we know customer statement report is using CustAccountStatementExtTmp table and its type is Regular. I run sql query on this table and it has more than 50 thousand records. 

My question is will it improvement performance if we change table type to TempDB? Is it a right approach and information remains the same?

Or some other way to improve this report performance. Please guide.

 

Thanks,

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Ludwig Reinhard Profile Picture
    Microsoft Employee on at

    Hi Rana Anees,

    Do you always need to run the customer account statement for all of your customers?

    If the users are only interested in the account statement of some of the customers, they could apply filters and/or make use of batch servers for printing faster.

    Best regards,

    Ludwig

  • André Arnaud de Calavon Profile Picture
    304,553 Super User 2026 Season 1 on at

    Hi Rana,

    50000 records is not really much for the SQL server. Changing the table type is not helping you. In this case, the data is prepared to be able to run over multiple sessions.

    It would be better to find out what is really causing the performance issue. Is it a missing index, fragmented index, wrong caching, slow disks, etc?

    To find out about this, you need to do some proper monitoring like using AXperf, Trace parser and SQL performance monitoring.

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 39

#2
Michel ROY Profile Picture

Michel ROY 14

#3
imran ul haq Profile Picture

imran ul haq 8

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans