MySQL Enterprise Monitor 8.0 Release Notes
This section describes the Schema advisors.
Many applications need to generate unique numbers and sequences for identification purposes, such as customer IDs, bug or trouble ticket tags, membership or order numbers, and so on. MySQL's mechanism for doing this is the AUTO_INCREMENT column attribute, which enables you to generate sequential numbers automatically.
However, the range of numbers that can be generated is limited by the underlying data type. For example, the maximum value possible for a TINYINT UNSIGNED column is 255. If you try to generate a number that exceeds the maximum allowed by the underlying data type, such as by inserting a NULL value into the AUTO_INCREMENT column, database errors are triggered and your application may not behave properly.
The primary purpose of AUTO_INCREMENT in MySQL is to generate a sequence of positive integers. The use of non-positive numbers in an AUTO_INCREMENT column is unsupported, so you may as well define those columns to be UNSIGNED, which effectively doubles their allowable range.
Default frequency 06:00:00
Default auto-close enabled no
For development environments, changes to databases and objects may be a normal occurrence, but not for production environments. It is wise to know when any changes occur in a production environment with respect to any database structures and investigate the reasons for the changes.
Default frequency 00:10:00
Default auto-close enabled no
For development environments, changes to databases and objects may be a normal occurrence, but not for production environments. It is wise to know when any changes occur in a production environment with respect to any database structures and investigate the reasons for the changes.
Default frequency 00:10:00
Default auto-close enabled no
For development environments, changes to databases and objects may be a normal occurrence, but not for production environments. It is wise to know when any changes occur in a production environment with respect to any database structures and investigate the reasons for the changes.
Default frequency 00:10:00
Default auto-close enabled no
For development environments, changes to databases and objects may be a normal occurrence, but not for production environments. It is wise to know when any changes occur in a production environment with respect to any database structures and investigate the reasons for the changes.
Default frequency 00:10:00
Default auto-close enabled no
For development environments, changes to databases and objects may be a normal occurrence, but not for production environments. It is wise to know when any changes occur in a production environment with respect to any database structures or functions and investigate the reasons for the changes.
Default frequency 00:10:00
Default auto-close enabled no
For development environments, changes to databases and objects may be a normal occurrence, but not for production environments. It is wise to know when any changes occur in a production environment with respect to any database structures and investigate the reasons for the changes.
Default frequency 00:10:00
Default auto-close enabled no
For development environments, changes to databases and objects may be a normal occurrence, but not for production environments. It is wise to know when any changes occur in a production environment with respect to any database structures and investigate the reasons for the changes.
Default frequency 00:10:00
Default auto-close enabled no
The MySQL optimizer needs index statistics to help make choices about whether to use indexes to satisfy SQL queries. Having no statistics or outdated statistics limits the optimizer's ability to make smart and informed access plan choices.
Default frequency 12:00:00
Default auto-close enabled no
For development environments, changes to databases and objects may be a normal occurrence, but not for production environments. It is wise to know when any changes occur in a production environment with respect to any database structures and investigate the reasons for the changes.
Default frequency 00:10:00
Default auto-close enabled no
SQL Modes define what SQL syntax MySQL should support and what kind of data validation checks it should perform. If no SQL modes are enabled this means there is no form of server-enforced data integrity, which means incoming data that is invalid is not rejected by the server, but is instead changed to conform to the target column's default datatype.
Note
Any client can change its own session SQL mode value at any time.
For more information, see Server SQL Modes.
Default frequency 06:00:00
Default auto-close enabled no
SQL Modes define what SQL syntax MySQL should support and what
kind of data validation checks it should perform. There are many
possible options that can be used in conjunction with each other
to specify varying degrees of syntax and data validation checks
the MySQL server performs. However, to ensure the highest level
of confidence for data integrity, at least one of the following
should be included in the list: TRADITIONAL,
STRICT_TRANS_TABLES, or
STRICT_ALL_TABLES.
For more information, see Server SQL Modes.
Note
Any client can change its own session SQL mode value at any time.
Default frequency 06:00:00
Default auto-close enabled no
For development environments, changes to databases and objects may be a normal occurrence, but not for production environments. It is wise to know when any changes occur in a production environment with respect to database structures and investigate the reasons for the changes.
Default frequency 00:10:00
Default auto-close enabled no
For development environments, changes to databases and objects may be a normal occurrence, but not for production environments. It is wise to know when any changes occur in a production environment with respect to database structures and investigate the reasons for the changes.
Default frequency 00:10:00
Default auto-close enabled no
For development environments, changes to databases and objects may be a normal occurrence, but not for production environments. It is wise to know when changes occur in a production environment with respect to database structures and investigate the reasons for the changes.
Default frequency 00:10:00
Default auto-close enabled no
A primary or unique key of a relational table uniquely identifies each record in the table. Except in very unusual circumstances, every database table should have one or more columns designated as the primary key or as a unique key, and it is common practice to declare one.
Note
Tables lacking primary or unique keys can have a very negative
impact on replication performance when using
binlog_format=ROW.
Default frequency 12:00:00
Default auto-close enabled no
For development environments, changes to databases and objects may be a normal occurrence, but not for production environments. It is wise to know when changes occur in a production environment with respect to database structures and investigate the reasons for the changes.
Default frequency 00:10:00
Default auto-close enabled no