Share
Report
5Hi
we have a custom developed solution for hospitals running on premises and since a few weeks face severe performance issues when using pages accessing the customer table in Dyxnamics BC.
Apparently there might be a solution to this when using partial tables which is working on DBC Version 21 upwards. Till we go to thos version there is some development upgrading work needed. so we would need a intermediate soltion which makes this faster.
When we run a trace with SQL Profiler we see that for the same function, in this case accessing customer data with a custom developed page, for some users the underlying sql query takes rougly 50 secons and for the same page with another user the query takes 3 secs. When analyzing the trace we see that the long running query selects all cusomers and the short running query makes a select with select top(50) which is the reason why its fast.
But the problem is that from within the AL code you cannot determine what SQL statement is to be used. This is handled by DBC internally.
So my question is has anyone seen this behaviour that the performance is so different for different users when using custom developed pages accessing the DBC customer table?
What was yourr workaround or solutrion to that?
Looking forward to your feedback and ideas.
Thanks.
All responses (
Answers (
