I have been using Mergetool for many years. Don't really remember how many, but it was back to when it was included on the Navision tools cd.
Speed has never really been an issue, as long as it was in a native database. But the last year or so, even with a SQL Server database performance has been great.
Now I have installed the latest version MGT1.30.39 running on NAV 2013.
Importing goes fine, no complaints about performance here.
But when trying to use the compare function on reports then Mergetool almost stops. Right now it has been running compare of report 35 (NAV 2009/NAV 2013) for over 3 hours!
Unless I find out what's going on, then I have to stop using this version of Mergetool and downgrade to the NAV 2009. There is no information about this on the mergetool.com homepage.
Why don't you just send Per an email?
I wrote it here first, not only because I believed that I wasn't the only one using Mergetool on NAV 2013, but also because I typically tells people who emails me general Dynamics questions to ask them in the forums. This way the answers can benefit the whole community, not just them. So next time the answer is already there.
But I did hope that Per would see the question and answer it here, when he got the time.
In the meantime, since I posted this yesterday, only 34% of the compare of a standard NAV 2009 against a NAV 2013 has been completed. Still working on the reports.
The problem is that the RDL code in the report is 10 times more code than the regular report. Between 2009 and 2013 is the RDL code basically completely redone. The 2013 is completely redoing the other part of the code too based on the removal of the classic layout. There is not much to do about that, moving code changes automatically for reports that are not ProcessingOnly is close to impossible.
You can find more information on the page belowhttp://mergetool.com/addin_e/faq/FAQ_MGTCOMPAREREPORTS_WEB.htm
Or generally for the FAQ's to the Mergetoolhttp://mergetool.com/addin_e/faq/mergetool.htm
Thank you Per, I knew there was a good explanation, and it was not because there was something wrong with my PC or Mergetool!
So best practice when comparing NAV 2009 (or older) to NAV 2013 is do not to compare reports?
But you're saying is also that it doesn't really matter which merge/compare-tool you are using, then we would get the same issues, as it's really due to the fact that NAV 2009 and NAV 2013 are natively different?
UPDATE: After setting the <>REPORTS filter, then the rest of the compare completed in less than 10 minutes!
And I'm happy again!