<div id="docs-body">
 <div class="section">
  <div class="titlepage">
   <div>
    <div>
     <h4 class="title">
      <a name="replication-features-sql-mode">
      </a>
      19.5.1.30 Replication and Server SQL Mode
     </h4>
    </div>
   </div>
  </div>
  <a class="indexterm" name="idm46045135139344">
  </a>
  <a class="indexterm" name="idm46045135137856">
  </a>
  <a class="indexterm" name="idm46045135136368">
  </a>
  <a class="indexterm" name="idm46045135134880">
  </a>
  <a class="indexterm" name="idm46045135133392">
  </a>
  <a class="indexterm" name="idm46045135131904">
  </a>
  <p>
   Using different server SQL mode settings on the source and the
        replica may cause the same
   <a class="link" href="insert.html" title="15.2.7 INSERT Statement">
    <code class="literal">
     INSERT
    </code>
   </a>
   statements to be handled differently on the source and the
        replica, leading the source and replica to diverge. For best
        results, you should always use the same server SQL mode on the
        source and on the replica. This advice applies whether you are
        using statement-based or row-based replication.
  </p>
  <p>
   If you are replicating partitioned tables, using different SQL
        modes on the source and the replica is likely to cause issues.
        At a minimum, this is likely to cause the distribution of data
        among partitions to be different in the source's and replica's
        copies of a given table. It may also cause inserts into
        partitioned tables that succeed on the source to fail on the
        replica.
  </p>
  <p>
   For more information, see
   <a class="xref" href="sql-mode.html" title="7.1.11 Server SQL Modes">
    Section 7.1.11, “Server SQL Modes”
   </a>
   .
  </p>
 </div>
 <br/>
</div>
