This week we continue our series on MySQL Utilities, talking about replication and failover tools. Ear Candy is a gotcha with poor GRANT syntax that MySQL does not give warnings about, and At the Movies is an open forum from the SkySQL Solutions Day a few months ago.
Part 1 of MySQL
Utilities
Part 2 of MySQL
Utilities
Part 4 of MySQL
Utilities
Part 5 of MySQL
Utilities
MySQL Utilities part 3
mysqlfailover
Most "SQL And Its Sequels" blog posts will be from me, Peter
Gulutzan, formerly Software Architect for MySQL then Sun then
Oracle. Most posts will be about MySQL / MariaDB and SQL
standards -- my expertises. But I learned about other products
during my recent stint at HP, and I like to look at other
open-source DBMSs as well.
The RSS feed is http://ocelot.ca/blog/feed/ and posts will occur
once or twice a week.
Copyright (c) 2013 by Ocelot Computer Services Inc. All rights reserved.
With organizations gearing up to the new round of technologies as the database vendors announce newer versions and features, the bloggers are busy covering all of those details with practical advice. This Log Buffer Edition brings you that advice.
Oracle:
Marco Vigelini has written one post regarding creation of a pluggable database PDB using the files of the seed PDB$SEED and his second post describes how to create a pluggable database by unplugging an existing PDB and plugging it into another container.
…
[Read more]The Sept. 8 deadline is looming to submit your speaker proposals for Percona Live London 2013′s conference breakout sessions and tutorial sessions.
In addition to fame (and dare I say fortune?), if selected as a speaker by our amazing conference committee, you’ll receive a complimentary, full-conference pass.
Some call for papers pointers:
A couple of weeks before I joined Oracle, I was working as a freelance consultant. One of my customers decided to migrate from PostgreSQL to MySQL.
The backstory:
My client initially decided to build their application with PostgreSQL, with the founding team already very experienced with MySQL. Their primary reason: schema changes on live MySQL deployments were difficult.
MySQL 5.6 introduced online DDL, addressing a large number of their issues.
As they experienced significant traction in their private beta, they decided to switch to MySQL 5.6, where they had more comfort in the size of the support & consulting ecosystem behind it.
I should point out in advance that I think …
[Read more]This post is a continuation of my research of TokuDB’s storage engine to understand if it is suitable for timeseries workloads.
While inserting LOAD DATA INFILE into an empty table shows great results for TokuDB, what’s more interesting is seeing some realistic workloads.
So this time let’s take a look at the INSERT benchmark.
What I am going to do is to insert data in 16 parallel threads into the table from the previous post:
CREATE TABLE `sensordata` ( `ts` int(10) unsigned NOT NULL DEFAULT '0', `sensor_id` int(10) unsigned NOT NULL, `data1` double NOT NULL, `data2` double NOT NULL, `data3` double NOT NULL, `data4` double NOT NULL, `data5` double NOT …[Read more]
We’ve been hard at work on TokuMX since it’s initial release just over 2 months ago. Today we released TokuMX v1.2 which includes Hot Backup in the Enterprise Edition.
Hot Backup allows users to create a backup of a running TokuMX primary or secondary server in a replica set, with no blocking of writes for clients. We will be blogging more about the Hot Backup technology in the coming weeks. This same technology is used for Hot Backup in TokuDB.
Also worth noting are the features we’ve added since the initial TokuMX release:
Measuring how well a MySQL is doing can be tough – most metrics are simply proxies for actual performance. Thankfully, the Percona build of MySQL allows you to see exactly how long your queries are taking. It provides a diagnostic view that shows how long queries take, allowing you to gauge its real-world performance. I’ll get to that in a little bit. Before we do that, I want to talk about some other tools you can use.
You can dump the status of the system by running “show global status;”. This will give you how many connections have aborted, rows written, and how long the server has been up. This is historical info that’s erased when you flush it or when the server restarts (planned or unplanned). By sampling at regular intervals, you can also build monitoring scripts that measure changes over time …
[Read more]MySQL 5.6 has a great many new features, including, but certainly not limited to a number of performance improvements. However, besides the widely talked-about features such as InnoDB support for full text search, optimizer, performance schema improvements and …
[Read more]
