Skip to content

DBAzine.com

Sections
Personal tools
You are here: Home » Blogs » Craig Mullins Blog » Craig Mullins: Perspectives on Database Management » DBA Rules of Thumb - Part 8 (Be Business Savvy)
Best Practices
For IT best practices, my IT shop uses:
ITIL
CobIT
Balanced Scorecard
Six Sigma
None of the above

[ Results | Polls ]
Votes : 67
 

DBA Rules of Thumb - Part 8 (Be Business Savvy) DBA Rules of Thumb - Part 8 (Be Business Savvy)

Heads-down DBAs who know technology, but not their company's business, soon will be on the endangered species list.
Be Business Savvy

Although DBAs are technologists first and foremost, we need to be ever cognizant of the business reasons that our beloved technologies support. Yes, DBAs like to immerse themselves in the bits and bytes of technical solutions and learn all there is to know about the software we use. And this is okay--up to a point. As long as we take care not to blind ourselves to the business reasons for the software and hardware they love so much.

To keep the business "top of mind," the DBA's tools and utilities need to be tied to business strategies and initiatives. In this way, the DBA's work becomes integrated with the goals and operations of the organization.

The first step in achieving this needed synergy is the integration of DBA services with the other core components of the IT infrastructure. Of course, the DBA should be able to monitor and control the databases under his purview, but he should also be able to monitor them within the context of the broader spectrum of the IT infrastructure--including systems, applications, storage and networks. Only then can companies begin to tie service-level agreements to business needs, rather than technology metrics.

To fulfill the promise of business/IT integration, it will be necessary to link business services to the underlying technology. For example, a technician should be able to immediately comprehend that a service outage to transaction X7R2 in the PRD2 CICS region means that regional demand deposit customers cannot access their accounts. See the difference?

Focusing on transactions, TP monitors and databases is the core of the DBA's job. But servicing customers is the reason the DBA builds those databases and manages those transactions. Technicians with an understanding of the business impact of technology decisions will do a better job of servicing the business strategy. This is even more true for the DBA's manager. Technology managers who speak in business terms are more valuable to their company.

Of course, the devil is in the details. A key component to realizing effective business/IT integration for DBAs is the ability to link specific pieces of technology to specific business services. This requires a service impact management capability--that is, analyzing the technology required to power each critical business service and documenting the link. Technologies exist to automate some of this through event automation and service modeling. Such capabilities help to transform availability and performance data into detailed knowledge about the status of business services and service level agreements.

Today's modern corporation needs technicians who are cognizant of the business impact of their management decisions. As such, DBAs need to get busy transforming themselves to become more business-savvy--that is, to keep an eye on the business impact of the technology under their span of control.

© 2005, Mullins Consulting, Inc.


Tuesday, July 12, 2005  |  Permalink |  Comments (0)
trackback URL:   http://www.dbazine.com/blogs/blog-cm/craigmullins/blogentry.2005-07-11.5341301064/sbtrackback
Craig Mullins
Data Management Specialist
Bio & Writings
Subscribe to my blog Subscribe to my blog
« March 2006 »
Su Mo Tu We Th Fr Sa
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31  
2006-03-02
00:54-00:54 The Problem with Prediction
2006-03-04
18:52-18:52 Data Privacy Policies
 
 

Powered by Plone