I am quite excited at the MySQL Labs feature to have a Binary log API .
The reason is that I see this as a possible disk-based queuing system for MySQL.

An example of how you could do this, is instead of having a trigger with its own overhead, you could create a program to parse the binary log and run a trigger yourself a little bit later with no "real-time" overhead. As in, it would be run when the user isn't waiting for it.
You could also, for another example, develop a program that counts the rows in a table and update memcached directly, instead of querying MySQL for it.
This can already be done with other queuing systems like Gearman, but with this API, you can develop other APIs or applications on top of it. Like, memcache_table_counter demon.

In any case, it would be very …

Thank you. Great news.

Although I no longer maintain hackmysql.com, I still actively develop MySQL tools. An article I wrote, 10 essential MySQL tools for admin, was published today. I hope no one’s feelings are hurt if their tool isn’t in the list, but it was rather difficult to compile the list given that so many tools are either not actively developed, not tested, or not well documented. Given lag time between writing and publishing, I was not able to write about Yoshinori’s MHA or newer tools. And given length constraints, I was not able to write about more tools. In any case, the world of MySQL tools is alive and well.

Last week was a banner week for MySQL at OSCON. We had many MySQL developers meeting with the MySQL community, conducting technical sessions, leading BOF sessions, working the exhibit hall, and confirming Oracle's leadership in the technical evolution of MySQL.  The highlight of the week was the unveiling of even more 5.6 early access InnoDB and Replication features that are now available for early adopters to download, evaluate and shape via labs.mysql.com.  

InnoDB is one of MySQL's "crown jewels" and beginning in 5.5 is now the default storage engine.  The following 5.6 feature improvements are in direct response to community and customer feedback and requests.  The new 5.6 early access features include:

• Full-text search
  
• REDO log files max size extended to 2 TB
• UNDO logs on their own tablespace …

There are 2 kind of upgrade is possible in MySQL.     Major version upgrade (i.e MySQL 4.1 to MySQL 5.0)     Minor version upgrade (i.e MySQL 5.0.45 to MySQL 5.0.47) In the Major version upgrade, people are generally using very common technique which is, taking backup by mysqldump from MySQL 4.1 and reload into MySQL [...]

At OSCON 2011 last week, Oracle delivered more early access (labs) features for MySQL 5.6 replication. These features are focused on better integration, performance and data integrity:

- The Binlog API: empowering the community to seamlessly integrate MySQL with other applications and data stores;

- Binlog Group Commit and Enhanced Multi-Threaded Slaves: continuing to deliver major improvements to replication performance;

- Durable Slave Reads: further enhancing data integrity.

These new features build on the significant replication enhancements announced as part of the MySQL 5.6.2 Development Milestone Release back in April.

We are always listening to our customers and community. And, based on their needs and input, the MySQL engineering team continues to take …

PART 1 – This will be a multi part post.

THIS DOCUMENT IS BEING UPDATED – PLEASE WATCH FOR CHANGES!

After years of supporting MySQL, for many different companies, I’ve seen this story played out again and again.
The company:

• chooses a Database Management System (MySQL)
• installs the DBMS on a computer with other processes
• writes many programs to access the data (Without concern on how the queries are written.)
• moves DBMS to a computer of its own and writes more programs
• buy bigger computer to run the DBMS and writes more programs
• tires of DBMS response times and outages caused by developers working on production systems and hires a Database Administrator to fix the mess

This is a step by step description of  how I build a highly available, production MySQL servers. Like most things it life, these problems …

In life there are really two major types of data analytics.  Firstly, we don’t know what we want to know – so we need analytics to tell us what is interesting.  This is broadly called discovery.  Secondly, we already know what we want to know – we just need analytics to tell us this information, often repeatedly and as quickly as possible.  This is called anything from reporting or dashboarding through more general data transformation and so on.

Typically we are using the same techniques to achieve this.  We shove lots of data into a repository of some from (SQL, MPP SQL, NoSQL, HDFS etc) then run queries/ jobs/ processes across that data to retrieve the information we care about.  

Now this makes sense for data discovery.  If we don’t know what we want to know, having lots of data in a big pile that we can slice and dice in interesting ways is good.   But when we already know what …

Keith Larson (Oracle’s MySQL Community Manager) nominated me to become an Oracle ACE. Thank you Oracle – it feels very good to receive this award.

Call or SKYPE us in New York City: +1-212-533-6828

MySQL in the Cloud

• Deploying MySQL in the Cloud
• Cloud Security considerations for databases
• Deploying in multiple Availability Zones
• Deploying in multiple regions
• Deploying MySQL with multi-az
• Horizontal scalability in the cloud
• MySQL spinup scripts
• Deploying Amazon RDS
• Evaluating RDS
• Evaluating MySQL in the cloud
• EBS Performance considerations
• Tuning MySQL parameters in the cloud
• Backup types & options
• Mitigating against cloud server failure
• Vertical scalability & MySQL on EC2

MySQL Consulting and Services

• Backup & recovery
• MySQL master master replication
• MySQL replication & horizontal scaling
• MySQL …