CiviCRM Community Forums (archive)

Wow. CiviCRM 3.2.1 (from 2.2.9) has been upgrading for the last hour. Almost all of that time has been queries of this form -

UPDATE civicrm_activity_target cat, civicrm_activity ca
                    SET cat.activity_id = 542639  
                WHERE ca.source_record_id IS NOT NULL   AND
                      ca.activity_type_id = 32          AND
                      ca.id <> 542639              AND
                      ca.source_record_id = 1020 AND
                      ca.id = cat.activity_id

DELETE ca.*
                FROM civicrm_activity ca
                WHERE ca.source_record_id IS NOT NULL  AND
                      ca.activity_type_id = 32         AND
                      ca.id <> 542639             AND
                      ca.source_record_id = 1020

It actually seems to be the DELETE which is slow.

civicrm_activity has only 1.3million rows, 2.5GHz core2, 2GB RAM on the VM. From ca.id there I'd guesstimate up to another hour to go.