[Vtigercrm-developers] migration of large database...

[Alan Lord]

The migration of databases with more then a million rows in crmentity is 
really painful...

I can "work around" the migration from 5.4.0 to 6.0.0 by pre-populating 
the crmentity label column with anything because there is a test for 
this in the migration script.

However, from 600_to_610.php contains a routine which updates this label 
column irrespectively (headed "//92 starts").

I've been running an update on a fairly fast machine, with a very fast 
SSD, where crmentity has ~2.5million rows and it is taking ages... My 
guess is it will probably take many, many hours...

Please can you optimise this routine a bit better? I suggested one 
method during the testing of these migration scripts that used SQL joins 
which took the time taken down from ~10hours to around 2 minutes!

As it stands I'm going to have to prepare a "special" package to handle 
the migration where I comment out this routine entirely and fix it 
afterwards. It is just too slow to be usable.

Cheers

Al