Reading Time: 3 minutes
Like most people I get my yearly performance evaluation but I’ve had the experience that my peers don’t really know how to evaluate me. So how do you effectively evaluate a DBA.
Your manager/team leader/superior has the information from previous performance interviews and based on that sees if you have performed as you should, or under, or above what was expected.
What I found out is that when the IT department doesn’t have a good understanding of the DBA’s responsibilities and possible metric to measure the effectiveness of the DBA (group) the evaluations don’t work.
How are most evalutions done
Your superior should have at least the following information:
- Knowledge of the DBA’ s job requirements
- Record of classes / training attended throughout the year
- Attendance records
- Productivity reports
- Records of previous performance interviews
You and your superior come together and based on the information above your superior shows how you performed.
In most cases you only have little room for discussion because most things are already discussed in previous interviews.
The problem is that there are so many factors that make this so difficult. A few questions that come to mind are:
- There are many different types of DBA’s, which one is used for evaluation
- What are the metrics to measure the performance and effectiveness on
- When is a DBA successful and and when is his/her performance good/medium/bad
The problem with this is that most managers I had (don’t get offended if you’re one of them this is just my experience) only look for certain aspects that can be found in other IT related jobs like how many incidents you solved or changes that are made.
You can look at the amount of incidents that were registered and fixed during that year but that’s only the case when you talk about real incidents like a server going down, low disk space or performance related problems.
This can be very offending towards other people who could do a tremendous amount of work in the background but is never really visible.
A DBA is a “jack of all trades” kind of person but to clearly evaluate a DBA you have to have a clear understanding what he/she does.
To address the first question in Problem-paragraph Craig Mullins wrote a nice article about this which gives a good overview of what kind of DBAs there are. Of course there are different versions and flavors especially with the DevOps who are hot nowadays.
An article that helped me out and for most still applies is an article written also by Craig Mullins called “Measuring DBA Effectiveness“. It helped my manager and me to create an evaluation metric.
The last thing, and I surely hope that’s in place, make reports from your service management application like Topdesk or SysAid. The reports give a clear understanding of the workload that’s been done.
To have another metric for the workload I used Brent Ozar’s “sp_Blitz” to create a health-check with all the items that need to be addressed. When an item of the list is done, remove it or give a status done, to keep track about what’s been done. When the manager asks for the progress of the list you can hand over the list.
I hope this helps you out for your next evaluation.