MySQL Con: Data Warehousing With MySQL

by Derek J. Balling

Related link: http://www.mysqluc.com/cs/mysqluc2005/view/e_sess/6219



This afternoon, I attended John Paul Ashenfelter's Data Warehousing With MySQL talk at the MySQL Users Conference.

I was trying to come up with some way of saying how completely and totally useful it was to me. After all, I realized after sitting there for the afternoon why I'd been struggling with my own implementation of a data warehouse at my workplace. I saw what he was defining as "classic mistakes" as being synonymous with "things I had just implemented".

I struggled for a while until I read John Adams' post about the talk (as given at a previous conference), and realized that John had said nearly everything I wanted to say, but done so much more eloquently than I could have.

While the talk was centered on MySQL, in reality it had much more to do with data warehousing in general (and I firmly beleive that an Oracle or SQL Server DBA in attendance would have gotten as much out of the session as all of us MySQL users did). It was, by and large, agnostic to the database being used, and more about the design and mindset behind the data warehouse itself.

I feel like I want to rush home now, tell my marketing guy to stop using the existing warehouse implementation while I completely gut it and start from scratch with something that he'll be a lot happier with.


Am I right? Am I wrong? What do you think?


2 Comments

adamsj
2005-04-19 04:53:14
Of course you're right
But I'm curious--was my guess that he might de-emphasis the open source tools surrounding the warehouse and put more emphasis on MySQL proper a good one?


And don't miss Magoulas' talk--the last I saw of him after it was Ashenfelter buttonholing him and saying, "Man, I want to talk to you," or words to that effect.

dballing
2005-04-19 08:40:26
Of course you're right
Yeah, I think it was the right way to go about it. He mentioned basically that there's any number of reporting tools you might be using to access the database itself, but what's really important is that the foundation - the DB itself - is sound. From that, it simply becomes a presentation issue. (severely paraphrased).