SQL Server is so well-behaved it's often installed by 3rd party applications in an organization or department without a professional Database administrator (DBA). When such implementations need attention (e.g. backups), system administrators often get involved as acting-DBAs, and some of them discover they enjoy it and start spending more and more time with SQL Server. Or someone starts moving from a coding job to a junior DBA position. These are a couple of examples of how people can become DBA's without formal training, and some of these folks occasionally start to wonder, "What are the main priorities I should pay attention to as a DBA?" Even when these guys and gals get training, it may not point out exactly what a DBA's primary duties should be, so here's a list I've compiled over the years as the top areas (categories) of DBA responsibilities, followed by a breakdown of some of the major tasks in each area. Obviously, DBA tasks will vary from day-to-day and from organization-to-organization, depending on how large the databases are, how many users they have, how many other people are involved in the organization's data management, and what their skills are, but all of the tasks listed below should be covered by someone. I'll also mention that this arrangement of categories and tasks has some matrix characteristics, for example, documentation is a task in multiple areas, but it's also a major category because there are documentation requirements that are outside of the other categories. If you think of something I've left out, please let me know.
Configuration
Data Management
Documentation
Education
Maintenance
Performance
Planning
Reporting
Security
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.