Re: [Axapta-Knowledge-Village] Create index with first column not dataareaid

2009-03-04 Thread Agus Riyadi
Thanks Varden / James, I will have a look more whats wrong in this instance, since usually recalc complete in 3 hours. Thanks and best regards, Agus On Thu, Mar 5, 2009 at 11:41 AM, Varden Morris wrote: >Wow. It's a bit difficult to trace this way on the live system since > the code could

Re: [Axapta-Knowledge-Village] Create index with first column not dataareaid

2009-03-04 Thread Varden Morris
Wow. It's a bit difficult to trace this way on the live system since the code could be anywhere in the app. It's possible that a query is not using the fields in the order of the index and since the kernel automatically adds the DataAreaId to the WHERE clause you do not need to specify it in cod

RE: [Axapta-Knowledge-Village] Create index with first column not dataareaid

2009-03-04 Thread James Flavell
Okay I see For closing the main tables as you probbaly know would be inventtrans, inventsettlement and inventsum and maybe inventdim and inventtable (but those are probably read only requirement) Do let us know your findings as would be interested to know what can help improve closing performan

Re: [Axapta-Knowledge-Village] Create index with first column not dataareaid

2009-03-04 Thread Agus Riyadi
Thanks James, Yes perhaps this is not relevant to recalc/closing because there are users activity during recalc which might get captured in the profiler too, and profiler will not tell from which ax function this particular query comes from. I am just curious since DTA suggested several more index

RE: [Axapta-Knowledge-Village] Create index with first column not dataareaid

2009-03-04 Thread James Flavell
I would double check why is recalc/closing looking at custpackingslipjour. As far as I am aware the std closing should not look at this table table so I would be a little careful...although I guess you can add the index and see but to me I would not expect any improvement in the recalc or closing

Re: [Axapta-Knowledge-Village] Create index with first column not dataareaid

2009-03-04 Thread Agus Riyadi
Hi Varden, Thanks for input. This comes from the profiler file during inventory recalculation process, so less likely that I will change the standard code. I will only add index from the DTA's recommendation. I think we need to concern the column order as suggested by DTA because otherwise the ind

Re: [Axapta-Knowledge-Village] Create index with first column not dataareaid

2009-03-04 Thread Varden Morris
You are right about the DataAreaId being added to the index by the kernel. I am not sure that you need to concern yourself about the order of the fields as suggested in the backend but you need to ensure that any query coming from AX should have the fields listed in the WHERE clause in the order