Why is Database Administration so hard?
The position requires a broad spectrum of knowledge ranging from development to system administration and even management.  Not only must a DBA know about backup, recovery, internal operations, memory and security, but also how to communicate with both developers and management.  A DBA could be giving a high level presentation to management, helping a developer tune a query, provisioning disk space for a new system and restoring data from backup all within the same hour.  These responsibilities require a wealth of knowledge with little overlap.

The consequences of failure are usually greater for a DBA than a developer.  DBAs often support dozens, even hundreds of different applications and systems most of which are vital to the success of the company.  A security breach, recovery failure, or performance problem could have far reaching and devastating ramifications.  This requires a level of knowledge and experience that can’t be gained in a short amount of time.

The better a DBA does their job the less visibility they have.  A DBA with a database that is secure, recoverable, available, and performing well will lack recognition.  DBAs get noticed when there are problems.  Not only do they get noticed when their problems are self-inflicted, they also get blamed when the database has problems due to poor coding, improper network setup, or incorrectly configured storage.



I switched from developer to DBA when I was 29.  For me the things that make being a DBA difficult also make it rewarding.  I enjoy absorbing and using a wide spectrum of knowledge, and the greater opportunity for failure makes the avoidance thereof all the more meaningful whether others see that or not.