<div id="docs-body">
 <div class="section">
  <div class="titlepage">
   <div>
    <div>
     <h3 class="title">
      <a name="information-schema-tables-table">
      </a>
      28.3.38 The INFORMATION_SCHEMA TABLES Table
     </h3>
    </div>
   </div>
  </div>
  <a class="indexterm" name="idm46045078469936">
  </a>
  <p>
   The
   <a class="link" href="information-schema-tables-table.html" title="28.3.38 The INFORMATION_SCHEMA TABLES Table">
    <code class="literal">
     TABLES
    </code>
   </a>
   table provides information
      about tables in databases.
  </p>
  <p>
   Columns in
   <a class="link" href="information-schema-tables-table.html" title="28.3.38 The INFORMATION_SCHEMA TABLES Table">
    <code class="literal">
     TABLES
    </code>
   </a>
   that represent
      table statistics hold cached values. The
   <a class="link" href="server-system-variables.html#sysvar_information_schema_stats_expiry">
    <code class="literal">
     information_schema_stats_expiry
    </code>
   </a>
   system variable defines the period of time before cached table
      statistics expire. The default is 86400 seconds (24 hours). If
      there are no cached statistics or statistics have expired,
      statistics are retrieved from storage engines when querying table
      statistics columns. To update cached values at any time for a
      given table, use
   <a class="link" href="analyze-table.html" title="15.7.3.1 ANALYZE TABLE Statement">
    <code class="literal">
     ANALYZE TABLE
    </code>
   </a>
   . To
      always retrieve the latest statistics directly from storage
      engines, set
   <a class="link" href="server-system-variables.html#sysvar_information_schema_stats_expiry">
    <code class="literal">
     information_schema_stats_expiry
    </code>
   </a>
   to
   <code class="literal">
    0
   </code>
   . For more information, see
   <a class="xref" href="information-schema-optimization.html" title="10.2.3 Optimizing INFORMATION_SCHEMA Queries">
    Section 10.2.3, “Optimizing INFORMATION_SCHEMA Queries”
   </a>
   .
  </p>
  <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
   <div class="admon-title">
    Note
   </div>
   <p>
    If the
    <a class="link" href="innodb-parameters.html#sysvar_innodb_read_only">
     <code class="literal">
      innodb_read_only
     </code>
    </a>
    system
        variable is enabled,
    <a class="link" href="analyze-table.html" title="15.7.3.1 ANALYZE TABLE Statement">
     <code class="literal">
      ANALYZE
        TABLE
     </code>
    </a>
    may fail because it cannot update statistics
        tables in the data dictionary, which use
    <code class="literal">
     InnoDB
    </code>
    . For
    <a class="link" href="analyze-table.html" title="15.7.3.1 ANALYZE TABLE Statement">
     <code class="literal">
      ANALYZE
        TABLE
     </code>
    </a>
    operations that update the key distribution,
        failure may occur even if the operation updates the table itself
        (for example, if it is a
    <code class="literal">
     MyISAM
    </code>
    table). To
        obtain the updated distribution statistics, set
    <a class="link" href="server-system-variables.html#sysvar_information_schema_stats_expiry">
     <code class="literal">
      information_schema_stats_expiry=0
     </code>
    </a>
    .
   </p>
  </div>
  <p>
   The
   <a class="link" href="information-schema-tables-table.html" title="28.3.38 The INFORMATION_SCHEMA TABLES Table">
    <code class="literal">
     TABLES
    </code>
   </a>
   table has these columns:
  </p>
  <div class="itemizedlist">
   <ul class="itemizedlist" style="list-style-type: disc; ">
    <li class="listitem">
     <p>
      <code class="literal">
       TABLE_CATALOG
      </code>
     </p>
     <p>
      The name of the catalog to which the table belongs. This value
          is always
      <code class="literal">
       def
      </code>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       TABLE_SCHEMA
      </code>
     </p>
     <p>
      The name of the schema (database) to which the table belongs.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       TABLE_NAME
      </code>
     </p>
     <p>
      The name of the table.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       TABLE_TYPE
      </code>
     </p>
     <p>
      <code class="literal">
       BASE TABLE
      </code>
      for a table,
      <code class="literal">
       VIEW
      </code>
      for a view, or
      <code class="literal">
       SYSTEM
          VIEW
      </code>
      for an
      <code class="literal">
       INFORMATION_SCHEMA
      </code>
      table.
     </p>
     <p>
      The
      <a class="link" href="information-schema-tables-table.html" title="28.3.38 The INFORMATION_SCHEMA TABLES Table">
       <code class="literal">
        TABLES
       </code>
      </a>
      table does not list
      <code class="literal">
       TEMPORARY
      </code>
      tables.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       ENGINE
      </code>
     </p>
     <p>
      The storage engine for the table. See
      <a class="xref" href="innodb-storage-engine.html" title="Chapter 17 The InnoDB Storage Engine">
       Chapter 17,
       <i>
        The InnoDB Storage Engine
       </i>
      </a>
      , and
      <a class="xref" href="storage-engines.html" title="Chapter 18 Alternative Storage Engines">
       Chapter 18,
       <i>
        Alternative Storage Engines
       </i>
      </a>
      .
     </p>
     <p>
      For partitioned tables,
      <code class="literal">
       ENGINE
      </code>
      shows the
          name of the storage engine used by all partitions.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       VERSION
      </code>
     </p>
     <p>
      This column is unused. With the removal of
      <code class="filename">
       .frm
      </code>
      files in MySQL 8.0, this column now
          reports a hardcoded value of
      <code class="literal">
       10
      </code>
      , which is
          the last
      <code class="filename">
       .frm
      </code>
      file version used in MySQL
          5.7.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       ROW_FORMAT
      </code>
     </p>
     <p>
      The row-storage format (
      <code class="literal">
       Fixed
      </code>
      ,
      <code class="literal">
       Dynamic
      </code>
      ,
      <code class="literal">
       Compressed
      </code>
      ,
      <code class="literal">
       Redundant
      </code>
      ,
      <code class="literal">
       Compact
      </code>
      ). For
      <code class="literal">
       MyISAM
      </code>
      tables,
      <code class="literal">
       Dynamic
      </code>
      corresponds to what
      <a class="link" href="myisamchk.html" title="6.6.4 myisamchk — MyISAM Table-Maintenance Utility">
       <span class="command">
        <strong>
         myisamchk -dvv
        </strong>
       </span>
      </a>
      reports
          as
      <code class="literal">
       Packed
      </code>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       TABLE_ROWS
      </code>
     </p>
     <p>
      The number of rows. Some storage engines, such as
      <code class="literal">
       MyISAM
      </code>
      , store the exact count. For other
          storage engines, such as
      <code class="literal">
       InnoDB
      </code>
      , this value
          is an approximation, and may vary from the actual value by as
          much as 40% to 50%. In such cases, use
      <code class="literal">
       SELECT
          COUNT(*)
      </code>
      to obtain an accurate count.
     </p>
     <p>
      <code class="literal">
       TABLE_ROWS
      </code>
      is
      <code class="literal">
       NULL
      </code>
      for
      <code class="literal">
       INFORMATION_SCHEMA
      </code>
      tables.
     </p>
     <p>
      For
      <a class="link" href="innodb-storage-engine.html" title="Chapter 17 The InnoDB Storage Engine">
       <code class="literal">
        InnoDB
       </code>
      </a>
      tables, the row count
          is only a rough estimate used in SQL optimization. (This is
          also true if the
      <a class="link" href="innodb-storage-engine.html" title="Chapter 17 The InnoDB Storage Engine">
       <code class="literal">
        InnoDB
       </code>
      </a>
      table is
          partitioned.)
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       AVG_ROW_LENGTH
      </code>
     </p>
     <p>
      The average row length.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       DATA_LENGTH
      </code>
     </p>
     <p>
      For
      <code class="literal">
       MyISAM
      </code>
      ,
      <code class="literal">
       DATA_LENGTH
      </code>
      is the length of the data file, in bytes.
     </p>
     <p>
      For
      <code class="literal">
       InnoDB
      </code>
      ,
      <code class="literal">
       DATA_LENGTH
      </code>
      is the approximate amount of space allocated for the clustered
          index, in bytes. Specifically, it is the clustered index size,
          in pages, multiplied by the
      <code class="literal">
       InnoDB
      </code>
      page
          size.
     </p>
     <p>
      Refer to the notes at the end of this section for information
          regarding other storage engines.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       MAX_DATA_LENGTH
      </code>
     </p>
     <p>
      For
      <code class="literal">
       MyISAM
      </code>
      ,
      <code class="literal">
       MAX_DATA_LENGTH
      </code>
      is maximum length of the
          data file. This is the total number of bytes of data that can
          be stored in the table, given the data pointer size used.
     </p>
     <p>
      Unused for
      <code class="literal">
       InnoDB
      </code>
      .
     </p>
     <p>
      Refer to the notes at the end of this section for information
          regarding other storage engines.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       INDEX_LENGTH
      </code>
     </p>
     <p>
      For
      <code class="literal">
       MyISAM
      </code>
      ,
      <code class="literal">
       INDEX_LENGTH
      </code>
      is the length of the index file, in bytes.
     </p>
     <p>
      For
      <code class="literal">
       InnoDB
      </code>
      ,
      <code class="literal">
       INDEX_LENGTH
      </code>
      is the approximate amount of space allocated for non-clustered
          indexes, in bytes. Specifically, it is the sum of
          non-clustered index sizes, in pages, multiplied by the
      <code class="literal">
       InnoDB
      </code>
      page size.
     </p>
     <p>
      Refer to the notes at the end of this section for information
          regarding other storage engines.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       DATA_FREE
      </code>
     </p>
     <p>
      The number of allocated but unused bytes.
     </p>
     <p>
      <code class="literal">
       InnoDB
      </code>
      tables report the free space of the
          tablespace to which the table belongs. For a table located in
          the shared tablespace, this is the free space of the shared
          tablespace. If you are using multiple tablespaces and the
          table has its own tablespace, the free space is for only that
          table. Free space means the number of bytes in completely free
          extents minus a safety margin. Even if free space displays as
          0, it may be possible to insert rows as long as new extents
          need not be allocated.
     </p>
     <p>
      For NDB Cluster,
      <code class="literal">
       DATA_FREE
      </code>
      shows the space
          allocated on disk for, but not used by, a Disk Data table or
          fragment on disk. (In-memory data resource usage is reported
          by the
      <code class="literal">
       DATA_LENGTH
      </code>
      column.)
     </p>
     <p>
      For partitioned tables, this value is only an estimate and may
          not be absolutely correct. A more accurate method of obtaining
          this information in such cases is to query the
      <code class="literal">
       INFORMATION_SCHEMA
      </code>
      <a class="link" href="information-schema-partitions-table.html" title="28.3.21 The INFORMATION_SCHEMA PARTITIONS Table">
       <code class="literal">
        PARTITIONS
       </code>
      </a>
      table, as shown in
          this example:
     </p>
     <div class="copytoclipboard-wrapper">
      <pre class="programlisting language-sql"><div class="docs-select-all right" id="sa77298905"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-sql"><span class="token keyword">SELECT</span> <span class="token function">SUM</span><span class="token punctuation">(</span>DATA_FREE<span class="token punctuation">)</span>
    <span class="token keyword">FROM</span>  INFORMATION_SCHEMA<span class="token punctuation">.</span><span class="token keyword">PARTITIONS</span>
    <span class="token keyword">WHERE</span> TABLE_SCHEMA <span class="token operator">=</span> <span class="token string">'mydb'</span>
    <span class="token operator">AND</span>   <span class="token keyword">TABLE_NAME</span>   <span class="token operator">=</span> <span class="token string">'mytable'</span><span class="token punctuation">;</span></code></pre>
     </div>
     <p>
      For more information, see
      <a class="xref" href="information-schema-partitions-table.html" title="28.3.21 The INFORMATION_SCHEMA PARTITIONS Table">
       Section 28.3.21, “The INFORMATION_SCHEMA PARTITIONS Table”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       AUTO_INCREMENT
      </code>
     </p>
     <p>
      The next
      <code class="literal">
       AUTO_INCREMENT
      </code>
      value.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       CREATE_TIME
      </code>
     </p>
     <p>
      When the table was created.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       UPDATE_TIME
      </code>
     </p>
     <p>
      When the table was last updated. For some storage engines,
          this value is
      <code class="literal">
       NULL
      </code>
      . Even with
      <a class="link" href="glossary.html#glos_file_per_table" title="file-per-table">
       file-per-table
      </a>
      mode
          with each
      <code class="literal">
       InnoDB
      </code>
      table in a separate
      <code class="literal">
       .ibd
      </code>
      file,
      <a class="link" href="glossary.html#glos_change_buffering" title="change buffering">
       change buffering
      </a>
      can delay the write to the data file, so the file modification
          time is different from the time of the last insert, update, or
          delete. For
      <code class="literal">
       MyISAM
      </code>
      , the data file timestamp
          is used; however, on Windows the timestamp is not updated by
          updates, so the value is inaccurate.
     </p>
     <p>
      <code class="literal">
       UPDATE_TIME
      </code>
      displays a timestamp value for
          the last
      <a class="link" href="update.html" title="15.2.17 UPDATE Statement">
       <code class="literal">
        UPDATE
       </code>
      </a>
      ,
      <a class="link" href="insert.html" title="15.2.7 INSERT Statement">
       <code class="literal">
        INSERT
       </code>
      </a>
      , or
      <a class="link" href="delete.html" title="15.2.2 DELETE Statement">
       <code class="literal">
        DELETE
       </code>
      </a>
      performed on
      <code class="literal">
       InnoDB
      </code>
      tables that are not partitioned. For
          MVCC, the timestamp value reflects the
      <a class="link" href="commit.html" title="15.3.1 START TRANSACTION, COMMIT, and ROLLBACK Statements">
       <code class="literal">
        COMMIT
       </code>
      </a>
      time, which is
          considered the last update time. Timestamps are not persisted
          when the server is restarted or when the table is evicted from
          the
      <code class="literal">
       InnoDB
      </code>
      data dictionary cache.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       CHECK_TIME
      </code>
     </p>
     <p>
      When the table was last checked. Not all storage engines
          update this time, in which case, the value is always
      <code class="literal">
       NULL
      </code>
      .
     </p>
     <p>
      For partitioned
      <a class="link" href="innodb-storage-engine.html" title="Chapter 17 The InnoDB Storage Engine">
       <code class="literal">
        InnoDB
       </code>
      </a>
      tables,
      <code class="literal">
       CHECK_TIME
      </code>
      is always
      <code class="literal">
       NULL
      </code>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       TABLE_COLLATION
      </code>
     </p>
     <p>
      The table default collation. The output does not explicitly
          list the table default character set, but the collation name
          begins with the character set name.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       CHECKSUM
      </code>
     </p>
     <p>
      The live checksum value, if any.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       CREATE_OPTIONS
      </code>
     </p>
     <p>
      Extra options used with
      <a class="link" href="create-table.html" title="15.1.20 CREATE TABLE Statement">
       <code class="literal">
        CREATE
          TABLE
       </code>
      </a>
      .
     </p>
     <p>
      <code class="literal">
       CREATE_OPTIONS
      </code>
      shows
      <code class="literal">
       partitioned
      </code>
      for a partitioned table.
     </p>
     <p>
      <code class="literal">
       CREATE_OPTIONS
      </code>
      shows the
      <code class="literal">
       ENCRYPTION
      </code>
      clause specified for tables
          created in file-per-table tablespaces. It shows the encryption
          clause for file-per-table tablespaces if the table is
          encrypted or if the specified encryption differs from the
          schema encryption. The encryption clause is not shown for
          tables created in general tablespaces. To identify encrypted
          file-per-table and general tablespaces, query the
      <a class="link" href="information-schema-innodb-tablespaces-table.html" title="28.4.24 The INFORMATION_SCHEMA INNODB_TABLESPACES Table">
       <code class="literal">
        INNODB_TABLESPACES
       </code>
      </a>
      <code class="literal">
       ENCRYPTION
      </code>
      column.
     </p>
     <p>
      When creating a table with
      <a class="link" href="glossary.html#glos_strict_mode" title="strict mode">
       strict mode
      </a>
      disabled,
          the storage engine's default row format is used if the
          specified row format is not supported. The actual row format
          of the table is reported in the
      <code class="literal">
       ROW_FORMAT
      </code>
      column.
      <code class="literal">
       CREATE_OPTIONS
      </code>
      shows the row format
          that was specified in the
      <a class="link" href="create-table.html" title="15.1.20 CREATE TABLE Statement">
       <code class="literal">
        CREATE
          TABLE
       </code>
      </a>
      statement.
     </p>
     <p>
      When altering the storage engine of a table, table options
          that are not applicable to the new storage engine are retained
          in the table definition to enable reverting the table with its
          previously defined options to the original storage engine, if
          necessary. The
      <code class="literal">
       CREATE_OPTIONS
      </code>
      column may
          show retained options.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       TABLE_COMMENT
      </code>
     </p>
     <p>
      The comment used when creating the table (or information as to
          why MySQL could not access the table information).
     </p>
    </li>
   </ul>
  </div>
  <h4>
   <a name="idm46045078331600">
   </a>
   Notes
  </h4>
  <div class="itemizedlist">
   <ul class="itemizedlist" style="list-style-type: disc; ">
    <li class="listitem">
     <p>
      For
      <a class="link" href="mysql-cluster.html" title="Chapter 25 MySQL NDB Cluster 8.4">
       <code class="literal">
        NDB
       </code>
      </a>
      tables, the output of
          this statement shows appropriate values for the
      <code class="literal">
       AVG_ROW_LENGTH
      </code>
      and
      <code class="literal">
       DATA_LENGTH
      </code>
      columns, with the exception
          that
      <a class="link" href="blob.html" title="13.3.4 The BLOB and TEXT Types">
       <code class="literal">
        BLOB
       </code>
      </a>
      columns are not taken
          into account.
     </p>
    </li>
    <li class="listitem">
     <p>
      For
      <a class="link" href="mysql-cluster.html" title="Chapter 25 MySQL NDB Cluster 8.4">
       <code class="literal">
        NDB
       </code>
      </a>
      tables,
      <code class="literal">
       DATA_LENGTH
      </code>
      includes data stored in main
          memory only; the
      <code class="literal">
       MAX_DATA_LENGTH
      </code>
      and
      <code class="literal">
       DATA_FREE
      </code>
      columns apply to Disk Data.
     </p>
    </li>
    <li class="listitem">
     <p>
      For NDB Cluster Disk Data tables,
      <code class="literal">
       MAX_DATA_LENGTH
      </code>
      shows the space allocated
          for the disk part of a Disk Data table or fragment. (In-memory
          data resource usage is reported by the
      <code class="literal">
       DATA_LENGTH
      </code>
      column.)
     </p>
    </li>
    <li class="listitem">
     <p>
      For
      <code class="literal">
       MEMORY
      </code>
      tables, the
      <code class="literal">
       DATA_LENGTH
      </code>
      ,
      <code class="literal">
       MAX_DATA_LENGTH
      </code>
      , and
      <code class="literal">
       INDEX_LENGTH
      </code>
      values approximate the actual
          amount of allocated memory. The allocation algorithm reserves
          memory in large amounts to reduce the number of allocation
          operations.
     </p>
    </li>
    <li class="listitem">
     <p>
      For views, most
      <a class="link" href="information-schema-tables-table.html" title="28.3.38 The INFORMATION_SCHEMA TABLES Table">
       <code class="literal">
        TABLES
       </code>
      </a>
      columns
          are 0 or
      <code class="literal">
       NULL
      </code>
      except that
      <code class="literal">
       TABLE_NAME
      </code>
      indicates the view name,
      <code class="literal">
       CREATE_TIME
      </code>
      indicates the creation time,
          and
      <code class="literal">
       TABLE_COMMENT
      </code>
      says
      <code class="literal">
       VIEW
      </code>
      .
     </p>
    </li>
   </ul>
  </div>
  <p>
   Table information is also available from the
   <a class="link" href="show-table-status.html" title="15.7.7.38 SHOW TABLE STATUS Statement">
    <code class="literal">
     SHOW TABLE STATUS
    </code>
   </a>
   and
   <a class="link" href="show-tables.html" title="15.7.7.39 SHOW TABLES Statement">
    <code class="literal">
     SHOW TABLES
    </code>
   </a>
   statements. See
   <a class="xref" href="show-table-status.html" title="15.7.7.38 SHOW TABLE STATUS Statement">
    Section 15.7.7.38, “SHOW TABLE STATUS Statement”
   </a>
   , and
   <a class="xref" href="show-tables.html" title="15.7.7.39 SHOW TABLES Statement">
    Section 15.7.7.39, “SHOW TABLES Statement”
   </a>
   . The following statements are
      equivalent:
  </p>
  <div class="copytoclipboard-wrapper">
   <pre class="programlisting language-sql"><div class="docs-select-all right" id="sa26401876"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-sql"><span class="token keyword">SELECT</span>
    <span class="token keyword">TABLE_NAME</span><span class="token punctuation">,</span> <span class="token keyword">ENGINE</span><span class="token punctuation">,</span> VERSION<span class="token punctuation">,</span> <span class="token keyword">ROW_FORMAT</span><span class="token punctuation">,</span> TABLE_ROWS<span class="token punctuation">,</span> <span class="token keyword">AVG_ROW_LENGTH</span><span class="token punctuation">,</span>
    DATA_LENGTH<span class="token punctuation">,</span> MAX_DATA_LENGTH<span class="token punctuation">,</span> INDEX_LENGTH<span class="token punctuation">,</span> DATA_FREE<span class="token punctuation">,</span> <span class="token keyword">AUTO_INCREMENT</span><span class="token punctuation">,</span>
    CREATE_TIME<span class="token punctuation">,</span> UPDATE_TIME<span class="token punctuation">,</span> CHECK_TIME<span class="token punctuation">,</span> TABLE_COLLATION<span class="token punctuation">,</span> <span class="token keyword">CHECKSUM</span><span class="token punctuation">,</span>
    CREATE_OPTIONS<span class="token punctuation">,</span> TABLE_COMMENT
  <span class="token keyword">FROM</span> INFORMATION_SCHEMA<span class="token punctuation">.</span><span class="token keyword">TABLES</span>
  <span class="token keyword">WHERE</span> table_schema <span class="token operator">=</span> <span class="token string">'<em class="replaceable">db_name</em>'</span>
  <span class="token punctuation">[</span><span class="token operator">AND</span> <span class="token keyword">table_name</span> <span class="token operator">LIKE</span> <span class="token string">'<em class="replaceable">wild</em>'</span><span class="token punctuation">]</span>

