New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure MySQL to create an innodb file per table to prevent ibdata1 growing indefinitely #388

Closed
GoogleCodeExporter opened this Issue Mar 24, 2015 · 1 comment

Comments

Projects
None yet
1 participant
@GoogleCodeExporter
http://stackoverflow.com/questions/3456159/how-to-shrink-purge-ibdata1-file-in-m
ysql

"But you can configure MySQL so that each table, including its indexes, is 
stored as a separate file. In that way ibdata1 will not grow as large. 
According to Bill Karwin's comment this is enabled by default as of version 5.6 
of MySQL.

It was a while ago I did this. However, to setup your server to use separate 
files for each table you need to change my.cnf in order to enable this:"

[mysqld]
innodb_file_per_table

Original issue reported on code.google.com by doug.bu...@gmail.com on 5 Sep 2013 at 6:31

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 24, 2015

Published:
http://blog.securityonion.net/2014/02/new-securityonion-setup-package.html

Original comment by doug.bu...@gmail.com on 11 Feb 2014 at 2:16

  • Changed state: Verified
  • Added labels: ****
  • Removed labels: ****
Published:
http://blog.securityonion.net/2014/02/new-securityonion-setup-package.html

Original comment by doug.bu...@gmail.com on 11 Feb 2014 at 2:16

  • Changed state: Verified
  • Added labels: ****
  • Removed labels: ****
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment