Database administration is a technical discipline, and it almost goes without saying that DBAs should be armed with significant technical knowledge. And this column typically covers the many diverse technology issues facing DBAs. However, there are non-technical qualities and aspects to the DBA role that are not as frequently discussed. So, this month we will proffer some guidance on non-technical areas for DBAs to focus on to make them more valuable to their employers!
Start with a proper attitude: Unfortunately, sometimes DBAs are viewed as surly prima donnas, unwilling to collaborate and quick to denigrate. This reputation has been improving lately, for example with the advent of DevOps requiring a more cooperative approach to work. To excel as a DBA, you will need a flexible and amiable demeanor. There are several key aspects of the attitude that DBAs must strive to embody.
The first is to adopt a problem-solving mindset. DBAs often encounter complex and critical issues. A problem-solving attitude, characterized by a proactive approach and a willingness to find solutions, is indispensable.
But this is not sufficient enough. DBAs must be viewed as team players. Today’s DBA team must collaborate with various departments, including development, IT operations, and business units. A collaborative and supportive attitude fosters effective teamwork and efficient problem-solving.
DBAs should also be constantly working to hone their communication skills. Clear and effective communication is important for explaining technical issues to non-technical stakeholders. A DBA with a strong communication style can build trust and prevent misunderstandings.
Finally, DBAs need to possess patience and perseverance. The job can be demanding and stressful. Patience and perseverance are essential for handling complex tasks, troubleshooting issues, and dealing with unexpected challenges.
A DBA with a positive attitude can improve team morale, foster creativity, build strong relationships, and increase their overall job satisfaction. A positive DBA can positively impact the overall performance of the organization.
Always document everything: DBAs need to be able to write well so that they can document the processes used to resolve the many challenging tasks and time-consuming problems they encounter. Such documentation is valuable to avoid duplicating effort when you encounter the same, or a similar, problem in the future. It is better to read your documentation than to try to re-create a scenario from memory. And your documentation may save somebody else a lot of work when they need to work on the systems you manage and administer.
Another aspect of documentation is that a good DBA will “keep everything!” It is good practice to store everything you come across while performing your job. This includes, but is not limited to manuals, scripts, programs, proceedings and presentations, notes, books, white papers, reports, articles, and, well, everything you use to do your job properly.
Embrace automate: Why should you do it by hand if you can automate DBA processes? Anything you can do by hand probably can be done better by the computer—if it is programmed to do it properly. And once it is automated you save yourself valuable time—that probably will be spent tackling other problems.
Furthermore, don’t reinvent the wheel. Someone, somewhere, at some time many have already solved the problem you are attempting to solve. Look to the web for sites that allow you to download and share scripts. Or if you have budget money look to purchase DBA tools from ISVs that can automate and optimize your database environment.
Share your knowledge: The more you learn, the more you should try to share what you know with others. You can participate in and share information at database user groups or industry conferences. Be sure to attend these sessions to learn what your peers are doing. And when you have some good experiences to share, put together a presentation yourself and disseminate your expertise to your peers. It is my experience that you can learn more by presenting than by simply attending. This is so because attendees will likely seek you out to discuss their experiences or question your approach.
Another avenue for sharing your knowledge is to participate in an online forum or group. Using social media sites like LinkedIn and Reddit you can share your knowledge and benefit from others who share their experiences. Working to put together a tip or article for these sites helps you arrange your thoughts and to document your experiences. If you have the time, consider publishing your experiences on your own blog, or in collaboration with an industry blog. Doing this can take even more time, but it brings the most exposure.
But the best reason of all to share your knowledge is because you want others to share their knowledge and experiences with you. Only if everyone cooperates by sharing what they know will we be able to maintain the community of DBAs who are willing and eager to help.
Don’t panic! Problems will occur—there is nothing you can do to eliminate every possible problem or error. Part of your job as a DBA is to be able to react to problems with a calm demeanor and analytical disposition. When the system is down, or applications are unavailable, your environment will become hectic and frazzled. The best things you can do when problems occur is to remain calm and go about your job using your knowledge and training.
As the DBA, you will be the focus of the company (or at least the business units affected) until the databases and applications are brought back online. It can be a harrowing experience to recover a database with your boss and your users hovering behind your computer and looking over your back. Be prepared for such events because eventually they will happen. Panicking can cause manual errors—the last thing you want to happen when you are trying to recover from an error.
Summary
Making sure that your DBAs possess these 5 basic qualities will help to improve your organization’s operational efficiency and make database administration a more manageable task.