The Data Warehouse, a work in progress

Last Friday Petter left the company and the Data Warehouse. He is one in a line of very talented youngster who over the years  have been working with and developed the Data Warehouse. When Ulf Davidsson and I 2001 created the Data Warehouse I know it was going to make an impact on the company, but I did not anticipate the success it has become. And this is much due to the great guys who replaced me and Ulf, we did a decent job too, but that is another post/story.

Camilla was the first one to join us. At the job interview she claims I said ‘If you do not know SQL well, you will be smoked. By the way we have a little test for you, you have these tables, now a production planner wants to see the weekly  consumption of components from warehouse XYZ. Write a SQL that show us this.’ This was not nice, Camilla was not prepared and it was not a trivial task, but she nailed it. Today Camilla is Team Lead for Business Intelligence at the company.
When Ulf left the company, Johan was hired. Johan was a young mathematician, with no special IT skills apart from playing computer games and some Matlab knowledge. Johan was a nice and intelligent guy, so we hired him. Johan joined us in the summer and he worked a week before two weeks of vacation, I told him he had to learn SQL during the leave otherwise he had to go. Johan came back not only knowing SQL inside out, but understood SQL better than anyone I know, after two weeks! He must have been working very hard that vacation. When Johan left, Camilla and I demanded we should have Petter transferred from the logistics department. Petter is a mathematician and a civil engineer, he also has his own football team where he is a bone crusher in the defense, (Johan is a forward in the team).
When I left, Feven replaced me, she has a solid IT education and is very sharp. You only explain once and she get it and do something better of it. After a week she managed the Data warehouse operations, and soon started to develop BI applications. She was project leader and developer of a new Data Warehouse for a factory in Milan, Italy. Apart from that she did a few PHP hacks in the ETL engine, fixing some old bugs of mine.
When Feven left, Henrik was recruited from another company in the Atlas Copco group. Henrik is a civil engineer and yet another brilliant co-worker of the Data Warehouse. Apart from the normal Data Warehouse operations and development Henrik is doing a lot of Qlikview development, and some PHP hacks fixing old bugs of mine.
I feel privileged to have worked with these five brilliant guys (Camilla, Johan, Petter, Feven and Henrik). It is a joy and pleasure to see new people taking on something you have created to new levels in ways you never anticipated yourself. I am sure Ulf Davidsson is proud of this progression of the Data Warehouse too.
It might look suspicious none of these guys stayed long. Camilla is still in the company, but now responsible for BI, and that is different from being a BI developer. They all being young and talented, it is just natural they move around. All of them have made significant contributions to the Data Warehouse.  I’m sure there will be a new brilliant member of the BI team replacing Petter, working together with Camilla and Henrik making the Data Warehouse better.


The graph now with Qlikview activities

The Data Warehouse monthly twitter graph is now enhanced with Qlikview user activities.

As you probably know by now the Data Warehouse is a Business Intelligence data storage system, it is GUI or viewer agnostic, viewers of users choice are welcome. MS Excel is the most popular one, but more and more users prefer Qlikview apps.
This monthly twitter graph is an attempt by me to show usage of the Data Warehouse and most usage is covered is the mQuery (millions of SQL queries, the lime-green line), But you do not see the Qlikview user activities, since Qlikview has it’s own proprietary storage. Data Warehouse information is exported to Qlikview,from there you have to measure activities via Qlikview. This is maybe thebiggest drawback of Qlikview, it is a closed environment, once the data is imported to Qlikview you can only access the data via Qlikview. You should not import the data directly from source systems into Qlikview, but use an open storage in between if you like to use other viewers together with Qlikview.  
I have used the calls figures from the Qlikview session logs, to illustrate user activities. The dotted dark yellow line represents Qlikview calls in the tens of thousands. If this is good figure to show Qlikview user activities I really do not know, if you have opinions on this please tell me.
You follow the Data Warehouse tweets here.