DBA

You are currently browsing the archive for the DBA category.

The MySQL 5.0 Archive Storage Engine

2010-03-12 in DBA, Data Warehouse, MySQL by face | No comments

DBAs facing the problem of corporate data explosion have an excellent new tool to help them in the MySQL 5.0 Archive storage engine. Whether it’s a data warehousing, data archiving, or data auditing situation, MySQL Archive tables can be just what the doctor ordered when it comes to maintaining large amounts of standard or sensitive information, while keeping storage costs at a bare-bones minimum.

via MySQL :: The MySQL 5.0 Archive Storage Engine.

Should probably investigate using ARCHIVE storage for the multi-year history tables

MySQL replication recovery

2010-02-27 in DBA, MySQL, Replication by face | No comments

MySQL replication can stop if slave fails to execute SQL statement from the binary log. From that moment, slave prints last error and waits for replication recovery. If master has consistent snapshot, then is only necessary to re-point slave to the new master position. It can be done with change master to or sql_slave_skip_counter.

via MySQL replication recovery.

Applying binary logs without adding to the binary log

2010-02-26 in DBA, MySQL by face | No comments

However, sometimes you want to apply binary logs to a MySQL instance, without having those changes applied to the binary logs themselves. One option is to restart the server binary logging disabled, and after the load is finished, restart the server with binary logging re-enabled. This is not always possible nor desirable, so there’s a better way, that works in at least versions 4.1 and up

via Applying binary logs without adding to the binary log | The Pythian Blog.

SET SESSION sql_log_bin=0;

MySQL Slave Errors?

2007-07-13 in DBA, MySQL, Replication by face | No comments

When you do a SHOW SLAVE STATUS\G and you see errors you need to resolve them. One way is to simply skip the offending statement.

SLAVE STOP;
SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1;
SLAVE START;

Repeat as desired.

SET GLOBAL SQL_SLAVE_SKIP_COUNTER documentation