Search Results
https://dev.mysql.com/doc/heatwave/en/mys-hw-genai-nl-sql.html
This feature collects information on the schemas, tables, and columns that you have access to, and then uses a Large Language Model (LLM) to generate an SQL query for the question pertaining to your data. As of MySQL 9.4.1, MySQL HeatWave GenAI ...
https://dev.mysql.com/doc/heatwave/en/mys-hw-lakehouse-limitations-parquet.html
As of MySQL 9.1.2, you can load Parquet files with row groups that total up to 10GB with large MySQL HeatWave Cluster shapes. MySQL HeatWave Lakehouse has the following limitations for Parquet files. Consider the following limitations: To load ...
https://dev.mysql.com/doc/heatwave/en/mys-hwaml-ml-explain.html
MySQL 9.0.0 introduces support for large models that changes how MySQL HeatWave AutoML stores models. To run ML_EXPLAIN_ROW and ML_EXPLAIN_TABLE with a different explainer, you must first run ML_EXPLAIN with the same explainer. Running the ...
https://dev.mysql.com/doc/refman/8.4/en/information-schema-innodb-virtual-table.html
A row appears in the INNODB_VIRTUAL table for each column upon which a virtual generated column is based. The value is large because it encodes the column sequence number and ordinal position. The INNODB_VIRTUAL table provides metadata about InnoDB ...
https://dev.mysql.com/doc/refman/8.4/en/miscellaneous-optimization-tips.html
Similarly, if your application computes a single result based on several column values or large volumes of data, combining the computation into a loadable function can help performance. If you have data that does not conform well to a ... This ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-ndb-innodb-usage.html
When comparing application feature requirements to the capabilities of InnoDB with NDB, some are clearly more compatible with one storage engine than the other. The following table lists supported application features according to the storage ...
https://dev.mysql.com/doc/refman/8.4/en/mysql.html
If you have problems due to insufficient memory for large result sets, use the --quick option. This forces mysql to retrieve results from the server a row at a time rather than retrieving the entire result set and buffering it in memory before ...
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-timing.html
The time a statement (or stage) takes to execute is in general orders of magnitude larger than the time it takes to execute a single wait. Performance Schema Timer Representation in Events Rows in Performance Schema tables that store current events ... Events are collected by means of instrumentation added to the server source ...
https://dev.mysql.com/doc/refman/8.4/en/sys-schema-object-overview.html
Note For MySQL instances with a large number of objects, this view might take a long time to execute. This view summarizes the types of objects within each schema. object_type The object type: BASE TABLE, INDEX (index_type), EVENT, FUNCTION, ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-restore-cluster.html
Doing this can decrease the time required to restore a large data set, particularly where many indexes were in use. Stop the cluster using stop cluster, then restart it using start cluster with the --initial option, which causes the data node file ...