GDPR - Your personal data is important

We value your personal data and ensure you that we will continue to secure the storage of the information you share with us regarding your use of this forum (email address, IP address, location, etc.) and only use them upon consent, and towards the purpose it’s intended for. Email us at to request the update or deletion of your data.

If you wish to make sure you get all our latest tutorials, customer success stories, product updates and many great news, subscribe now to our monthly newsletter.


Nous accordons beaucoup d’importance au traitement de vos données personnelles. Soyez assurés que les informations collectées dans le cadre de votre utilisation de ce forum (adresse email, IP de connexion, localisation, etc.) sont stockées de manière sécurisée et qu’elles ne sont utilisées que dans le cadre pour lequel elles sont été collectées. Pour toute demande de modification ou suppression de vos informations, écrivez-nous à

Si vous souhaitez recevoir tous nos tutoriels, retours d’expériences, nouveautés produit et bien d’autres actualités, (ré)abonnez-vous sans attendre à notre newsletter mensuelle !
See more
See less

Centreon 2.6.2 - Converting tables to InnoDB

  • Filter
  • Time
  • Show
Clear All
new posts

  • Centreon 2.6.2 - Converting tables to InnoDB

    Hello everybody,

    in an effort to make our database replication more reliable and increase overall database performance i thought about converting the database to all-InnoDB and i was wondering if any of you knew if that could cause any issues. Now i know 2.7 is running on pure InnoDB and i know that in theory converting shouldn't be to much of a problem (i've tested it in our pre-prod environment, but i wanted to ask you guys before i put it on prod) but i was wondering if there were any drawbacks to using InnoDB for tables like data_bin and so on or if you know any issues in that regard.

    Thanks already.