Microsoft Dynamics AX (Archived)

Very Slow Statement calculation

(0) Share

Report

Posted on by Community Member

if a statement is calculated manually it's very slow and in batch, i get a deadlock error as below.

I have deleted "inventsumlogtts" but still no improvement and nobody is using this table but still deadlock error

Anybody faced such issue.

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

vijaysharma 2 on at

Like (0)

Report

HI,

what about the event viewer log? it seem that some problem in table indexing .

Was this reply helpful? Yes No
Suggested answer

Mea_ 60,284 on at

Like (0)

Report

Hi Phani Buddha,

You have multiple batch thread that lock same table and cause deadlocks. I would recommend you to go to Retail parameters -> posting -> batch processing and remove "process requests in parallel" check box or change "Maximum sales orders per task" value as a workaround. Also you need to open a case with MS, so they can fix this if it is not caused by your customization.

Was this reply helpful? Yes No
Balaji TK on at

Like (0)

Report

This Occurred After Any Cumulative Updates or GST Updates?

Was this reply helpful? Yes No
Suggested answer

Vilmos Kintera 46,149 on at

Like (0)

Report

Make sure you have the recommended SQL Server Trace Flags enabled for Dynamics AX. There is one which helps with lock escalation, and might clean up the deadlocks in combination with Ievgen's recommendation for retail batch parallelism.

Was this reply helpful? Yes No
Suggested answer

guk1964 10,888 on at

Like (0)

Report

if you have mass deleted then check your transaction log size.

There are many other tables also that can probably be cleaned up.

Run SQL stats.

There are far too many other tuning suggestions above, and in other posts to cover here and there are many posts already.

There is not enough information to pin point a specific problem e.g. how many POS are involved? Is this run daily? what maintenance is done on the store databases?

The configuration key Sales tax (ledgerbasicSalesTax) may be turned off in the system if you are not using tax. When running for example the retail statement posting, the performance may then be very poor. The slow response is originated in every call to TaxParameters::find(). When analyzing the sql server queries you will see a large number of Temporary table are generated.

If that is the case then turn it on again and set sales tax to use a tax percentage of 0,00%.

Was this reply helpful? Yes No
Mahmoud Hakim 17,887 on at

Like (0)

Report

also to enhance your performance , you need to run periodic jobs for maintance plan like rebuild and reorganize indexes ,and update statsitics ...etc

Was this reply helpful? Yes No