Category: maxdb

  • Synchronization Manager: MySQL as replication destination

    Earlier this week, I wrote about the Synchronization Manager and gave a step-by-step tutorial on getting an initial scenario implemented. In this article, I’ll expand on the previous tutorial by introducing the concept of uni-directional synchronization. Uni-directional participants act as destinations for replicated data. These participants are sometimes called “slaves,” because they are not capable […]

  • Creating a Synchronization Management Scenario

    This is a follow-up to my earlier article on the MaxDB Synchronization Manager. In the months since my prior article, the Synchronization Manager has proved itself production ready and capable of replicating real-world databases in demanding scenarios. Take the following as theoretical and emperical examples of such scenarios (not necessarily in that order): i) For […]

  • On vacation

    So. I’m on vacation. But I’m thinking a bit about work-related stuff, like Raimi’s MySQL-related blog entries: In case any of you out there read German. I know enough to figure out that he’s got a link to me in it :) Mark Thomas has created a blog as well.

  • Planet MaxDB, MaxDB Project

    Well, I set up an aggregator for folks who blog about MaxDB. If you are one of these folks, please email anybody who is aggregated at Planet MaxDB, or join us on #maxdb on I am using the monologue code to aggregate the blog feeds, and while I was altering the default template, I […]

  • Customer’s experience with Sync Manager

    14:34 < MThomas> Time to install and configure Sync Manager in development environment: 4 days, one of which was 15 hours long. Time to install and configure in production: 30 minutes. I’ve written a bit of documentation that might help you get things running in the same way: Create a Synchronization Scenario