Your MySQL server was upgraded from an earlier major version.
The sales database contains three tables, one of which is the transactions table, which has 4 million rows.
You are running low on disk space on the datadir partition and begin to investigate.
Examine these commands and output:
Which two statements are true? (Choose two.)
Examining the provided outputs, innodb_file_per_table is set to ON. This means newer tables would have their own tablespace files, unlike older tables that could have been created when this setting was OFF. The transactions table seems to be using the shared tablespace, indicating it was likely created when innodb_file_per_table was OFF, which supports option E. Given its large size, truncating the transactions table would free up significant disk space as the table contains 4 million rows, supporting option D.
is it AE or CE? is it crazy to truncate sales data?
If was E was true, the individual tables, wouldn't exist, and empty database on disk would, it is wrong.
A and C. compresion will most likely work. truncate will work because truncate now drops and adds the table.
It is C and E. the transactions table doesn't have its own data file, so it uses the general tablespace. truncate won't free up space. Is was created when the variable was OFF. Ignore my other comments.
Row compress may not shrink down ibdata file