• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

InnoDB default setting enable file_per_table by default

Rob_108

New Pleskian
Seems to me that this setting should be default with the option for those with specialized considerations to turn it off. My Plesk installation is on CentOS (6) by GoDaddy and there is no way to turn it off when one starts up a new server as Plesk itself is using the database. I am very afraid of exporting, flushing and otherwise changing this database to enable this option manually as I have (just) experienced how this can break the entire installation.

When this option is enabled, one can easily move databases by simply copying the .frm, .MYI and .MYD files to whatever location. This is especially good when the server unexpectedly crashes and you use this opportunity to upgrade the OS or something. It also allows one to shrink this ever expanding db file and index files associated with it. Without enabling this option one cannot shrink these files and they grow ever larger.

Please consider this! It would be really great if there were an option in Plesk itself to choose this.

Thank you for your consideration.
 
Back
Top