AX2009->AX2012 R2 upgrade performance

Question Status

Pirmin Bercher asked a question on 14 Sep 2013 4:16 AM

Hi we are right in the middel on testing / planing an upgrad from AX 3.0 (yes) via 2009 to 2012 R2..

Most of the Jobs in the AX 2012 data upgrade Center run fine and relativly fast .. except  thos:

Split billing lines updateCostSalesLineFunders Proj 3198.35 min

Update PSAProjProposalProj table updatePSAProjProposalProjMajor Proj 4000 min

Did any one else have performace probs with both or one of them?

When looing at AOS and SQL both seem to be  bored .. AOS somewhto 5-10% CPU, still mem free. DB Server 3 % CPU. mem ok, haveing about 1300 Batch requests per second. Not seeing any lock or heavy disk traffice..

any ideas welcome


André Arnaud de Calavon responded on 15 Sep 2013 1:06 PM

Hi Pirmin,

I have not seen an upgrade with Projects. Until now only (re)new implementations. The reason why I anwer on this topic is that I have seen a strange performance issue due to some checks in the project postings when you have multiple funding sources per project.

You issue sound like this same experience I had before.

You can check if the upgrade results in  lager number of funding sources in stead of one or some. I don't know your current setup. In many scenario's there will be just one funding source.

Chris Dando responded on 20 Sep 2013 3:16 AM

Hi Pirmin,

Did you make any progress with this issue?

We are having the same problem with the updatePSAProjProposalProjMajor job taking many days to complete.

I am considering splitting the job into multiple batch tasks each processing a subset of the ProjProposalJour records (and then run the jobs in parallel). Do you have any thoughts on this approach?

Thanks, Chris

Pirmin Bercher responded on 20 Sep 2013 3:43 AM

Hi Chris,

sorry to say.. nope .. is still converting !  (since Sep. 10th) ..

I don't dare so far to cancel the Job, as it is still creating some new records.  When i look at AOS Server, it seems to do something ( ~ 7 % cpu) the DB Server is more than bored (no siginficant  CPU, not Storage Action)  just ~ 1500 Batch requests per sec.

We just started a perdormanc Analysis.. (with our developers)

maybe paralell could be a solution as it not seems to use many ressources .

Any other ideas?


Chris Dando responded on 20 Sep 2013 4:28 AM

10 days!

I laughed at that, but actually it's not funny when you consider the system is unavailable to users when this job runs

We've only started to think of a solution but if we have any success I'll let you know (I think the problem lies with the row-by-row processing which uses the ProjTrans wrapper classes)

It's comforting to know we're not the only ones with this problem!

Cheers, Chris

Pirmin Bercher responded on 20 Sep 2013 5:32 AM

thanx.. well we have data of 13 (!!!!) years to Transfer!

And currently the Job has created ~1.2 mio (!!) records in PSAProjProposal...

good luck


Nick Hulbert responded on 8 Oct 2013 4:35 AM

Just wondering if anyone has worked out how to speed this up?  I stopped the upgrade process after waiting 2 days for this to finish.

Even then PSAProjProposalProj table had no records inserted.

I'm upgrading from RTM to R2 btw - not from 2009. 

Pirmin Bercher responded on 8 Oct 2013 4:39 AM


well this one is still converting (since Sep 10th) .. i let it run just ..

We did split up for the next test in multiple batchjobs.. will run it tonight ..

Toni Feldinger responded on 1 Jan 2014 12:24 PM

Hi Pirmin,

we are upgrading from AX4 to AX2012R2 CU7.

Batch job "updateCostSalesLineFunders" is running for days and we do not have a clue why...

Would like to check back with you if there are any news you can share!



Steven Harvey responded on 29 Apr 2015 11:10 AM

Hi Pirmin

Did you ever find a solution to this long running job ? I know there is a hot fix from Microsoft for this, however i'm finding it still runs for a long time.

How did you get past this?

Pirmin Bercher responded on 29 Apr 2015 1:54 PM


as mentioned above we did split the whole job und thousands ( yes) of single jobs. And did run them on parallel.. then it took a day or so .. and the server was nearly on fire ;)