?
How many of the following shared tablespaces is bound by the OS file size limit?
How many of the following shared tablespaces is bound by the OS file size limit?
MyISAM, InnoDB, TRANSACTION
MyISAM, InnoDB, TRANSACTION
Answer & Solution
Correct Answer:
Option
B
This question is about how MySQL handles storage for different table types.
Let's break down the options:
* MyISAM: MyISAM tables are stored in separate files. Each MyISAM table has its own set of files. So they are not bound by the operating system (OS) file size limit.
* InnoDB: InnoDB tables store data in a shared tablespace. This tablespace is essentially a single file that holds data for multiple InnoDB tables. So they are bound by the OS file size limit.
* TRANSACTION: The transaction log for InnoDB is also stored in a shared tablespace, which is also a single file. So they are bound by the OS file size limit.
Therefore, the answer is Option C: 2. Two tablespaces, InnoDB and TRANSACTION, are bound by the OS file size limit.
Let's break down the options:
* MyISAM: MyISAM tables are stored in separate files. Each MyISAM table has its own set of files. So they are not bound by the operating system (OS) file size limit.
* InnoDB: InnoDB tables store data in a shared tablespace. This tablespace is essentially a single file that holds data for multiple InnoDB tables. So they are bound by the OS file size limit.
* TRANSACTION: The transaction log for InnoDB is also stored in a shared tablespace, which is also a single file. So they are bound by the OS file size limit.
Therefore, the answer is Option C: 2. Two tablespaces, InnoDB and TRANSACTION, are bound by the OS file size limit.
Join the Discussion
Login to post a comment or share your explanation.
Login