Skip to content

Databases and warehouses

Find and export
your MySQL data.

MySQL exposes table-size metadata for accessible schemas. Its physical-storage statistics and a logical dump describe different representations of the same application data.

Report in
GB
Category
Databases and warehouses
Last checked

Find your MySQL data size

  1. Connect with an account that can inspect all application schemas in scope.
  2. Run the read-only information_schema query below.
  3. Record each schema's data-plus-index size and convert bytes to GB with the basis stated.
  4. Inspect key tables and their oldest business timestamps for counts and years covered.
SELECT table_schema,
       SUM(data_length + index_length) AS size_bytes
FROM information_schema.tables
WHERE table_schema NOT IN
  ('mysql', 'information_schema', 'performance_schema', 'sys')
GROUP BY table_schema
ORDER BY size_bytes DESC;
InnoDB storage and row statistics can be estimates and may be cached. Ask the administrator to confirm how current they are.

What to include in your data inventory

Report in GB, naming schemas and whether indexes are included. Give table or row quantities separately where available.

Describe the retained business period and any external file store. Identify production, archive and replica copies so totals stay interpretable.

Add the dates covered and the people who use this software. Label estimates and describe how you calculated them.

Export your MySQL history

  1. Have the administrator choose a consistent snapshot route appropriate to the table storage engines.
  2. Use mysqldump for the agreed schemas, including routines, triggers and events where required.
  3. For a larger collection, review MySQL Shell dump utilities, which support parallel compressed exports.
  4. Verify table coverage and collect external files and schema documentation separately.

The --single-transaction route provides its snapshot guarantee for suitable transactional tables such as InnoDB. Other engines need separate planning.

Physical storage, dump size and uncompressed record size can differ. Keep the measurement method with each quantity.

Why MySQL data has value for AI training

Relational tables can connect customers, transactions and operational events over time.

Schema relationships and field definitions provide the context needed to interpret those sequences.

What stays private

Choose schemas, tables and columns in scope, reviewing personal, credential and sensitive business fields.

Telegraph Lab reviews the proposed material with you and agrees how sensitive information will be handled. Preparation can include excluding material, redacting details and replacing personal identifiers. Your company keeps ownership; the licensing agreement defines the material, permitted uses and authorized recipients.

Common questions about MySQL data

Does TABLE_ROWS give an exact count?

For InnoDB it is an estimate. Use an exact count query when necessary and appropriate.

Why might recent changes be absent?

Storage statistics can be cached. Have the administrator check their freshness.

Does one dump option guarantee consistency for every engine?

Consistency depends on the table engines and export method. Have the administrator choose the route.

Are external uploads in the dump?

Collect files stored outside MySQL separately and retain their record relationships.

Your data inventory

Add your numbers to the picture.

Enter the quantities and years covered in your data inventory, then share it with your Telegraph Lab contact. We’ll review the material and discuss the next step with you.

Discuss your data