Tuesday, March 31, 2009

How it all began: Preventative Maintenance for DBA's

Wow, I started my first engineering assignment almost 20 years ago at Del Monte, the last San Jose, CA cannery. At that point I was a Civil Engineering undergraduate with strong CAD skills. A buddy of mine, Miguel, who was an Industrial Engineer major was raving about this innovative internship he had working for the plant manager, Howard, of a local San Jose cannery doing AM/FM. No, my first job was not in radio but about Facility Management (FM). The AM (Automated Mapping) piece was about giving you a map to visualize were your facility needed help.

Preventative Maintenance (PM) is a term commonly used in FM. The basic objective of objective is to avoid the constant fire drills in facility maintenance.

The Wikipedia provides the following definition for Preventive Maintenance:
The care and servicing by personnel for the purpose of maintaining equipment and facilities in satisfactory operating condition by providing for systematic inspection, detection, and correction of incipient failures either before they occur or before they develop into major defects.
Why was PM so important to Howard, the plant engineer? Because the price for an outage was very expensive in terms of labor and capital. How does a cannery work? It's a labor intensive 24/7 operation where if a major component\area goes down due to a maintenance issue you could have 100's of workers just standing around, your mechanics running around trying to figure out what went wrong and how to fix it ASAP and your capital, in our case fruit, is rotting as you wait to get back online.

Howard, was a smart guy and he new many of these outages could be prevented by doing PM. He and the mechanics knew that a motor or pump or elevator, etc ... typically worked well only for X months. And if he could keep track of all of key components and when they were last worked on. Then he might be able to come up with a plan to fix the equipment before it broke again and thus potentially preventing a problem or at least from an even larger problem.

The AM piece was about not having the mechanics run around everywhere. Don't fix one motor on one side of the cannery and then have your mechanics move all their equipment to the other side of the cannery to overhaul the next motor. Once they setup camp in a particular area what else should be done there. So, Howard wanted a map to visualize all the equipment that needed to be worked on for the next two months, so he could could plan and schedule the work. He also used the map to communicate to the mechanics what needed to be done. And later on he started using the map to look for patterns in outages. It became Howard's dashboard.

BTW, we did not call it AM/FM back then it was just known as Howard's pet project. A couple of years later as I learned about GIS ; I realized that we had built a crude AM/FM GIS out of RBase and AutoCAD.

Wouldn't it be great if DBA's could do PM to help them prevent their daily fire drills? Wouldn't it be great if DBA mangers had a dashboard to help them visulaize potential problematic areas and then be able to plan and schedule work to address these concerns, just like Howard?

Tuesday, March 17, 2009

IBM Eclipse Database tool for MySQL?

Did you read this correctly?   Yes, IBM has released some tools that support database development for MySQL.  Don't  worry  my blue blooded buddie DB2 and IDS are also supported.   Check it out:

It has a very long name:

Eclipse Based Foundation Toolkit for Heterogenous Database Applications

but it is basically provides a plug-in for:
  • Connecting to MySQL, DB2's and IDS
  • Browse, Create, Alter and Drop database objects (DDL)
  • Query editing and running for standard ANSI SQL with content assist
  • An IDE for SQL stored procedure (aka routine) development
The nice thing about this tool is that is uses the Eclipse update infrastructure to install into your existing Eclipse 3.4.1 environment. 

Monday, March 16, 2009

Smart Metering/DB2 Performance Expert

Henrik came up with an awesome analogy for DB2 Performance Expert.  Here is his blog entry:

The basic analogy that Henrik tries to draw is that if you want to find out how much energy you are using you have to go to your meter and check it.  But how do you know when you are using the most energy?   How do you know if you are using more or less than last month?  The only way to know is to collect/store the energy amount somewhere so you can later go back and do some analysis.    This is basically one of the main features of DB2 PE is to collect monitoring information (snapshot, event monitor) and store it, so you can go back later to do analysis on how much CPU or Memory have you been using, from who and when.   It also just provides a nice way to visualize database monitoring information.

Wednesday, March 4, 2009

Data Studio Eclipse 3.4 facelift

With Data Studio 2.1 it moved from being based on Eclipse 3.2.2 to Eclipse 3.4.1. One of the major changes/enhancements was leveraging the latest Data Tools Project (DTP). One of the most major changes was in how connections are managed. In eclipse 3.2 connection were under the Database Explorer view and in eclipse 3.4 there are in the Data Source Explorer. Check it out!

Not only did we add the eclipse 3.4 capabilities but we also did a few extras also. We added the ability to store and manage connection in centralized Connection Configuration Repository. There is also a nice video on the connection Configuration Repository on channel DB2.

The other major thing that changed and improved in going to eclipse 3.4 is how SQL results are displayed.

You can learn more about these enhancements from in the following article: