Skip to content

Commit 18b7240

Browse files
committed
tablespace limitation
1 parent 80fd852 commit 18b7240

File tree

2 files changed

+6
-1
lines changed

2 files changed

+6
-1
lines changed

articles/mariadb/concepts-limits.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -146,6 +146,12 @@ Review the [MariaDB documentation](https://mariadb.com/kb/en/server-system-varia
146146

147147
The time zone tables can be populated by calling the `mysql.az_load_timezone` stored procedure from a tool like the MySQL command line or MySQL Workbench. Refer to the [Azure portal](howto-server-parameters.md#working-with-the-time-zone-parameter) or [Azure CLI](howto-configure-server-parameters-cli.md#working-with-the-time-zone-parameter) articles for how to call the stored procedure and set the global or session-level time zones.
148148

149+
### innodb_file_per_table
150+
151+
MariaDB stores the InnoDB table in difference tablespace based on the configuration you provided during the table creation. The [system tablespace](https://mariadb.com/kb/en/innodb-system-tablespaces/) is the storage area for the InnoDB data dictionary. A [file-per-table tablespace](https://mariadb.com/kb/en/innodb-file-per-table-tablespaces/) contains data and indexes for a single InnoDB table, and is stored on the file system in its own data file. This behavior is controlled by the innodb_file_per_table variable. Set `innodb_file_per_table = OFF` causes InnoDB to create tables in the system tablespace, otherwise InnoDB creates tables in file-per-table tablespaces.
152+
153+
The Azure Database for MariaDB supports the biggest **1TB** in a single data file. If your database size is bigger than 1TB, you should create the table in [innodb_file_per_table](https://mariadb.com/kb/en/innodb-system-variables/#innodb_file_per_table) tablespace. If you have a single table size larger than 1TB, you should use the partition table.
154+
149155
## Storage engine support
150156

151157
### Supported

articles/mysql/concepts-limits.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -155,7 +155,6 @@ MySQL stores the InnoDB table in difference tablespace based on the configuratio
155155

156156
The Azure Database for MySQL supports the biggest **1TB** in a single data file. If your database size is bigger than 1TB, you should create the table in [innodb_file_per_table](https://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_file_per_table) tablespace. If you have a single table size larger than 1TB, you should use the partition table.
157157

158-
159158
## Storage engine support
160159

161160
### Supported

0 commit comments

Comments
 (0)