Which of the following is true for how the InnoDB storage engine uses diskspace?

Question

Options

• AIt stores its data, index and undo information all in its own tablespace.
• BIt stores its data in .MYD files, in the respective database directory, and its index and undo
• CIt stores its data and index in .MYD and .MYI files, in the respective database directory, and undo
• DIt stores its data, index and undo information in .MYD and .MYI files, in the respective database

• A
  72% (23)
• B
  16% (5)
• C
  9% (3)
• D
  3% (1)

Explanation

On disk, MySQL represents each MyISAM table using three files: a format file that stores the definition of the table structure, a data file that stores the contents of table rows, and an index file that stores any indexes on the table. These files are distinguished from one another by their suffixes. For example, the format, data, and index files for a table named mytable are called mytable.frm, mytable.MYD, and mytable.MYI. The InnoDB Tablespace and Logs Each InnoDB table has a format (.frm) file in the database directory of the database to which the table belongs. This is the same as tables managed by any other MySQL storage engine, such as MyISAM. However, InnoDB manages table contents (data rows and indexes) on disk differently than does the MyISAM engine. By default, InnoDB uses a shared "tablespace," which is one or more files that form a single logical storage area. All InnoDB tables are stored together within the tablespace. There are no table-specific data files or index files for InnoDB the way there are for MyISAM tables. The tablespace also contains a rollback segment. As transactions modify rows, undo log information is stored in the rollback segment. This information is used to roll back failed transactions.

No community discussion yet for this question.