Last modified: October 10, 2024
The SQL section includes the following settings:
| Setting | Description | Values | Default |
|---|---|---|---|
| Include databases in disk usage calculations | If you enable this setting, your server will include databases in disk usage calculations. |
|
On |
| Use INFORMATION_SCHEMA to acquire MySQL disk usage | This setting uses MySQL’s INFORMATION_SCHEMA view to include MySQL table disk usage when it calculates disk usage totals. This setting causes MySQL to become unresponsive until data collection finishes, which may degrade your system’s performance.If you disable this setting, cPanel & WHM queries the filesystem for MySQL’s disk usage information. Table type usage and local configuration may cause inaccuracy in the disk usage totals. |
|
On |
| Allow cPanel & WHM to determine the best value for your MySQL open_files_limit configuration? | This setting allows cPanel & WHM to determine the best value for your MySQL open_files_limit setting in the /etc/systemd/system/ MySQL file. The system uses the total number of open tables in your databases to determine this value.Newer versions of MySQL require additional file descriptors for each open table. A server with a large number of open tables (for example, servers with multiple installations of WordPress®) may require an open_files_limit value that is greater than the default value of 2048. However, an extremely large open_files_limit setting requires more memory, and may cause performance issues.We recommend that you do not manually adjust the open_files_limit setting in the /etc/systemd/system/ MySQL file. If you manually adjust this setting and add more databases and tables, the system will not increase the limit. When you surpass the limit, you will receive an error. |
|
On |
| Allow cPanel & WHM to determine the best value for your MySQL max_allowed_packet configuration? | This setting allows cPanel to determine the best value for your MySQL max_allowed_packet setting in your server’s my.cnf configuration file. The max_allowed_packet setting determines the maximum size of a single packet for any generated or intermediate string. The value of this setting must be large enough to properly handle very long BLOB columns or long strings. However, an extremely large max_allowed_packet setting may catch unnecessarily large packets, and may cause performance issues.We recommend that you do not manually adjust the max_allowed_packet setting in your server’s my.cnf file. If you manually adjust this setting and add more databases and tables, the system will not increase the limit. When the system surpasses the limit, you will receive an error. |
|
On |
| Allow cPanel & WHM to determine the best value for your MySQL innodb_buffer_pool_size configuration? | This setting allows cPanel & WHM to determine the best value for your MySQL innodb_buffer_pool_size setting in your server’s my.cnf configuration file. The innodb_buffer_pool_size setting determines the size of the memory buffer in bytes that the InnoDB storage engine uses to cache data and indexes of its tables. However, an extremely large innodb_buffer_pool_size setting requires more memory and may cause performance issues. We recommend that you do not manually adjust the innodb_buffer_pool_size setting in your server’s my.cnf file. If you manually adjust this setting and add more databases and tables, the system will not increase the limit. When you surpass the limit, you will receive an error. |
|
Off |
| Require a username prefix on names of new databases and database users | When you enable database prefixing, the system prefixes database names and database usernames with a portion of the system username and an underscore.
|
|
On |
| Force short prefix for MySQL and MariaDB databases | If you enable this setting, your server will limit MySQL and MariaDB database prefixes to eight characters. |
|
Off |