<div id="docs-body">
 <div class="section">
  <div class="titlepage">
   <div>
    <div>
     <h2 class="title">
      <a name="faqs-storage-engines">
      </a>
      A.2 MySQL 8.4 FAQ: Storage Engines
     </h2>
    </div>
   </div>
  </div>
  <div class="qandaset">
   <a name="idm46045056447408">
   </a>
   <dl>
    <dt>
     A.2.1.
     <a href="faqs-storage-engines.html#faq-mysql-what-storage-engines">
      Where can I obtain complete documentation for MySQL storage
        engines?
     </a>
    </dt>
    <dt>
     A.2.2.
     <a href="faqs-storage-engines.html#faq-mysql-have-new-storage-engines">
      Are there any new storage engines in MySQL 8.4?
     </a>
    </dt>
    <dt>
     A.2.3.
     <a href="faqs-storage-engines.html#faq-mysql-removed-storage-engines">
      Have any storage engines been removed in MySQL 8.4?
     </a>
    </dt>
    <dt>
     A.2.4.
     <a href="faqs-storage-engines.html#faq-mysql-disabling-storage-engines">
      Can I prevent the use of a particular storage engine?
     </a>
    </dt>
    <dt>
     A.2.5.
     <a href="faqs-storage-engines.html#faq-mysql-innodb-backup-recovery-advantage">
      Is there an advantage to using the InnoDB
        storage engine exclusively, as opposed to a combination of
        InnoDB and non-InnoDB
        storage engines?
     </a>
    </dt>
    <dt>
     A.2.6.
     <a href="faqs-storage-engines.html#faq-mysql-what-archive-engine">
      What are the unique benefits of the ARCHIVE
        storage engine?
     </a>
    </dt>
   </dl>
   <table border="0" style="width: 100%;">
    <colgroup>
     <col align="left" width="1%"/>
     <col/>
    </colgroup>
    <tbody>
     <tr class="question">
      <td align="left" valign="top">
       <a name="faq-mysql-what-storage-engines">
       </a>
       <a name="idm46045056446592">
       </a>
       <p>
        <b>
         A.2.1.
        </b>
       </p>
      </td>
      <td align="left" valign="top">
       <p>
        Where can I obtain complete documentation for MySQL storage
        engines?
       </p>
      </td>
     </tr>
     <tr class="answer">
      <td align="left" valign="top">
      </td>
      <td align="left" valign="top">
       <p>
        See
        <a class="xref" href="storage-engines.html" title="Chapter 18 Alternative Storage Engines">
         Chapter 18,
         <i>
          Alternative Storage Engines
         </i>
        </a>
        . That chapter contains
        information about all MySQL storage engines except for the
        <a class="link" href="innodb-storage-engine.html" title="Chapter 17 The InnoDB Storage Engine">
         <code class="literal">
          InnoDB
         </code>
        </a>
        storage engine and the
        <a class="link" href="mysql-cluster.html" title="Chapter 25 MySQL NDB Cluster 8.4">
         <code class="literal">
          NDB
         </code>
        </a>
        storage engine (used for MySQL
        Cluster).
        <a class="link" href="innodb-storage-engine.html" title="Chapter 17 The InnoDB Storage Engine">
         <code class="literal">
          InnoDB
         </code>
        </a>
        is covered in
        <a class="xref" href="innodb-storage-engine.html" title="Chapter 17 The InnoDB Storage Engine">
         Chapter 17,
         <i>
          The InnoDB Storage Engine
         </i>
        </a>
        .
        <a class="link" href="mysql-cluster.html" title="Chapter 25 MySQL NDB Cluster 8.4">
         <code class="literal">
          NDB
         </code>
        </a>
        is covered in
        <a class="xref" href="mysql-cluster.html" title="Chapter 25 MySQL NDB Cluster 8.4">
         Chapter 25,
         <i>
          MySQL NDB Cluster 8.4
         </i>
        </a>
        .
       </p>
      </td>
     </tr>
     <tr class="question">
      <td align="left" valign="top">
       <a name="faq-mysql-have-new-storage-engines">
       </a>
       <a name="idm46045056437616">
       </a>
       <p>
        <b>
         A.2.2.
        </b>
       </p>
      </td>
      <td align="left" valign="top">
       <p>
        Are there any new storage engines in MySQL 8.4?
       </p>
      </td>
     </tr>
     <tr class="answer">
      <td align="left" valign="top">
      </td>
      <td align="left" valign="top">
       <p>
        No.
        <code class="literal">
         InnoDB
        </code>
        is the default storage engine for
        new tables. See
        <a class="xref" href="innodb-introduction.html" title="17.1 Introduction to InnoDB">
         Section 17.1, “Introduction to InnoDB”
        </a>
        for
        details.
       </p>
      </td>
     </tr>
     <tr class="question">
      <td align="left" valign="top">
       <a name="faq-mysql-removed-storage-engines">
       </a>
       <a name="idm46045056434096">
       </a>
       <p>
        <b>
         A.2.3.
        </b>
       </p>
      </td>
      <td align="left" valign="top">
       <p>
        Have any storage engines been removed in MySQL 8.4?
       </p>
      </td>
     </tr>
     <tr class="answer">
      <td align="left" valign="top">
      </td>
      <td align="left" valign="top">
       <p>
        No.
       </p>
      </td>
     </tr>
     <tr class="question">
      <td align="left" valign="top">
       <a name="faq-mysql-disabling-storage-engines">
       </a>
       <a name="idm46045056432208">
       </a>
       <p>
        <b>
         A.2.4.
        </b>
       </p>
      </td>
      <td align="left" valign="top">
       <p>
        Can I prevent the use of a particular storage engine?
       </p>
      </td>
     </tr>
     <tr class="answer">
      <td align="left" valign="top">
      </td>
      <td align="left" valign="top">
       <p>
        Yes. The
        <a class="link" href="server-system-variables.html#sysvar_disabled_storage_engines">
         <code class="literal">
          disabled_storage_engines
         </code>
        </a>
        configuration option defines which storage engines cannot be
        used to create tables or tablespaces. By default,
        <a class="link" href="server-system-variables.html#sysvar_disabled_storage_engines">
         <code class="literal">
          disabled_storage_engines
         </code>
        </a>
        is
        empty (no engines disabled), but it can be set to a
        comma-separated list of one or more engines.
       </p>
      </td>
     </tr>
     <tr class="question">
      <td align="left" valign="top">
       <a name="faq-mysql-innodb-backup-recovery-advantage">
       </a>
       <a name="idm46045056427312">
       </a>
       <p>
        <b>
         A.2.5.
        </b>
       </p>
      </td>
      <td align="left" valign="top">
       <p>
        Is there an advantage to using the
        <code class="literal">
         InnoDB
        </code>
        storage engine exclusively, as opposed to a combination of
        <code class="literal">
         InnoDB
        </code>
        and non-
        <code class="literal">
         InnoDB
        </code>
        storage engines?
       </p>
      </td>
     </tr>
     <tr class="answer">
      <td align="left" valign="top">
      </td>
      <td align="left" valign="top">
       <p>
        Yes. Using
        <code class="literal">
         InnoDB
        </code>
        tables exclusively can
        simplify backup and recovery operations. MySQL Enterprise Backup does a
        <a class="link" href="glossary.html#glos_hot_backup" title="hot backup">
         hot backup
        </a>
        of all tables
        that use the
        <code class="literal">
         InnoDB
        </code>
        storage engine. For
        tables using
        <code class="literal">
         MyISAM
        </code>
        or other
        non-
        <code class="literal">
         InnoDB
        </code>
        storage engines, it does a
        <span class="quote">
         “
         <span class="quote">
          warm
         </span>
         ”
        </span>
        backup, where the database continues to run,
        but those tables cannot be modified while being backed up. See
        <a class="xref" href="mysql-enterprise-backup.html" title="32.1 MySQL Enterprise Backup Overview">
         Section 32.1, “MySQL Enterprise Backup Overview”
        </a>
        .
       </p>
      </td>
     </tr>
     <tr class="question">
      <td align="left" valign="top">
       <a name="faq-mysql-what-archive-engine">
       </a>
       <a name="idm46045056418032">
       </a>
       <p>
        <b>
         A.2.6.
        </b>
       </p>
      </td>
      <td align="left" valign="top">
       <p>
        What are the unique benefits of the
        <code class="literal">
         ARCHIVE
        </code>
        storage engine?
       </p>
      </td>
     </tr>
     <tr class="answer">
      <td align="left" valign="top">
      </td>
      <td align="left" valign="top">
       <p>
        The
        <code class="literal">
         ARCHIVE
        </code>
        storage engine stores large
        amounts of data without indexes; it has a small footprint, and
        performs selects using table scans. See
        <a class="xref" href="archive-storage-engine.html" title="18.5 The ARCHIVE Storage Engine">
         Section 18.5, “The ARCHIVE Storage Engine”
        </a>
        , for details.
       </p>
      </td>
     </tr>
    </tbody>
   </table>
  </div>
 </div>
 <br/>
</div>
