Archive

Author Archive

DB2 for i › You’re a DBE, now what?

January 27th, 2014 Comments off
In between client engagements this past week, I had the opportunity to sit down with a long time member of my Center of Excellence team and all around super consultant Jim Denton.  We talked about the progress made in getting more and more of our IBM i users to embrace the idea of a DB2 database engineer. The notion of having a person (or persons) in the building who really get, and truly focus on "DB2 for i" is taking hold, and it's paying dividends for those companies that are forward thinking.

Jim was relaying an interesting question he received from one of our favorite clients over in Dayton, Ohio.  This particular company has fully embraced the wholesale and winning combination of acquiring data centric knowledge and skills, as well as embarking on a targeted and well managed database modernization and re-engineering project.  Good for them!

The question posed goes something like this:

"Hey Jim, now that I'm a database engineer, what should I be doing day to day?"

First, this is a really insightful question. It means that the person is thinking strategically and is ahead of the curve.  Well done!


The What and Why


What you should be doing day-to-day as a DB2 for i engineer basically falls into two categories:

  1. Reactive
  2. Proactive

Both reactive and proactive activities generally involve: monitoring, analysis and something else.

The something else will depend on your focus and your client (i.e. who are you providing value to).

Why you should be doing this seems self explanatory, but if it's not, consider this:

Partnering with leaders on solving data centric business problems and getting more value out of data is of the utmost importance. Doing it proactively makes YOU more valuable and your company or organization more viable.

In terms of monitoring, assume you are an investigator.  You need to peek behind the curtain, look inside the black box, ask the probing questions. In short, you need to learn more about your data, the usage of data and the life cycle of data. You need to discover who is using the data and for what purpose.

Here are a few ideas to get you started. If you need more, please reach out and we can help you identify and prioritize activities that provide a good return on investment. We can also help you get better at identifying and partnering with your colleagues.

The Ideas


Narrow your scope to the top 10. Once you have a repeatable process, open the aperture and expand.

Profile your data. Learn more about the properties and trends of tables and indexes. How large are they. How fast are they growing. Who is using them.  How are they used. Who has access to the data. How is the data accessed. When is the data accessed.  Get the idea?  Know your data.

Take periodic and consistent snapshots of the the query plans. Store this data and use it to develop trends. What are the longest running queries. Who is running the queries. What are the attributes of the query requests (do you see simple statements, or complex statements).  Who is reading the three million results from the query run twice a day, every day (I can tell you... no one - this is an extract!).

The DB2 for i catalog is your friend. Get to know it. Use it.

Make a blueprint of your current data model. Pick a subject area or application and model the database objects, such as they are. Use reverse engineering tools and methods to be more productive. While you're at it, take this opportunity to learn a proper database modeling interface. Something that has more colors than just green.

Use the blueprint to identify gaps in your organization's relational database best practices. SQL queries are based on and driven by the data model. A bad data model means more work for the SQL query. A good data model means less work for the SQL query. If the model behaves well (i.e. well defined sets), then the SQL will behave well (i.e. good set operations).

Using the current data model and your gap analysis, define a future data model, build a new blueprint. Formulate a plan to modernize and re-engineer the database to incorporate the foundational elements that support data centric processing.

Watch and wait for an opportunity (i.e. business requirements) to implement the modernization and re-engineering plan. We like to do this on a targeted and cost justified basis. Better yet, don't wait; engage the business to understand pain points and new initiatives.

Get out of your office or cubical. Go meet people. Talk to your colleagues and clients at every level. Find out what they are struggling with. Find out what they are using the data for. Find out what the data is NOT providing them.

The information seekers in your organization are requesting data from IT. The data is extracted and downloaded to a PC. Once on the desktop, the real magic occurs. Peek behind the curtain, look inside the black box, ask the probing questions about what the data is used for and why. Better yet, ask the information seeker "what problem are you trying to solve?". This is how you get in a position to provide value on a proactive basis.

This is how you become relevant and stay relevant.

What else?

Well... what about you?

I recommend you strive to learn something new every week. Take an hour (or two) each and every week for yourself. Crack open the SQL Reference manual. Initiate a project for yourself. Do a proof of concept or proof of technology. Develop and hone your soft skills.

