Hello.
I'm a DBA and i'm currently doing an upgrade from version 1.8 to 2.0 to 2.2 with the zabbix administrator.
Our DB is not fairly large: 250 GB and is partitionned.
It's a mysql database and i've notice some strange things about the upgrade.
I wonder why in the upgrade script you first drop an index on the table events and just after you create te SAME index. And after that, you alter the table events. Each step for us takes about 2.5 hours.
What's the matter ? The ALTER TABLE already rebuild the index.
And it's the same thing with the upgrade from 2.0 to 2.2 (and the modifications to the database aren't available anymore in a sql file)
So why proceed like that ?
If i could suggest some changes, is to not doing theses drop / create again.
DBA can handle the index by doing an optimize.
Regards
I'm a DBA and i'm currently doing an upgrade from version 1.8 to 2.0 to 2.2 with the zabbix administrator.
Our DB is not fairly large: 250 GB and is partitionned.
It's a mysql database and i've notice some strange things about the upgrade.
I wonder why in the upgrade script you first drop an index on the table events and just after you create te SAME index. And after that, you alter the table events. Each step for us takes about 2.5 hours.
What's the matter ? The ALTER TABLE already rebuild the index.
And it's the same thing with the upgrade from 2.0 to 2.2 (and the modifications to the database aren't available anymore in a sql file)
So why proceed like that ?
If i could suggest some changes, is to not doing theses drop / create again.
DBA can handle the index by doing an optimize.
Regards