ÃÛ¶¹ÊÓƵ

DocumentationCommerceInstallation Guide

General MySQL guidelines

Last update: Wed Apr 17 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Experienced
  • Admin
  • Developer

See System Requirements for supported versions of MySQL.

ÃÛ¶¹ÊÓƵ strongly recommends you observe the following standard when you set up your database:

  • ÃÛ¶¹ÊÓƵ Commerce uses to improve database access during reindexing. These get created when the indexer mode is set to schedule. The application does not support any custom triggers in the database because custom triggers can introduce incompatibilities with future ÃÛ¶¹ÊÓƵ Commerce versions.
  • Familiarize yourself with before you continue.
  • To enhance your database security posture, enable the SQL mode to prevent storing invalid data values, which might cause unwanted database interactions.
  • ÃÛ¶¹ÊÓƵ Commerce does not support MySQL statement-based replication. Make sure you use only .
WARNING
ÃÛ¶¹ÊÓƵ Commerce currently uses CREATE TEMPORARY TABLE statements inside transactions, which are with database implementations use GTID-based replication, such as . Consider MySQL for Cloud SQL 8.0 as an alternative.
NOTE
If your web server and database server are on different hosts, perform the tasks discussed in this topic on the database server host then see Set up a remote MySQL database connection.

Installing MySQL on Ubuntu

ÃÛ¶¹ÊÓƵ Commerce 2.4 requires a clean installation of MySQL 8.0. Follow the links below for instructions on installing MySQL on your machine.

If you expect to import large numbers of products, you can increase the value for that is larger than the default, 16 MB.

NOTE
The default value applies to ÃÛ¶¹ÊÓƵ Commerce on cloud infrastructure and on-premises projects. ÃÛ¶¹ÊÓƵ Commerce on cloud infrastructure Pro customers must open a support ticket to increase the max_allowed_packet value. ÃÛ¶¹ÊÓƵ Commerce on cloud infrastructure Starter customers can increase the value by updating the configuration in the /etc/mysql/mysql.cnf file.

To increase the value, open the /etc/mysql/mysql.cnf file in a text editor and locate the value for max_allowed_packet. Save your changes to the mysql.cnf file, close the text editor, and restart MySQL (service mysql restart).

To optionally verify the value that you set, enter the following command at a mysql> prompt:

SHOW VARIABLES LIKE 'max_allowed_packet';

Then, Configure the database instance.

MySQL 8 changes

For ÃÛ¶¹ÊÓƵ Commerce 2.4, we added support for MySQL 8.
This section describes major changes to MySQL 8 that developers should be aware of.

Removed width for integer types (padding)

The display width specification for integer data types (TINYINT, SMALLINT, MEDIUMINT, INT, BIGINT) has been deprecated in MySQL 8.0.17. Statements that include data-type definitions in their output no longer show the display width for integer types, except for TINYINT(1). MySQL Connectors assume that TINYINT(1) columns originated as BOOLEAN columns. This exception enables them to continue to make that assumption.

Example

Describe admin_user at mysql 8.19

Field
Type
Null
Key
Default
Extra
user_id
int unsigned
NO
PRI
NULL
auto_increment
firstname
varchar(32)
YES
NULL
lastname
varchar(32)
YES
NULL
email
varchar(128)
YES
NULL
username
varchar(40)
YES
UNI
NULL
password
varchar(255)
NO
NULL
created
timestamp
NO
CURRENT_TIMESTAMP
DEFAULT_GENERATED
modified
timestamp
NO
CURRENT_TIMESTAMP
DEFAULT_GENERATED on update CURRENT_TIMESTAMP
logdate
timestamp
YES
NULL
lognum
smallint unsigned
NO
0

Except for TINYINT(1), all integer padding (TINYINT > 1, SMALLINT, MEDIUMINT, INT, BIGINT) should be removed from the db_schema.xml file.

For more information, see .

Default ORDER BY behavior

Before 8.0, entries were sorted by the foreign key. Default sort order depends on the engine that is used.
Always specify a sort order if your code depends on a specific sort.

Deprecated ASC and DESC qualifiers for GROUP BY

As of MySQL 8.0.13, the deprecated ASC or DESC qualifiers for GROUP BY clauses have been removed. Queries that previously relied on GROUP BY sorting may produce results that differ from previous MySQL versions. To produce a given sort order, provide an ORDER BY clause.

Commerce and MySQL 8

There have been some changes to ÃÛ¶¹ÊÓƵ Commerce to properly support MySQL 8.

Query and Insert Behavior