All work and no play makes Jack a dull boy.


Read the original at DB2 for i.

Categories: Blogs Tags:

DB2 for i › RESOLUTION

January 16th, 2014 Comments off

As we pass AND approach the various new year thresholds, this is a time when most of us symbolically reflect on the past, and plan for the future. This has been practiced for centuries in cultures all around the world.

While crossing the seasonal threshold and moving from one year to the next, there is a long standing tradition of making (and breaking) a resolution. Many of these annual resolutions involve a promise to do less, do more, or do better.

According to Merriam-Webster the definition reads...

res·o·lu·tion    noun \ˌre-zə-ˈlü-shən\

: the act of finding an answer or solution to a conflict, problem, etc.

: the act of resolving something

: an answer or solution to something

: the ability of a device to show an image clearly and with a lot of detail


I really like all of these explanations, and believe they apply very well to what we need to do as IT professionals (your personal resolutions are your own business).

When I reflect back on what my team has witnessed in countless IT organizations around the world, a few clear and distinct things come to mind.

Every business leader wants to have (IT) solutions that are:

  • Flexible
  • Extensible
  • Agile
  • Scalable
  • Timely

To meet these requirements, new tools, new techniques and new approaches need to be embraced. And if you ask me, doing so without throwing the baby out with the bath water. In other words, keeping what works and re-engineering what doesn't. Rarely do we find that it is cost effective or advantageous to start over from scratch. Some might call this approach "evolution, not revolution". The pace at which you evolve is a function of time, energy and funding. I would also throw in will power.

From a data perspective, business leaders want more relevant information. They want to move from data being the static and benign byproduct of a transaction or event, to data being the raw material that is refined into insightful information; something that provides a unique and otherwise hidden perspective on what's happening, what's coming, what's needed.

For many (most?) of my clients, it seems that data is dragging them down like some kind of massive anchor. A huge bucket of bits that is increasing in weight and volume, forever tugging on the organization's precious resources.

For a few keen companies, data is an enabler. This byproduct of their transactions or events will serve an important purpose. That is to become a lens to focus the past, and for looking into the future. Their data becomes an asset; something to be preserved, treasured and made useful. Something that becomes a unique advantage to their business, their partners and their customers.

Approaching Information Management Differently


Another major trend we see is that increasingly, the formal IT organization is being bypassed. Or at best, relegated to being just the conduit for data. This means that the effectiveness and more importantly, the value of traditional IT organizations is being eroded.

We see more and more business users acquiring information technology solutions directly - deploying and using them without the assistance or oversight of the IT organization. Obviously there are many concerns with this trend. The one I want you to focus on is: irrelevance.  As in, your knowledge, skill and expertise are irrelevant, no longer required.

Increasingly, users have access to the data. The various lines of business have growing requirements for information. If IT cannot provide the information, then they are asked only to provide the data. Sooner than later, the "value add" of IT will dry up. To be sure, IT should have a vital part to play in the acquisition, storage, management, and productive / safe use of data. But given the current trend, how do you stay relevant?  How do you continue to provide value?

One idea I have been sharing with my clients involves a change in philosophy and approach. In terms of engaging your business leaders, users and colleagues, move towards a consulting oriented discussion instead of service oriented discussion. As a consultant, you are in a position to guide and influence the community around you. And don't wait for them to come to you.  Be proactive. Go to them.  This is what makes you valuable and keeps you on the list of critical success factors.

Find a way to help, not hinder.

_________


For the coming year, let me suggest that you persevere to:

  • Stay relevant
  • Make and maintain a connection with your users clients
  • Provide real value

