As a DBA you you are pushed for time. The role of the DBA has changed considerably and in many organisations is central to developing and managing large scale data based applications. To illustrate this point , the range of tasks I dealt with yesterday included:
-Troubleshooting some poorly formed queries on SQL server
-Investigating DB2 backup failures on TSM
-Planning a JRules database implementation
-Security review of financial application
-Deploying a SQL server instance
-Reviewing alerts for monitoring
-High level discussions for SQL server architecture planning
Only 2 of the above where scheduled , the rest were last minute requests. Organising my time to ensure the critical tasks are completed is a challenge. My mantra is : any issue that relates to availability and performance of a production database take priority. Even though this is an effective
principle , it's not practical in a demanding IT environment
Following is my time management system. C.L.E.A.R The aim is to be more effective not more efficient
Critical Jobs
Paretos principle , 20% of effort to achieve 80% of job(s) - and 80% of effort to achieve the remaining 20% of job(s). My list is broken down into 2 parts. 20\80.
In the 20 part I place all the high priority critical jobs , in the 80 section the lower priority. I work from the top of the 20 list
Let Slide - this is the mirror image of step 1 i.e 80% effort to achieve 20% results
Just make sure you let slide or delay the right jobs!
Extreme jobs first. What is the toughest job for today? Applying this approach will train you to complete complex jobs
Always : is this the best use of my time?
Review session - just a few minutes - to plan the day.Review through your goal list every morning.
Source:Jack Vamvas (http://www.sqlserver-dba.com)
