I feel like I just got back home from Oracle OpenWorld (check out my pictures) and some vacation, but I'll be on the road again next week to attend LinuxCon Europe in Barcelona. I'll be there from Monday (Nov. 5th) until Wednesday evening. Oracle is sponsoring the event and we'll have a booth at the exhibition area (booth #19), handing out free Oracle Linux and Oracle VM DVDs. I'll be at the booth every now and then and plan to give a short introduction and live demo of Ksplice rebootless updates on Monday evening (6:00pm).

Two …

This article is following the previously published investigation about I/O limitations on Linux and also sharing my data from the steps in investigation of MySQL/InnoDB I/O limitations within RW workloads..

So far, I've got in my hands a server with a Fusion-io card and I'm expecting now to analyze more in details the limits we're hitting within MySQL and InnoDB on heavy Read+Write workloads. As the I/O limit from the HW level should be way far due outstanding Fusion-io card performance, contentions within MySQL/InnoDB code should be much more better visible now (at least I'm expecting ;-))

But before to deploy on it any of MySQL test workloads, I want to understand the I/O limits I'm hitting on the lower levels (if any) - first on the card itself, and then on the filesystem levels..

NOTE …

I was digging through some old project code and found this script. Sometimes one finds oneself in an odd situation and needs to convert regular SQL, say from a MySQL database dump, into SQLite3 format. There’s not too much else to say, but here is a script that helps with the process. It can likely be improved but this handles the items that came up during conversion on initial runs.

#!/bin/sh
####
# NAME: convert-mysql-to-sqlite3.sh
# AUTHOR: Matt Reid
# DATE: 2011-03-22
# LICENSE: BSD
####
if [ "x$1" == "x" ]; then
   echo "Usage: $0 "
   exit 
fi 
cat $1 |
grep -v ' KEY "' |   
grep -v ' UNIQUE KEY "' |
grep -v ' PRIMARY KEY ' |
sed '/^SET/d' |          
sed 's/ unsigned / /g' | 
sed 's/ auto_increment/ primary key autoincrement/g' |
sed 's/ smallint([0-9]*) / integer /g' | 
sed 's/ tinyint([0-9]*) / integer /g' |  
sed 's/ int([0-9]*) / integer /g' |      
sed 's/ character set [^ ]* / /g' |      
sed 's/ enum([^)]*) / varchar(255) /g' | 
sed 's/ on …

Read the original article at 10 ways I avoid trouble in database operations

1. Avoid destructive commands From time to time I’m working with new recruits and bringing them up to speed in operations. The first thing I emphasize is care with destructive commands. What do I mean here? Well there are all sorts of them. SQL commands such as DROP table & DROP database. But also TRUNCATE [...]

For more articles like these go to Sean Hull's Scalable Startups

Related posts:

1. 5 Ways to Avoid EC2 Outages
2. 7 Ways to Troubleshoot MySQL
…

It's that time of the year again — the summer holidays are over and the conference season starts!

I'm very excited to be at Oracle Open World in San Francisco again, where I will pretty busy. On Saturday and Sunday I will attend MySQL Connect, primarily to man the Oracle Linux booth in the exhibition area. But I hope to catch some of the talks as well (I shared my favourite sessions with Keith Larson from the MySQL team in this interview). During Open World, I will help out manning the Oracle Linux demo pods in the exhibition grounds in Moscone South, where we will showcase Oracle Linux with Ksplice and related technologies. I also have a joint presentation with two of our …

Software patents have been an agent of change in open source over the last decade, as I explained in my keynote at the 8th International Conference on Open Source Systems this week. Most notably, the astonishing proliferation of software patents has forced technology companies to spend a lot of time and energy assembling defensive portfolios.

read more

After a long pause in the speaking game, I am back.

It's since April that I haven't been on stage, and it is now time to resume my public duties.

• I will speak at MySQL Connect in San Francisco, just at the start of Oracle Open World, with a talk on MySQL High Availability: Power and Usability. It is about the cool technology that is keeping me busy here at Continuent, which can make life really easy for DBAs. This talk will be a demo fest. If you are attending MySQL Connect, you should see it!
• A happy return for me. On October 27th I will talk about open source databases and the pleasures of command line operations at …

If you’ve ever been troubleshooting on the MySQL command line and needed to quickly see how much memory is being used then you’ve probably noticed that there are no built in commands to give you this data. Unlike other enterprise databases MySQL doesn’t have a very robust management system built in to help make the DBA’s life easier. It doesn’t come with built in Stored Procedures to report on usage statistics or generate handy reports; so we have to code them and import them to MySQL — no relying on Oracle to help us out here.

So, here’s a stored procedure that can be imported to MySQL and run whenever you need to see the memory usage statistics. Installation and usage info is built into the SP below. The SP can also be downloaded from the repo: https://bitbucket.org/themattreid/generic-sql-scripts/src/15c75632f1af/mysql-memory-report-storedproc.sql

##################################################################### …

As Patrik noted last week, MariaDB is taking a leading role in the trend of keeping the MySQL ecosystem an open one. The SkySQL and MariaDB teams work together closely on this, and we even travel together!

Join both SkySQL and MariaDB at this week’s LinuxCon North America conference in sunny San Diego to learn more about how MariaDB is directly communicating with users (including SkySQL enterprise customers) to not only identify and help fix issues with current releases of the MySQL database, but to also further enhance MariaDB to become even more technologically advanced.

read more

I don't know why SELinux problems seem so frustrating. The problem almost certainly is related to the fact that there is frequently no error message. This is exactly the problem I ran into while turning up a new Apache web server on Red Hat Enterprise Linux 6 (RHEL6) with SELinux enabled.