My Oracle Support Banner

MySQL Server Variable: innodb_file_per_table (Doc ID 1320634.1)

Last updated on MARCH 12, 2021

Applies to:

MySQL Server - Version 4.1 and later
Information in this document applies to any platform.

Purpose

Understand the advantages and disadvantages of using innodb_file_per_table, why it was not the default but now is since 5.6 and some of the known limitations and problems.

Scope

Detailed general guidance for DBAs already familiar with the option seeking guidance on how to use it and what problems it can be involved with.

Details

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Scope
Details
 Why use innodb_file_per_table?
 Why not use innodb_file_per_table?
 General tablespaces
 Checking to see if a table is using per-table tablespaces
 Why is the default not to use innodb_file_per_table?
 Related options
 Known problems with innodb_file_per_table in old versions
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.