In a previous Tuesday Tips post we provided a look at the primary business metrics that DBAs should balance in order to optimize database management. As if that balancing act weren’t enough, the entire job function of a DBA has really become an exercise in servicing two organizations: Operations and Applications. Have you found yourself facing conflicting job pressures? Download the complimentary Dell Software whitepaper, “Key Methods for Managing Complex Database Environments,” here for tips. First, let’s look at why it’s happening. In our Internet connected age, corporate applications are no longer just a cost center, they have transformed to a profit center by generating revenue through customer interaction. While a positive business advancement, for DBAs the shift means an increase in urgency for application support. That urgency exists because application downtime means a more direct hit to the corporate bottom line. For optimized database management, simplify by considering the high level objectives of operations and applications support: Applications : Ensure high-quality services experience for users Operations : Effectively manage resources Demands from application and operation teams align with demands for DBAs to address both incident management and problem management. Let’s also break down these common DBA tasks to core objectives: Incident management : Restore service as quickly as possible, preferably to maintain defined SLAs; speed of resolution measures success Problem management : Identify and address the root cause of errors to find a long-term solution; focus shifts from speed to accuracy While the pressure on DBAs continues to grow, a strategy that focuses daily job functions on the deliverable will help bring your day-to-day in balance. With objectives defined, don’t forget the important role third party tools can play in easing management. Check back for upcoming posts on selecting third party tools. Can’t wait? Download the Dell Software whitepaper, “Key Methods for Managing Complex Database Environments,” here .
↧