Editorials

Better Defining the SQL Server “DBA”

Understanding the Hazards that Zap your Hardware Resources!
This webcast will explore the challenges around maintaining optimal performance in a SQL Server environment while keeping downtime to a minimum. Well discuss methodologies you can take and use to administer your environment efficiently, and offer solutions to easily view server resources and anticipate growth.

> Register Now
> Webcast date: 12/11/2008 at 12:00pm Noon Pacific

Better Defining "DBA"
David wrote in with a different approach to understanding a given DBA. This could be applied at a more micro-level too, for identifying where someone stands on the feature sets that we’re responsible for knowing with SQL Server. This isn’t to say that someone should know all – in fact, as David’s model shows, it’s just as important to know where someone’s emphasis is with SQL Server as you work with them in your environment.

"First, there needs to be a better description of DBA or at least a better understanding. There is a vast difference between a dials and knobs DBA, meaning the basic backup and administrative duties, and a DBA who designs and implements Enterprise Data Models. There are many value added skills that a DBA can have. Understanding of the server engine and TSQL goes a long way for supporting the company infrastructure. Even taking part in database design extends the capabilities and the value of the DBA.


I have always had in my mind a model of the DBA with a value from 1 to 10, where 1 is the entry level SQL tasks and 10 is the Enterprise Data Architect who can work with networks, enhanced security models and sophisticated distributed queries, transactions and replication.

So the stability is also in the skill level of the DBA where the endpoints are less secure than the middle. So using this scale, anyone who ranks between 4 and 8 are a pretty good bet for security. It is the beginners and the top level “Experts” that may have the most problems since basic administration is known to all levels, and the Enterprise Architects design and implement, but are not necessary to maintain once the system is in place."

Would you use the same metrics?

Featured White Paper(s)
Choosing a Remote DBA Instead of a Full-time Consultant
Relational databases like SQL Server and Oracle grow 3x to 5x in size every three years and present organizations with signif… (read more)

Defending Against New and Emerging Database Threats
IT Security is constantly evolving. The cat-and-mouse game that researchers and security professionals play with attackers ex… (read more)