Not very subtle title?

But look at databases, and applications using databases...
You've got your databases, tables and columns. Exciting? Or yawn...

Think of data, not by columns and type, but rather how it lives.

- Some data participates in "business logic" — what to show, how to show, related to other tables, etc.
- Some data changes often, some is literally static
- Some data needs to remain static, try Sarbanes-Oxley?, or J-SOX the Japanese counterpart
- Some data is small, but some is large (music, movies, pics)
- Some tables need to be transactional, some you couldn't care less

So, what — just cram it all in a database...?

Consider this — for each of the examples above, there is a penalty you pay, either in storage or performance for your choice.

What if you …

Not very subtle title?

But look at databases, and applications using databases...
You've got your databases, tables and columns. Exciting? Or yawn...

Think of data, not by columns and type, but rather how it lives.

- Some data participates in "business logic" — what to show, how to show, related to other tables, etc.
- Some data changes often, some is literally static
- Some data needs to remain static, try Sarbanes-Oxley?, or J-SOX the Japanese counterpart
- Some data is small, but some is large (music, movies, pics)
- Some tables need to be transactional, some you couldn't care less

So, what — just cram it all in a database...?

Consider this — for each of the examples above, there is a penalty you pay, either in storage or performance for your choice.

What if you …

Not very subtle title?

But look at databases, and applications using databases...
You've got your databases, tables and columns. Exciting? Or yawn...

Think of data, not by columns and type, but rather how it lives.

- Some data participates in "business logic" — what to show, how to show, related to other tables, etc.
- Some data changes often, some is literally static
- Some data needs to remain static, try Sarbanes-Oxley?, or J-SOX the Japanese counterpart
- Some data is small, but some is large (music, movies, pics)
- Some tables need to be transactional, some you couldn't care less

So, what — just cram it all in a database...?

Consider this — for each of the examples above, there is a penalty you pay, either in storage or performance for your …

MySQL — or, as I was frequently instructed, you spell it My-Ess-Que-Ell?...

Something everybody learns when starting at MySQL — though few as forcefully as I learned, when staying my first few weeks with Monty.

Ok, so I'm no spring chick anymore... it took me two weeks to learn the mantra, and now I have been assimilated.
But, look at it from the lighter perspective — if that was the hardest part — then the rest is really easy.

If you can handle more Monty stories, check out the interview:
http://dev.mysql.com/tech-resources/interviews/taneli-otala-mysql.html

But, what I really want to write about in this blog is about databases, or data management — future trends, how to make some entirely new and efficient applicatiions …

MySQL — or, as I was frequently instructed, you spell it My-Ess-Que-Ell?...

Something everybody learns when starting at MySQL — though few as forcefully as I learned, when staying my first few weeks with Monty.

Ok, so I'm no spring chick anymore... it took me two weeks to learn the mantra, and now I have been assimilated.
But, look at it from the lighter perspective — if that was the hardest part — then the rest is really easy.

If you can handle more Monty stories, check out the interview:
http://dev.mysql.com/tech-resources/interviews/taneli-otala-mysql.html

But, what I really want to write about in this blog is about databases, or data management — future trends, how to make some entirely new and efficient applicatiions without changing too much. It's all about …

MySQL — or, as I was frequently instructed, you spell it My-Ess-Que-Ell?...

Something everybody learns when starting at MySQL — though few as forcefully as I learned, when staying my first few weeks with Monty.

Ok, so I'm no spring chick anymore... it took me two weeks to learn the mantra, and now I have been assimilated.
But, look at it from the lighter perspective — if that was the hardest part — then the rest is really easy.

If you can handle more Monty stories, check out the interview:
http://dev.mysql.com/tech-resources/interviews/taneli-otala-mysql.html

But, what I really want to write about in this blog is about databases, or data management — future trends, how to make some entirely new and efficient applicatiions without changing too much. It's all about …

Greg Stein, chair of the Apache Software Foundation, and an employee at Google, working on open source projects, gave a very informative and compelling talk this morning comparing the various open source (and commercial) licensing schemes and the development model of both the Apache Foundation and the Eclipse Foundation.

Some of the main points of Greg's talk were that:

• The Apache Foundation manages a community, not code.
• The trend towards commoditization in the software industry will push most software licenses towards non-copyleft licenses (more in a later post)
• A community will grow only when it is given the freedom to grow, and part of this freedom is the ability to commit code to the project

As for Apache managing a community, and not code, Greg is saying, quite rightly, that the value of the Apache Software Foundation is not in the combined quality of the project's code, but in …

To start with the Postgresql talk , I ran in just too late as the slides about slony were just finished :(

Skipped out on Nigel's Talk, after not having time to play with the OpenPower at the office I`m assuming that Macbar knows enough about it already , Then the awkard break before your own talk it's the waiting and the people dropping in one by one , It's much easier to start directly after someone else :) Ray introduced my talk as "The talk you have all been waiting for" , hmm.. he shouldn't have done that. It made me fall back into my old bad habit of speeding trough my slides in just about 35 minutes rather than the scheduled 45 I had.

I'm starting to hear myselve thinking during a talk that I gave before "Hmm.. I've already said this" then realising 2 slides later that I actually didn't say that yet during that talk but during a previous one. That really might have confused people. I really have to work on my presentation …

I just received a copy of Alex Davies and Harrison Fisk’s book MySQL Clustering (us; uk).

I had the honor of reading a few of the chapters before they were published, and this looks to be a really excellent hands-on guide for setting up your own clusters. It takes you all the way from a thorough understanding of the types of nodes that make up a cluster, hardware requirements and initial setup through security and management to tuning and troubleshooting.

This is good …