<div id="docs-body">
 <div class="section">
  <div class="titlepage">
   <div>
    <div>
     <h2 class="title">
      <a name="optimizing-database-structure">
      </a>
      10.4 Optimizing Database Structure
     </h2>
    </div>
   </div>
  </div>
  <div class="toc">
   <dl class="toc">
    <dt>
     <span class="section">
      <a href="data-size.html">
       10.4.1 Optimizing Data Size
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="optimize-data-types.html">
       10.4.2 Optimizing MySQL Data Types
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="optimize-multi-tables.html">
       10.4.3 Optimizing for Many Tables
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="internal-temporary-tables.html">
       10.4.4 Internal Temporary Table Use in MySQL
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="database-count-limit.html">
       10.4.5 Limits on Number of Databases and Tables
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="table-size-limit.html">
       10.4.6 Limits on Table Size
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="column-count-limit.html">
       10.4.7 Limits on Table Column Count and Row Size
      </a>
     </span>
    </dt>
   </dl>
  </div>
  <p>
   In your role as a database designer, look for the most efficient
      way to organize your schemas, tables, and columns. As when tuning
      application code, you minimize I/O, keep related items together,
      and plan ahead so that performance stays high as the data volume
      increases. Starting with an efficient database design makes it
      easier for team members to write high-performing application code,
      and makes the database likely to endure as applications evolve and
      are rewritten.
  </p>
 </div>
 <br/>
</div>
