--- title: "Advanced parameters for Public Cloud Databases for MySQL" description: "This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for MySQL according to your use cases" url: https://docs.ovhcloud.com/de/guides/public-cloud/databases/mysql-advanced-parameters-references lang: de lastUpdated: 2025-06-19 --- # Advanced parameters for Public Cloud Databases for MySQL ## Objective This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for MySQL according to your use cases. ## Requirements - A [Public Cloud project](https://www.ovhcloud.com/de/public-cloud/) in your OVHcloud account. - A database running on your OVHcloud Public Cloud Databases ([this guide](/de/guides/public-cloud/databases/getting-started.md) can help you to meet this requirement). - Access to your OVHcloud Control Panel or to the [OVHcloud API](https://eu.api.ovh.com/). ## Instructions :::warning The management of advanced parameters is not supported via Terraform. ::: ### Using the OVHcloud Control Panel Please refer to this [guide](/de/guides/public-cloud/databases/advanced-configuration.md#using-the-ovhcloud-control-panel) to find out how to change your advanced parameters from the OVHcloud Control Panel. ### Using API Please refer to this [guide](/de/guides/public-cloud/databases/advanced-configuration.md#using-api) to find out how to change your advanced parameters from the OVHcloud API. ### Advanced parameters for MySQL Below you can find a summary of every configuration option available for a MySQL service: | Parameters | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **mysql.connect\_timeout** `long`
min: `2` max: `3600`
The number of seconds that the mysqld server waits for a connect packet before responding with Bad handshake.
| | **mysql.default\_time\_zone** `string`
Default server time zone as an offset from UTC (from -12:00 to +12:00), a time zone name, or 'SYSTEM' to use the MySQL server default.
| | **mysql.group\_concat\_max\_len** `long`
min: `4` max: `18446744073709552000`
The maximum permitted result length in bytes for the GROUP\_CONCAT() function.
| | **mysql.information\_schema\_stats\_expiry** `long`
min: `900` max: `31536000`
The time, in seconds, before cached statistics expire.
| | **mysql.innodb\_change\_buffer\_max\_size** `long`
min: `0` max: `50`
Maximum size for the InnoDB change buffer, as a percentage of the total size of the buffer pool. Default is 25.
| | **mysql.innodb\_flush\_neighbors** `long`
min: `0` max: `2`
Specifies whether flushing a page from the InnoDB buffer pool also flushes other dirty pages in the same extent (default is 1): 0 - dirty pages in the same extent are not flushed, 1 - flush contiguous dirty pages in the same extent, 2 - flush dirty pages in the same extent.
| | **mysql.innodb\_ft\_min\_token\_size** `long`
min: `0` max: `16`
Minimum length of words that are stored in an InnoDB FULLTEXT index. Changing this parameter will lead to a restart of the MySQL service.
| | **mysql.innodb\_ft\_server\_stopword\_table** `string`
This option is used to specify your own InnoDB FULLTEXT index stopword list for all InnoDB tables.
| | **mysql.innodb\_lock\_wait\_timeout** `long`
min: `1` max: `3600`
The length of time in seconds an InnoDB transaction waits for a row lock before giving up. Default is 120.
| | **mysql.innodb\_log\_buffer\_size** `long`
min: `1048576` max: `4294967295`
The size in bytes of the buffer that InnoDB uses to write to the log files on disk.
| | **mysql.innodb\_online\_alter\_log\_max\_size** `long`
min: `65536` max: `1099511627776`
The upper limit in bytes on the size of the temporary log files used during online DDL operations for InnoDB tables.
| | **mysql.innodb\_print\_all\_deadlocks** `boolean`
When enabled, information about all deadlocks in InnoDB user transactions is recorded in the error log. Disabled by default.
| | **mysql.innodb\_read\_io\_threads** `long`
min: `1` max: `64`
The number of I/O threads for read operations in InnoDB. Default is 4. Changing this parameter will lead to a restart of the MySQL service.
| | **mysql.innodb\_rollback\_on\_timeout** `boolean`
When enabled a transaction timeout causes InnoDB to abort and roll back the entire transaction. Changing this parameter will lead to a restart of the MySQL service.
| | **mysql.innodb\_thread\_concurrency** `long`
min: `0` max: `1000`
Defines the maximum number of threads permitted inside of InnoDB. Default is 0 (infinite concurrency - no limit).
| | **mysql.innodb\_write\_io\_threads** `long`
min: `1` max: `64`
The number of I/O threads for write operations in InnoDB. Default is 4. Changing this parameter will lead to a restart of the MySQL service.
| | **mysql.interactive\_timeout** `long`
min: `30` max: `604800`
The number of seconds the server waits for activity on an interactive connection before closing it.
| | **mysql.internal\_tmp\_mem\_storage\_engine** `string`
values: `MEMORY`, `TempTable`
The storage engine for in-memory internal temporary tables.
| | **mysql.log\_output** `string`
values: `INSIGHTS`, `INSIGHTS,TABLE`, `NONE`, `TABLE`
The slow log output destination when slow\_query\_log is ON. To enable MySQL AI Insights, choose INSIGHTS. To use MySQL AI Insights and the mysql.slow\_log table at the same time, choose INSIGHTS,TABLE. To only use the mysql.slow\_log table, choose TABLE. To silence slow logs, choose NONE.
| | **mysql.long\_query\_time** `double`
min: `0` max: `3600`
The slow\_query\_logs work as SQL statements that take more than long\_query\_time seconds to execute.
| | **mysql.max\_allowed\_packet** `long`
min: `102400` max: `1073741824`
Size of the largest message in bytes that can be received by the server. Default is 67108864 (64M)
| | **mysql.max\_heap\_table\_size** `long`
min: `1048576` max: `1073741824`
Limits the size of internal in-memory tables. Also set tmp\_table\_size. Default is 16777216 (16M)
| | **mysql.net\_buffer\_length** `long`
min: `1024` max: `1048576`
Start sizes of connection buffer and result buffer. Default is 16384 (16K). Changing this parameter will lead to a restart of the MySQL service.
| | **mysql.net\_read\_timeout** `long`
min: `1` max: `3600`
The number of seconds to wait for more data from a connection before aborting the read.
| | **mysql.net\_write\_timeout** `long`
min: `1` max: `3600`
The number of seconds to wait for a block to be written to a connection before aborting the write.
| | **mysql.slow\_query\_log** `boolean`
Slow query log enables capturing of slow queries. Setting slow\_query\_log to false also truncates the mysql.slow\_log table.
| | **mysql.sort\_buffer\_size** `long`
min: `32768` max: `1073741824`
Sort buffer size in bytes for ORDER BY optimization. Default is 262144 (256K)
| | **mysql.sql\_mode** `string`
Global SQL mode. Set to empty to use MySQL server defaults. When creating a new service and not setting this field, Aiven default SQL mode (strict, SQL standard compliant) will be assigned.
| | **mysql.sql\_require\_primary\_key** `boolean`
Require primary key to be defined for new tables or old tables modified with ALTER TABLE and fail if missing. It is recommended to always have primary keys because various functionalities may break if any large table is missing them.
| | **mysql.tmp\_table\_size** `long`
min: `1048576` max: `1073741824`
Limits the size of internal in-memory tables. Also sets max\_heap\_table\_size. Default is 16777216 (16M).
| | **mysql.wait\_timeout** `long`
min: `1` max: `2147483`
The number of seconds the server waits for activity on a non-interactive connection before closing it.
| ## Go further Visit our dedicated Discord channel: [https://discord.gg/ovhcloud](https://discord.gg/ovhcloud). Ask questions, provide feedback and interact directly with the team that builds our databases services. If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/de/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project. Join our [community of users](https://community.ovhcloud.com/).