Mar 5, 2012
What Does a Database Administrator Actually Do?
Most people in your organisation, never mind everyone else, have no real clue as to what it is you do.
It’s not because you don’t actually do anything, at least I hope not, it’s because the domain of responsibility for a DBA is both vast and varied. Ask any two DBAs what it is they do exactly and you can expect to get two broadly different answers.
For those new to the event, #mememonday is the community creation of Thomas LaRock (Blog|Twitter), the driving force of which is to encourage the SQL community to put virtual pen to paper. This months theme “List out all the little things you do as a DBA, since the term DBA means so many different things in each shop.”
In the spirit of adding to the confusion, here are some of the things that I do in my current role as a “DBA”.
- project management
- consulting
- server builds
- troubleshooting
- backups
- restores
- security
- compliance
- change control
- change management
- develop a hobby, preferably a full contact sport, to vent
- server specification and hardware procurement
- development consulting
- database design
- solution design
- team mentoring
- customer liaison
- release package development and deployment
- capacity planning
- ignore as many of the competing communication channels as possible
- wrestle daily with email volume and rules
- administer all database platforms not just SQL
- research emerging database technology
- ensure platform availability
- continually review existing solutions and processes for improvement
- devising elaborate methods to synchronise and initialize overly complex replication topologies
The astute reader amongst you will have noticed a degree of sarcasm sprinkled throughout the list. A sense of humour is a valuable character trait for a DBA, a survival skill that can see you through troubled times.
If you really want to learn more about the DBA game and what it takes, head on over to the How To Become A SQL Server DBA area on the blog. There’s a wealth of great content there from both myself and other community sources. As always if you cannot find the answer to your question let me know.
In the spirit of #mememonday I encourage you to put virtual pen to paper and add to the confusion by sharing some of the little things you do as a DBA.











Mar 12, 2012 @ 21:29:00
hi john,
i am swetha ,i joined as a fresher in a company as sql dba .will u tell me the way we have to learn sql .i want to know what is the starting and ending point of sql.The thing is from where i have to start learning…
pls,please guide me i want to settle as sql dba ,,pls reply to the post.
Thanks in advance
Mar 13, 2012 @ 14:45:00
Hi Doredia, check out my post series: Your Road To Becoming a DBA where I answer this question:
http://www.johnsansom.com/your-road-to-becoming-a-dba/
Thanks for your comments!
Mar 14, 2012 @ 11:30:00
John,
Great to know .
Thanks for your article.Never expect such a huge list
Thanks for sharing,
Good Day,
Anish
Apr 27, 2012 @ 13:17:00
Here’s my definition of the DBA:
Ensure availability, security, and performance of databases.
1. Prevent data loss due to hardware failure (mostly backup)2. Prevent data loss due to user action (permissions)3. Ensure adequate performance of database servers (monitoring + tuning)4. Ensure availability of data (High Availability)5. Develop sql code for DB management, develop automatic DB management solutions
Apr 27, 2012 @ 14:00:00
Sounds like plenty to be getting on with to me and with Data at the heart of responsibility as it should be. Thanks for sharing!
May 31, 2012 @ 13:21:00
I do plenty of the above – and soon to be grading for my Tae Kwon Do black belt. Venting is good!
May 31, 2012 @ 13:38:00
Rob, combat sports and martial arts are a great way to unwind! Just be sure not to vent on your colleagues
Thanks for your comments!
Sep 04, 2012 @ 14:07:30
Hi john,
How network issues related to the SQL server performance.will you please describe it in brief…
thanks,
swetha
Sep 04, 2012 @ 14:51:49
Hi Swetha,
It really depends on how you’re working with SQL Server. Are you seeing a particular performance problem?