hi , I have exp in working with a Navision client having G/L Entries more than 25,000,000 and as we were using a max of 8 dimensions then the Ledger entry records were around 90,000,000.
The ldeger Entry records depends on the dimsnions used while posting. So if ur G/L Entry has x number of records and u are having y dimensions , then your ledger entry diension table will have <= x*y records
So its pretty normal.
And i don't think that Adjust Cost Batch job depends on the Ledger Entry Dimension table size. It depends on ILE, VLE, and item appl. entry mostly.
We had more than 36000 item records and ILE size of almost 4,000,000. we used to run batch job daily and it hardly took more than 30 mins.
so even we had run that once a week, it wud have taken at max 2.5 hrs.
I'll suggest you one small thing that even we did to optimize our batch job.
previously batch job was running for all 36000 items and finding entries in ILE for those items. so in place of this we made created a flag in item table. and whenever an ILE entry is passed for that item in the day, that flag was set to true .
and at night when batch job runs, it should consider only those items which has flag set as true( as its waste of time on iteratnig wid items which hav not been used in thwe day). and set the flag false after batch job completes.
Hope this should be enough hint for u to go ahead with optmizing it like magic.
thanks and regards
Anurag atish
technical consultant
Bangalore