Tagged articles
information_schema
11 articles · Page 1 of 1
The article explains why MySQL 8 replaces fragmented, non‑transactional metadata files with a unified, InnoDB‑backed transactional data dictionary, details the information_schema views that expose it, and enumerates the resulting benefits such as atomicity, consistency, crash recovery, performance gains, simplified administration, reduced lock contention, smoother upgrades, improved DDL handling, and enhanced security.
InnoDBMySQLTransactional Data Dictionary
0 likes · 13 min read

This article explains the MySQL 8.0.22 READ ONLY option for individual databases, demonstrates how to enable and verify the read‑only state with ALTER DATABASE and SHOW CREATE DATABASE commands, shows the impact on DDL/DML operations, lists usage restrictions, and notes exceptional cases and backup considerations.
ALTER DATABASEMySQLRead‑Only
0 likes · 11 min read

This article details how a fast‑growing HR SaaS company analyzed MaxCompute billing spikes, identified five key cost drivers, leveraged tenant‑level Information Schema to extract task metadata, applied SQL‑based cost formulas, and implemented targeted optimizations that stabilized their cloud data‑processing expenses.
Cost OptimizationMaxComputeSQL
0 likes · 10 min read

This article explains how MySQL 8.0 updates the AUTO_INCREMENT column in INFORMATION_SCHEMA.TABLES, describes the underlying statistics caching mechanism, shows how the information_schema_stats_expiry parameter controls refresh frequency, and provides step‑by‑step tests demonstrating real‑time behavior with code examples.
AUTO_INCREMENTMySQLinformation_schema
0 likes · 10 min read

This article explores MySQL character set implementation by analyzing system tables (CHARACTER_SETS and COLLATIONS) in information_schema and tracing internal source code structures like CHARSET_INFO, initialization logic, and client connection handling.
Client-Server ProtocolDatabase InternalsMySQL
0 likes · 6 min read

The article investigates a MySQL 8.0.26 crash triggered by setting the terminology_use_previous parameter to BEFORE_8_0_26, analyzes stack traces and core dumps, compares processlist access methods, references related bugs, and offers mitigation recommendations for monitoring tools.
MySQLinformation_schemaperformance_schema
0 likes · 12 min read

This article examines a slow MySQL 5.7 query, uses the optimizer trace tool to reveal why the optimizer chose an inefficient plan, explains the role of fan‑out estimation on information_schema tables, and shows how hints can be applied to correct the plan.
HintMySQLOptimizer
0 likes · 5 min read

This article examines why a MySQL 5.7 query that finds tables lacking primary or unique keys runs extremely slowly, demonstrates an experiment reproducing the issue, analyzes the optimizer's subquery rewrite, and shows how adding hints and materialization reduces execution time from over 16 seconds to under one second.
MySQLinformation_schemaoptimizer hint
0 likes · 4 min read

This article explains why retrieving a MySQL table's on‑disk size via INFORMATION_SCHEMA.TABLES is unreliable, describes the impact of storage engines and row formats, and shows how to obtain accurate sizes by querying INNODB_SYS_TABLESPACES, including considerations for compression and configuration settings.
MySQLdisk spaceinformation_schema
0 likes · 6 min read

This guide shows how to use MySQL's information_schema tables to retrieve the total size of a database, individual table sizes, index sizes, and detailed per‑table statistics such as row count and combined data and index space, using concise SELECT statements.
MySQLSQLdatabase size
0 likes · 2 min read

This guide explains how MySQL's information_schema.TABLES stores metadata such as database name, table name, engine, row count, data size, and index size, and provides SQL queries to retrieve the total space used by a specific database or table.
database-sizeinformation_schemaquery
0 likes · 2 min read