ÃÛ¶¹ÊÓƵ Commerce disabled the regular validation behavior by setting SET SQL_MODE=‘’ in /lib/internal/Magento/Framework/DB/Adapter/Pdo/Mysql.php:424.. With validation disabled, it is possible that MySQL truncates data. In MySQL, the Query behavior has changed: Select * on my_table where IP='127.0.0.1' no longer returns results because the IP address is now properly seen as a string, rather than an integer.

Upgrading from MySQL 5.7 to MySQL 8

To properly update MySQL from version 5.7 to version 8, you must follow these steps in order:

  1. Upgrade ÃÛ¶¹ÊÓƵ Commerce to 2.4.0.
    Test everything and make sure that your system works as expected.

  2. Enable maintenance mode:

    code language-bash 
    bin/magento maintenance:enable

  3. Make a database backup:

    code language-bash 
    bin/magento setup:backup --db

  4. Update MySQL to version 8.

  5. Import the backed-up data into MySQL.

  6. Clean the cache:

    code language-bash 
    bin/magento cache:clean

  7. Disable maintenance mode:

    code language-bash 
    bin/magento maintenance:disable

Configuring the database instance

This section discusses how to create a database instance for ÃÛ¶¹ÊÓƵ Commerce. Although a new database instance is recommended, you can optionally install ÃÛ¶¹ÊÓƵ Commerce with an existing database instance.

To configure a MySQL database instance:

  1. Log in to your database server as any user.

  2. Get to a MySQL command prompt:

    code language-bash 
    mysql -u root -p

  3. Enter the MySQL root user’s password when prompted.

  4. Enter the following commands in the order shown to create a database instance named magento with username magento:

    code language-sql 
    create database magento;
    code language-sql 
    create user 'magento'@'localhost' IDENTIFIED BY 'magento';
    code language-sql 
    GRANT ALL ON magento.* TO 'magento'@'localhost';
    code language-sql 
    flush privileges;

  5. Enter exit to quit the command prompt.

  6. Verify the database:

    code language-bash 
    mysql -u magento -p

    If the MySQL monitor displays, you created the database properly. If an error displays, repeat the preceding commands.

  7. If your web server and database server are on different hosts, perform the tasks discussed in this topic on the database server host then see Set up a remote MySQL database connection.

    We recommend you configure your database instance as appropriate for your business. When configuring your database, please keep the following in mind:

    • Indexers require higher tmp_table_size and max_heap_table_size values (for example, 64 M). If you configure the batch_size parameter, you can adjust that value along with the table size settings to improve indexer performance. Refer to the Optimization Guide for more information.

    • For optimal performance, make sure all MySQL and ÃÛ¶¹ÊÓƵ Commerce index tables can be kept in memory (for example, configure innodb_buffer_pool_size).

    • Reindexing on MariaDB 10.4 takes more time compared to other MariaDB or MySQL versions. See Configuration best practices.

  8. For MySQL TIMESTAMP fields to follow the preferences and composition expected by the application’s declarative schema architecture, the system variable explicit_defaults_for_timestamp must be set to on.

    References:

    If this setting is not enabled, bin/magento setup:db:status always reports that the Declarative Schema is not up to date.

NOTE
The explicit_defaults_for_timestamp setting is deprecated. This setting controls deprecated TIMESTAMP behaviors that will be removed in a future MySQL release. When those behaviors are removed, the explicit_defaults_for_timestamp setting is removed as well.
WARNING
For ÃÛ¶¹ÊÓƵ Commerce on cloud infrastructure projects, the explicit_defaults_for_timestamp setting for MySQL (MariaDB) defaults to OFF.

Reindexing on MariaDB 10.4 and 10.6 takes more time compared to previous MariaDB or MySQL versions. To speed up reindexing, we recommend setting these MariaDB configuration parameters:

If you experience performance degradation not related to indexation after upgrading to MariaDB 10.6, consider enabling the setting. For example, --query-cache-type=ON.

Before upgrading ÃÛ¶¹ÊÓƵ Commerce on cloud infrastructure projects, you may also need to upgrade MariaDB (see MariaDB upgrade best practices).

For example:

  • ÃÛ¶¹ÊÓƵ Commerce 2.4.6 with MariaDB version 10.5.1 or higher
  • ÃÛ¶¹ÊÓƵ Commerce 2.3.5 with MariaDB version 10.3 or earlier

In addition to these recommendations, you should consult with your database administrator on configuring the following parameters:

NOTE
These settings are available for on-premises deployments only. ÃÛ¶¹ÊÓƵ Commerce on cloud infrastructure customers do not have access to these settings.
recommendation-more-help
0f8e7db5-0e9c-4002-a5b8-a0088077d995