Jeff wrote:
> True, is there a way to tell a slave to not replicate certain queries
> like alter table or would I need to get creative and stop replication
> and all writes to the main database, then issue the alter table
> statement, then restart replication with a set global
> slave_sql_skip_counter=1 so that it skips the alter statemtent?
There's a much easier way - issue the statement "SET SQL_LOG_BIN = 0;"
before issuing any ALTER TABLE statements. This will cause all
statements for the duration of that session to not be written to the
binlog. See http://dev.mysql.com/doc/mysql/en/set-option.html for more
information.
You may want to look at a few pages in the docs, for information about
InnoDB / MyISAM differences. If your code relies on one table type (or
features only available with that table type, like transactions for
InnoDB or "SELECT COUNT(*)" for MyISAM), you may run into some problems.
Here are a couple links to try to help.
http://dev.mysql.com/doc/mysql/en/innodb-and-mysql-replication.html
http://dev.mysql.com/doc/mysql/en/converting-tables-to-innodb.html
http://dev.mysql.com/doc/mysql/en/innodb-auto-increment-column.html
http://dev.mysql.com/doc/mysql/en/replication-features.html (towards the
bottom it talks about replication of transactions and MyISAM engine)
Best Regards,
Devananda vdv
