Showing entries 31 to 40 of 105
« 10 Newer Entries | 10 Older Entries »
Displaying posts with tag: Commentary (reset)
My List of MySQL Websites

I ask Sheeri of the OurSQL podcast to publish her list of MySQL websites and podcasts she follows. I thought it was only fair I do the same.  If you don’t watch these all the time your missing out. I read most of these every week.

If I missed one please leave a comment.

Planet MySQL –  - This is the big community list of MySQL info.  Not all my list is found here.
OurMySQL - – This a THE podcast for MySQL.  New shows each week.
Sergey Petrunia’s blog –
clever elephant –

[Read more]
The Full Monty- Part 3

This is more boring parts but you must lay a good foundation.

MySQL Setup:

All the resources must be in place before you configure Pacemaker. The default location for MySQL data is /var/lib/mysql.  You will be moving this to the DRBD file system in /data/mysql.   The default MySQL configuration is in /etc/my.cnf.  I move it to /data/mysql so updates will move with system fail overs.   To keep life simple I use sym-links to point from /var/lib/mysql and /etc/my.cnf to their new locations.
Install MySQL of your choise on DB1, DB2 and DB3.

# rpm -Uhv
# yum -y install Percona-Server-server-51.x86_64 Percona-Server-client-51.x86_64 \
 Percona-Server-shared-51.x86_64 xtrabackup.x86_64
# service mysql start
[Read more]
Oracle commercializes MySQL, sun rises in east

I’ve never objected to someone making money from MySQL. I’ve only expressed disappointment that they weren’t doing it effectively enough. As I have predicted many times, Oracle is good at this. Oracle is the number one reason I didn’t start a new career in some other database a few years ago. Oracle is making MySQL more successful not only for Oracle, but also for the users, the community, and the competition.

I am glad that Oracle is offering more pay-only extensions to the server in a way that creates opportunities for others to do the same, and I look forward to even more of them in the future.

Further Reading:

[Read more]
The Full Monty- Part 2

Installing DRDB in CentOS 5.6.

In Part 1 I when through the process of preparing a number of CentOS 5.6 servers. Now make the services they’ll preform more stable.

High Availability (HA)

I’ll be presenting two ways to provide redundant data and high available services. First, Pacemaker – with DRDB will duplicate your data at the disk partition level and watch for failures. Should the hardware failure, Pacemaker will take all the needed steps to start MySQL on the Hot Stand By (HSB). This is not perfect. Should someone run ‘rm *’ or drop a database DRDB will duplicate the loss on the HSB.

In another part, I’ll use …

[Read more]
Measuring open-source success by jobs

It’s notoriously hard to measure the usage of open-source software. Software that’s open-source or free can be redistributed far and wide, so the original creators have no idea how many times it’s installed, deployed, or distributed. As a proxy, we often use downloads, but that’s woefully inadequate.

I’ve recently begun trying to figure out how many job openings are mentioning various open-source projects. I think that this might be a better metric because it’s driven by the end result (usage), rather than intermediate processes (downloads, etc). I think that it’s likely that usage and demand for skilled people is somewhat realistically related.

To be more concrete, I’ve been watching RSS feeds from job posting aggregators for several alternative versions of MySQL: Percona Server, MariaDB, and Drizzle. It appears that Percona Server is by far the most in-demand in terms of job skills. (I haven’t seen a job posting …

[Read more]
Oracle is not screwing MySQL

People keep asking me “what is going to happen to MySQL now that Oracle has screwed MySQL?” I bluntly disagree that any such thing has happened. This blog post is just my personal view and does not reflect my employer’s opinion, but Oracle might have saved MySQL from what I can see. There is no evidence that supports the hysterical doomsday theories. (Witness MySQL 5.5, probably the best MySQL release in history. Not exactly what I’d call “screwing.”)

I believe that a product with such a large, diverse, and important market presence needs a variety of companies involved with it in many different ways. One of the absolutely key things is a company to make money from it. MySQL needs Oracle, because no one else involved is both capable and trying to make MySQL, the product, a large-scale commercial success. It looks like Oracle is doing what I wish Sun could have done.

Now, is Oracle going to be community friendly, …

[Read more]
A Complete List of MySQL Storage Engines

Opps… What happens when you press the post button instead of the preview button.  You publish a story before it’s time.

I’m working on compiling a complete list of MySQL storage engines. I didn’t intend to publish this so soon.  Maybe you can tell me what I’m missing.

Here is what I’ve found so far.  This is mostly an update of an older work I found.  Now that it’s posted I work hard to complete it.

Provider Engine State Platforms License Release Features
Toru Maesaka BlitzDB SE
[Read more]
Big Data is how big exactly?

I see that “Big Data” has become the new buzzword with a spike of hype around it. Everyone’s jumping on it. Companies are eager to promote their products as “Big Data,” just as they were eager to be associated with Web 2.0, Service-Oriented Architectures, and all the rest. Predictably, there’s basically zero agreement on what it means.

I’ve seen “Big Data” mentioned in the context of 1TB, which I think is rather moderate sized. But worse yet, I’ve seen 100GB labeled Big Data. I’ve even seen 5GB labeled Big Data. No links — I don’t want to draw attention to them.

I don’t know what Big Data is, but the stick-of-gum-sized flash drive in my pocket holds 16GB. It’s pretty Small. I mean, I forget it’s even there — it’s definitely not Big. I don’t know where I’d draw the line, but if it fits in a commodity server’s memory, which 100GB can do easily these days, it’s not Big Data. I don’t even …

[Read more]
Update to

For a long time I though the AutoMySQLBackup project had died.  Then, after I created many updates, in November of last year I saw some life. Meanwhile, I have continued to update the code and track what people have requested.   Low volume project are sometimes hard to keep alive. People think the project is dead and don’t want to use code that will not see updates.  Then if you make updates the authors may not come alive often enough to make the changes.

I have updated AutoMySQLBackup again. This time I have included the ability to make backups at the table level by including the table name, with the database name, in the list of databases to be backed up.  Adding a ‘.’ between the database name and the table name (data.table) will backup only that table in the database.  (IE DBNAME=”mysql test database.table”)

[Read more]
It’s about Time.


This post started with a simple question: “Does the function NOW() get executed every time a row is examined?” According to the manual,  “Functions that return the current date or time each are evaluated only once per query …. multiple references to a function such as NOW() … produce the same result. …. (However,) as of MySQL 5.0.12, SYSDATE() returns the time (the row is) executes. “

  • CURDATE() returns the current date.
  • CURTIME() returns the current time.
  • UTC_DATE() returns the current UTC date.
  • UTC_TIME() returns the current UTC time.
  • NOW() return the current date and time.
  • UTC_TIMESTAMP() returns the current UTC date and time.
  • SYSDATE() returns the date and …
[Read more]
Showing entries 31 to 40 of 105
« 10 Newer Entries | 10 Older Entries »