<span class="token keyword">SHOW</span> <span class="token keyword">TABLE</span> <span class="token keyword">STATUS</span>
  <span class="token keyword">FROM</span> <em class="replaceable">db_name</em>
  <span class="token punctuation">[</span><span class="token operator">LIKE</span> <span class="token string">'<em class="replaceable">wild</em>'</span><span class="token punctuation">]</span></code></pre>
  </div>
  <p>
   The following statements are equivalent:
  </p>
  <div class="copytoclipboard-wrapper">
   <pre class="programlisting language-sql"><div class="docs-select-all right" id="sa63784876"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-sql"><span class="token keyword">SELECT</span>
  <span class="token keyword">TABLE_NAME</span><span class="token punctuation">,</span> TABLE_TYPE
  <span class="token keyword">FROM</span> INFORMATION_SCHEMA<span class="token punctuation">.</span><span class="token keyword">TABLES</span>
  <span class="token keyword">WHERE</span> table_schema <span class="token operator">=</span> <span class="token string">'<em class="replaceable">db_name</em>'</span>
  <span class="token punctuation">[</span><span class="token operator">AND</span> <span class="token keyword">table_name</span> <span class="token operator">LIKE</span> <span class="token string">'<em class="replaceable">wild</em>'</span><span class="token punctuation">]</span>

<span class="token keyword">SHOW</span> <span class="token keyword">FULL</span> <span class="token keyword">TABLES</span>
  <span class="token keyword">FROM</span> <em class="replaceable">db_name</em>
  <span class="token punctuation">[</span><span class="token operator">LIKE</span> <span class="token string">'<em class="replaceable">wild</em>'</span><span class="token punctuation">]</span></code></pre>
  </div>
 </div>
 <br/>
</div>