To accomplish these things (from an information management perspective), I recommend you personally resolve to:

  1. Learn more about the science and art of information management
  2. Gain control and governance of data and data access (don't be a Target)
  3. Get better at the design, architecture and modeling of database solutions

Happy New Year!



Read the original at DB2 for i.

Categories: Blogs Tags:

DB2 for i › DB2 for i SQL Classes for 2014

December 11th, 2013 Comments off
The DB2 for i Center of Excellence team has scheduled some high powered classes in Rochester, Minnesota (home of IBM i and DB2 for i) for 2014.  Make your plans now to take advantage of THE experts and in some cases, the folks who wrote the code.

For the data centric application architect and SQL programmer we have the DB2 for i Advanced SQL Workshop. This event is scheduled for February and September.

To view the description, dates and to enroll go  here  and be sure to check out the video overview at one of these sites:

English on YouTube

Spanish on YouTube

English on YouKu  (I have no control over the commercials!)

For the DB2 for i Engineer, or anyone interested in becoming more adept at understanding and solving SQL performance and scalability issues we have the DB2 for i SQL Performance Workshop. This event is scheduled for March and September.

To view the description and to enroll go  here  and check out the video overview at one of these locations:

English on YouTube

Spanish on YouTube

English on YouKu  (again, I have no control over the commercials!)

If you have any questions about the value of attending these workshops, please reach out to me.

If you are interested in bringing these knowledge and skills transfer workshops directly to your organization on a private basis, we can do that too.


Read the original at DB2 for i.

Categories: Blogs Tags:

DB2 for i › Big Data Analytics: an Example

November 1st, 2013 Comments off
During virtually ever presentation I've made this year I've been asked about "big data"...

What is it?
Why is it?
Can IBM i do it?

My brief answer usually takes the form of both a description, followed by a question back.

The subjective and objective description of Big Data and the notion of analytics have been covered here and in many other places, so I'll spare you the repetition. Do be aware that Big Data is so hot right now, everyone is jumping on the band wagon - using the phrase as a way to associate their products and services with the latest trend. Combining "Big Data" and "Cloud" results in a hurricane of marketing hype that is vast and powerful.

In my quest to provide clarity and understanding, the question I pose back to the audience goes something like this:

"Do YOU have big data, and do YOU have a requirement to analyze it"?

Most folks stare back at me, wondering whether they do or not. To help them really understand my question, I offer a simple (and favorite) example of Big Data Analytics:

"Imagine the capture and analysis of every tweet flowing through Twitter on a daily basis".

To be sure, most folks in my audience are not taking full advantage of the data they have in house now, much less able and willing to make use of the truly massive amounts of data flowing past their internet doorstep.

A Real Live Example


Lo and behold while traveling this week, I read an article that crisply illustrates my default example of Big Data Analytics.  The article highlights a new startup, Social Market Analytics, that looks at all the tweets pulsing through the world wide network.

They analyze the messages to develop a profile based on the Twitter "chatter" about a given company traded publicly on the stock market. The resulting profile and corresponding scoring of the dialog will (hopefully) provide to investors a crystal ball of sorts. At least that's what they are telling potential users of the service.

If you want to read the article for yourself (and I recommend you take time to do so), it appears in the October 15, 2013 edition of American Way Magazine.

And if you are still wondering what it takes to handle big data, imagine trolling through 400 million tweets per day, looking for the few pearl laden oysters, in near real time!


Read the original at DB2 for i.

Categories: Blogs Tags:

DB2 for i › Are You Ready to Advance Your Knowledge

October 14th, 2013 Comments off
In previous posts we've discussed how to become a database engineer, and we've talked about how to advance your knowledge and skills around SQL.  We've also chatted many times about the importance of learning the science and art of data centric design and programming.

To that end, I'm happy to announce a couple classes being offered by the DB2 for i Center of Excellence in Rochester, Minnesota (home of IBM i and DB2 for i).

For the application architect and SQL programmer we have the DB2 for i Advanced SQL Workshop. This event is scheduled for 12-14 November 2013

To view the description and to enroll go here.

For the DB2 for i Engineer, or anyone interested in becoming more adept at understanding and solving SQL performance and scalability issues we have the DB2 for i SQL Performance Workshop. This event is scheduled for 3-6 December 2013

To view the description and to enroll go here.

If you have any questions about the value of attending these public workshops, please reach out to me.

If you are interested in bringing these workshops directly to your organization on a private basis, we can do that too.


Read the original at DB2 for i.

Categories: Blogs Tags:
css.php