by Craig S. Mullins
Before we go any further, let me briefly answer the question posed in this column's title:
OK ... with that out of the way, let's discuss the issue ...
Every so often, some industry pundit gets his opinions published by declaring that "Database administrators are obsolete" or that "we no longer need DBAs." Every time I hear this, it makes me shake my head sadly as I regard just how gullible IT publications can be.
These types of proclamations are typically based on the increasing autonomics within database systems. And yes, database management system (DMBS) software is becoming easier to use; some of the things that used to require manual effort are now automated. But that does not eliminate the need for DBAs!
It is not possible to entirely automate all of the duties performed by DBAs. For example, how can a DBMS make changes to its database structures (such as adding new columns to support a new business requirement)? How would it know what to add-
Database design, both logical and physical, will always be needed (along with knowledge of the business) to create and maintain properly running database systems-
What about backup and recovery? Would you trust a DBMS that had corrupted data to recover itself? If it was that darn smart, why did it become corrupted in the first place? Yes, the job of the DBA will morph and change-
Database administration needs to be practiced in a more rigorous manner. Too often the DBA is viewed as a fireman. This is not meant to disparage firemen, of course, but the fireman is called after the fire has started. Database administration practiced as a management discipline should be focused on prevention first, cure second. This requires a set of best practices for database implementation and management to be designed and followed.
There are several layers of misunderstanding and poor DBA practices running rampant across the industry that need to be addressed. The most pervasive is probably faced by DBAs working for organizations predominantly focused on the Internet. As companies move from traditional development to web development, there is the inevitable change in mindset that creates "mad rushes." This "get it done NOW!" mentality is bad news for DBAs because it is detrimental to good database design practices. Poorly planned or unplanned changes get made to the database in order to speed development. These mistakes persist for years and can cause poor performance, data integrity problems, and make future changes more difficult.
Another problem is the "we don't need no stinking DBAs" attitude. Sometimes smaller organizations attempt to implement database applications without DBAs. Well, not really-
Perhaps the greatest issue facing DBAs these days is the whole "proactive versus reactive" argument. Many so-
The bottom line is this: As portions of the DBA job are automated, the DBA can focus on those things that have been ignored or poorly addressed. They can better implement practices and procedures for the things that cannot become autonomic: backup/recovery and change management, to name two. And, they can begin to tackle bigger problems ... such as business issues, compliance and governance, data quality issues, metadata management, and so on.
Long live the DBA!
From Database Trends and Applications, June 2010.
© 2012 Craig S. Mullins,