Replication Features and Issues • character_set_client • character_set_connection • character_set_database • character_set_server • collation_connection • collation_database • collation_server • foreign_key_checks • identity • last_insert_id • lc_time_names • pseudo_thread_id • sql_auto_is_null • time_zone • timestamp • unique_checks When  MIXED  mode is used, the variables in the preceding list, when used with session scope, cause a switch from statement-based to row-based logging. See Section 5.4.4.3, “Mixed Binary Logging Format” . sql_mode  is also replicated except for the  NO_DIR_IN_CREATE  mode; the replica always preserves its own value for  NO_DIR_IN_CREATE , regardless of changes to it on the source. This is true for all replication formats. However, when  mysqlbinlog  parses a  SET @@sql_mode =  mode  statement, the full  mode  value, including  NO_DIR_IN_CREATE , is passed to the receiving server. For this reason, replication of such a statement may not be safe when  STATEMENT  mode is in use. The  default_storage_engine  system variable is not replicated, regardless of the logging mode; this is intended to facilitate replication between different storage engines. The  read_only  system variable is not replicated. In addition, the enabling this variable has different effects with regard to temporary tables, table locking, and the  SET PASSWORD  statement in different MySQL versions. The  max_heap_table_size  system variable is not replicated. Increasing the value of this variable on the source without doing so on the replica can lead eventually to  Table is full  errors on the replica when trying to execute  INSERT  statements on a  MEMORY  table on the source that is thus permitted to grow larger than its counterpart on the replica. For more information, see Section 17.5.1.21, “Replication and MEMORY Tables” . In statement-based replication, session variables are not replicated properly when used in statements that update tables. For example, the following sequence of statements does not insert the same data on the source and the replica: SET max_join_size=1000; INSERT INTO mytable VALUES(@@max_join_size); 3680