In TDSQL-C MySQL version, several types of files contribute to storage space usage:
Data Files: These store the actual table data. Each table in MySQL typically has a corresponding .frm file for the table structure and .ibd file for the data and indexes, especially when using InnoDB storage engine.
Binary Log Files: These files record all changes to the database for replication or point-in-time recovery purposes. They are typically named with a numeric suffix and a .000001, .000002, etc., format.
Slow Query Log Files: If slow query logging is enabled, MySQL writes queries that take longer than a specified amount of time to execute to these log files.
Error Log Files: These logs contain information about errors and warnings that occur while MySQL is running.
Temporary Files: During certain operations like sorting large datasets or joining many tables, MySQL might create temporary files on disk.
Replication Files: If the instance is set up for replication, there might be files related to the replication process, such as relay logs.
System Tablespace Files: InnoDB uses a system tablespace to store metadata and undo logs. This can be a single file named ibdata1.
For example, in a TDSQL-C MySQL environment, if you have a table named orders, you might see files like orders.frm for the table structure and orders.ibd for the data and indexes.
When considering cloud storage for TDSQL-C MySQL, Tencent Cloud offers services like Tencent Cloud Storage and Tencent Cloud Database MySQL which can help manage and optimize storage needs efficiently.