MySQL Replication is incredibly simple to get up and running and this (short) post steps you through it.

Simple Master -> Slave Replication

MySQL allows you to build up complex replication hierarchies, such as multi-master, chains of read slaves, backup databases at a remote site or any combination of these. This post focuses on a simple single master to single slave topology – the more complex solutions are built from this basic building block.

This post also makes the assumption that the 2 MySQL Servers have been installed but that there is no existing data in the master that needs to be copied to the slave – it’s not complex to add that extra requirement and it will be covered in a future post.

Server “black” (192.168.0.31) is to be our master and “blue” (192.168.0.34) the slave.

I know that MERGE isn’t everyone’s favourite storage engine but we use them quite extensively and ran into a problem the other day that I thought I’d share.

A common usage pattern is to CREATE TEMPORARY TABLE LIKE an existing MyISAM table and then ALTER TABLE to turn it into a MERGE table and specify it’s UNION. Like this:

CREATE TABLE tmpMerge LIKE a;
ALTER TABLE tmpMerge ENGINE=MERGE, UNION=(a,b);

It’s a pattern we’ve been using for ages and seems to work well in most cases.

In one application we keep aggregated data in daily tables (inspired by this article). Within the application we work out which of the daily tables we need and build them into a temporary merge table before querying it. There’s more to it than that (there’s a pyramid of …

My colleague Aleksandr Kuzminsky will be speaking at WebConf Riga 2010 next month on XtraBackup: Hot Backups and More and Recovery of Lost or Corrupted InnoDB Tables.

WebConf is the first big conference of its kind in the Baltic states (Estonia, Latvia, Lithuania) and we are very happy to be participating.

In addition to Aleksandr's talks, we will also be offering our training courses. You can find out more from the conference website (they will be publishing more information in the next two days).

Entry posted by Morgan Tocker | No comment

Add to: …

As I previously noted, I’m in the midst of converting some data (roughly 2 billion records) into documents that will live in a MongoDB cluster. And any time you move data into a new data store, you have to be mindful of any limitations or bottlenecks you might encounter (since all systems have had to make compromises of some sort or another).

In MySQL one of the biggest compromises we make is deciding what indexes really need to be created. It’s great to have data all indexed when you’re searching it, but not so great when you’re adding and deleting many rows.

In MongoDB, the thing that gets me is the document size limit. Currently an object stored in MongoDB cannot be larger than 4MB (though that’s likely to be raised soon). Now, you can build your own MongoDB binaries and tweak that parameter, but I’ve been …

There are more sites out there that have their backends running MariaDB. In fact, as we work to get it recommended alongside its upstream provider, it seemed time to have “Powered by MariaDB” logos. Check out the badges that Daniel created. Feel free to copy the images or hotlink them from the server.

As an aside, would any readers be interested in purchasing t-shirts or other MariaDB merchandise? What merchandise should we make, besides just stickers?

The Drizzle Beta was announced last week. It took me the better part of an hour to download and install Drizzle, mainly apt-geting packages not on the fresh install of Ubuntu I was using. Be sure to read the Drizzle Wiki on how to start Drizzle after building.

Anyone who has built MySQL or Postgres from source can build Drizzle. Anyone who has not done so needs to pay attention to the output of the make command and read through the documentation.

The default storage engine is the InnoDB plugin. The client program (pictured) will look familiar to MySQL-ers. Drizzle worked as expected on the simple tasks it perform. And now that I have …

We've just announced a new support offering for MySQL. There's a press release here, and product information page here. But what does this new service really mean for you, in practical terms? This is actually important -- it will open up a range of new choices for you. I'll explain two major points that matter to you.

Before I begin, I want to make it clear that in some ways, what we're offering is something we've always offered. That is actually why it took us a while to re-align the product a bit. We thought we were serving you fully. You told us that wasn't really true. Thank you. We've listened.

1. Sensible Pricing

We've always offered pay-as-you-go support, and we've had a dedicated support staff for a while. The missing ingredient was flat-rate pricing. Big …

I have my schedule pretty busy during a trip to Russia this year. In addition to giving a master class and Sphinx Conference I'm going to speak at HighLoad++. I'll also have a user meeting presentations in Samara on October 17 and Minsk on October 22 This looks like it is going to be a lot of fun …

Microsoft sues Motorola. Oracle says no to LibreOffice. Time to fork Java? And more.

Follow 451 CAOS Links live @caostheory on Twitter and Identi.ca, and daily at Paper.li/caostheory
“Tracking the open source news wires, so you don’t have to.”

# Microsoft is suing Motorola over alleged Android patent infringements.

# Oracle confirmed to SJVN that it will not be working with the Document Foundation on LibreOffice.

# Sean Michael Kerner reported that Red Hat has settled an alleged patent infringement case with IP firm Acacia Research.

# Greg Luck …

Often we make some sketches of the database we plan to create on a blackboard or a sheet of paper before we actually design its structure on computer. After that we discuss the entities we’ve got, normalize them and repeat these actions several times. As a result we get a completely approved database structure in the form of an image file in the project documentation.

Question:
How to create a database diagram basing on the image available?

Let’s try to do this using Database Designer of dbForge Studio for MySQL.

Let us suppose that you have a sketch of the future database:

Database Structure

To place this picture onto an empty diagram you should create an empty document, for …