It seems that there’s so much to learn when you are first working as a production DBA. What do you focus on first? How should you prioritize your learning? What things should you automate and measure? What skills are core to your job, no matter how long you’ve been a DBA. These are the things that we think that all production DBAs need to know and continue to build upon.
In our DBA Fundamentals presentation on The Minimalist Guide to Database Administration, Thomas LaRock ( blog | @sqlrockstar )and I (@datachick) discussed the core skills one should have when filling a DBA role. That presentation has been recorded (I will update here when it is posted). I hope you were able to join us or will stop by and watch the recording.
10 Tips for the Minimalist DBA
- Protecting your data is your number one job. I’m betting that no one else in the company has a to-do list to protect the company’s data. Maybe someone at the strategic level, but not to actually ensure it’s available when it needs to be. That means your first job is to ensure backups and recovery are working. Test your backups, test your restores. The first thing I do on new projects is to ask about the backup and recovery configurations. I once found that the production system had not been backed up for more than five years, even though everyone else thought it was backed up daily. Don’t just ask. Go look.
- Don’t waste time alerting yourself of things that don’t require a reaction. You may be tempted to set up alerts so that you get an email and a text message to notify you every time a backup successfully completes. Or when your online monitor finds your database upright and smiling. However, that soon leads to alert blindness. You will miss the real alerts that you need to do something about. Hard drive getting full? Response times approaching ice age times? Those are things you’ll need to be ready to deal with.
- The best DBA is a lazy DBA. Not a sleepy DBA, but a DBA that automates as much as you can. Think of this as a Driven, Lazy DBA (DLDBA). Do you have tasks that take 15 minutes to do, require no human decisions and that you have to do multiple times a week? Those are automation candidates. Be lazy so that you can spend your already overscheduled time on tasks that need your awesome data professional skills.
- You can’t manage what you don’t measure. If you don’t know it exists, or whether it is still up and running, you will be stuck in a perpetual firefighting mode. Tom thinks that firefighters would make great DBAs, but that doesn’t mean that great DBAs are in 24/7 firefighting mode. It’s also good to understand what’s the best way to measure these things. Almost all measurement consumes resources. Do you understand what make sense for each case?
- You need to understand the basics of all kinds of things. Always be learning and looking forward. Just because we picked a few things to focus on doesn’t mean you can ignore all the rest. You need to build your basic literacy of things that aren’t your primary responsibility. Storage basics, database design methods and practices, web services, development tools and methods…yes, there’s a lot. Start with the things that are causing your databases the most pain and work out from there. It’s sometimes a bit overwhelming when you attend a conference or pick up a book and realize how much you just don’t know enough about. In fact, there’s a name for this: the Dunning-Kruger effect. The more you know, the more realize how much you don’t know. The only way to deal with this is to always be learning and looking forward. Sure, there are some people making RAID-loads of money supporting COBOL and IMS systems, but overall staying afraid of new technologies like cloud, NoSQL, BI, and big data is going to keep you blissfully ignorant.
- You must practice everything while your database isn’t burning. It’s not enough to watch a one hour presentation on how backups and restores work. It’s not enough to download a script. You need to get in-depth, hands-on experience doing these things. Not just a one time in a class thing, but practice with real world situations and data. You need to schedule that time to do this. And your boss needs to support this. Then you need to practice with intentional errors. What happens when the time on the server is messed up? What happens when you don’t have the right log files? What do you do if the SAN is down? Where are your restore procedures and checklists documented? You don’t want to be “learning on the job” when your PHB boss is standing beside you and there’s smoke coming out of the server.
- Writing stuff down is good. It’s Agile even. The Agile software method calls for the right amount of documentation. Many read this as “no documentation”, but they are wrong. Yes, sometimes to you can just walk over and ask the person who set up the job why they did something, but on my projects that person has moved on to 6 more teams since I last saw him. I recommend using wikis or SharePoint collaboration areas for these things, so that they are all in the same place and can be accessed with any device. By the way, do you know if your documentation is backed up? Redundantly available? Restores aren’t just for databases.
- The more you install, the more you have to manage and troubleshoot. Install only what you need. Of course, that may mean looking a bit forward for planned uses, but there’s no need to install everything “just in case”. You might even want to look at Server Core as an option, since it has a tiny footprint, requires less management and you can still use your remote GUI tools to manage it.
- Don’t be the one that panics. Practice and documentation mitigate stress and panic. This is where all your laziness, planning, testing and learning pay off. You’ve seen the guy that sits in front of a server, rapidly pulling cables, pushing buttons, running scripts and wizards and has no idea that he’s making things worse. Don’t be that guy. The more calm you are, the better job you’ll do. And the more calm everyone else will be.
- Empathy is a highly-valued trait. For users, for other data professionals, for everyone. Empathy isn’t sympathy or feeling bad for others. It’s about understanding what their pain points are and why they feel the way they do. If you can reflect that empathy, work will be easier and progress towards a common goal can be made. If you come at all issues with a zero-sum game approach, you’re going to have issues getting in the way of doing your job.
We also listed these links as great places to find more information about these skills or to practice them:
- Sampling Database Backups https://www.simple-talk.com/sql/database-administration/statistical-sampling-for-verifying-database-backups/
- Are your Backups Available? http://www.sqlservercentral.com/articles/Administration/areyourdatabasebackupscurrentandavailable/2309/
- SQL Server Virtual Labs https://www.microsoft.com/en-us/sqlserver/learning-center/virtual-labs.aspx
- Windows Azure VMs http://windowsazure.com
- What to Do if Your Database Catches Fire http://thomaslarock.com/2013/11/database-catches-fire/
- SQL Server Troubleshooting http://thomaslarock.com/2013/11/sql-server-troubleshooting-useful-links/
- DBA Survivor http://www.apress.com/9781430227878
What advice did you wish you’d had years ago? What else should a minimalist DBA know about?
What do you think are the minimum skills a person should have before they are allowed to manage a database? Does it matter whether or not it’s a production database? Does it matter how much data is there? What kind of data? Is recovery a goal or a symptom? Does it matter how old you are? Or how old the database is? What is the meaning of all this anyway?
Thomas LaRock ( blog | @sqlrockstar ) and I will be talking about what a Minimalist DBA is, what skills we think they need, and how to ensure that they have them on 3 December at Noon EST for the DBA Fundamentals Virtual Chapter of PASS.
Every profession has a core set of responsibilities that are expected of every practitioner. For anyone that has the letters “DBA” in their job description their job function is a black box to anyone on the outside. "What do you do here?" is a common question for most DBAs.
Some DBAs are a part-time data modelers, SAN admins, VM admins. Sometimes they know all about security, or Active Directory, or .NET. It differs from one shop to another. Whether it is day one or one hundred in your career as a DBA you need to make certain you stay focused on your core duties. If you slip up then you will find out why DBA often stands for Default Blame Acceptor.
Attend this webinar to make sure that no matter what your level of efficiency and laziness you are able to focus on the bare essentials (the minimum) necessary to be a Rockstar DBA."
Karen Lopez is a senior project manager and architect for InfoAdvisors. A frequent speaker at conferences and local user groups, she has 20+ years of experience in project and data management on large, multi-project programs. Karen is a chronic volunteer, a SQL Server MVP, and an active advocate for science, technology, engineering, and mathematics (STEM) education and data quality. She isn’t a DBA, but loves to talk and debate about the effectiveness of lazy DBAs. She isn’t sure if the minimalist thing is a strength or an excuse.
Thomas LaRock is a Microsoft Certified Master, a SQL Server MVP, a VMWare vExpert, and a Microsoft Certified Trainer with over 15 years’ experience in the IT industry in various roles such as programmer, developer, analyst, and database administrator. He is also the author of “DBA Survivor: Become a Rock Star DBA” (http://dbasurvivor.com) and has participated in the technical review of several other books.
Currently, Thomas is a Technical Evangelist for Confio Software. This role allows for him to work with a variety of customers to help solve questions regarding database performance tuning and virtualization. Thomas also serves on the Board of Directors for PASS as Vice President of Marketing. You can find out more information about him at his blog: http://thomaslarock.com/resume/.
You can probably expect our usual level of snark, debate, levity and great info for this presentation. Bring your ideas and snark, too. I always ensure that the audience is part of the presentation, so expect more the a slew of bullet points and demos. And even though this is hosted by a SQL Server organization, all we will be talking about will be applicable to multiple platforms. That’s how real enterprise database systems are anyway, right?
You’ll need to register, but it’s free. By the way, if you also register on that site, you’ll become a member of that chapter. And that’s free, too.
Thursday, 24 October 2013, 2PM EDT http://www.dataversity.net/oct-24-webinar-big-challenges-in-data-modeling/
In this month’s Big Challenges in Data Modeling #BCDModeling webinar we’ll be tackling the issue of working with models purchased or borrowed from third parties. This includes standard models, modeling patterns from books, and models inherited with software packages.
Have you ever considered using pre-existing pattern models to jump start your database projects? Have you considered purchasing proprietary models? Did you know that there are hundreds of models available to you for free or for minimal cost? In this month’s Data Modeling Challenges webinar, we discusses some of the benefits and gotchas of working with acquired models – industry standard models, patterns, and other universal model concepts.
We will chat about:
· The costs, benefits, and risks of working with industry standard data models
· The benefits of using industry standards in your package acquisition projects
· Choosing the right process
· Myths in working with pattern models
· What you should know before committing to project plans and estimates
· Lessons Learned
· …and whatever you, attendees, want to chat about. It’s a conversation, not a presentation!
My panelists will be Paul Agnew, co-author of The Data Model Resource Book, Vol 3 and David Hay, author of Data Model Patterns, and YOU, the attendees. Unlike many other webinars, you can participate in the discussion by chatting with each other, as well as asking formal questions to the panelists.
While the formal part of the webinar begins at 2PM EDT, you can join early to start the chat while we go through some sound checks and pre-show rants. Also, some of us will stay on for about 15-20 minutes “off the record”. You can also ask questions on Twitter via the #BCDModeling hashtag.
Registration is free, but you do have to register to get into the webinar.
See you soon.
Sunday Yanni Robel (@yannirobel). Rob (@projmgr) and I (@datachick) will be running the Portland Marathon. Yanni has done so many I can’t keep track.
Tonight we did the pasta dinner are now hoping to get a good sleep.
This is my second full marathon and Rob’s first. So this is where you can help. We all us Runmeter, an app that will not only track and tweet our progress, it will also read your tweets and Facebook posts to us as we run.
Today Yanni showed me she had selected a sexy French voice to read your messages. Just so you know.
I can’t even begin to explain how much hearing your support helps during a race.
You don’t have to install anything. All you have to do is tweet at us. There are just a few things you need to know:
- We can only hear tweets directly tweeted to us, with our twitter IDs right at the beginning of the tweet.
- That means that you will need three separate tweets to talk to all of us. If you mention more than one of us, only the first person will hear the tweet.
- We won’t hear retweets.
- We will probably set our apps to tweet our progress every 2 miles or so. If you reply to those, we will hear your tweet.
- You don’t have to include anything else in the tweet. No need for the Runmeter ID or a hashtag.
- We won’t hear DMs or private messages.
- Status updates also go to our Facebook walls. You can also talk to us there, too.
- I am slow. I will take more than 6 hours to finish. You can sleep in and still help.
- Our corral will probably start at 7:15 -7:30 or so AM PDT. But you don’t have to cheer us only as we start. Messages later are appreciated a lot.
I hope you can help us along the way. Even if you can’t, sending good vibes are also appreciated.
And thank you to all of you who supported us during our training runs.
See you on the other side of 26.2 miles. Upright and smiling.
Starting today I will be visiting CERN, the Conseil Européen pour la Recherche Nucléaire with 11 other STEM social media advocates. What is CERN? It’s the location of the Large Hadron Collider and the birthplace of the World Wide Web. From the CERN Website:
At CERN, the European Organization for Nuclear Research, physicists and engineers are probing the fundamental structure of the universe. They use the world’s largest and most complex scientific instruments to study the basic constituents of matter – the fundamental particles. The particles are made to collide together at close to the speed of light. The process gives the physicists clues about how the particles interact, and provides insights into the fundamental laws of nature.
I will be sharing facts, images and videos via this blog and other social media.
I will be tweeting about this event a lot using the hashtag #CERNTweetup. If you aren’t interested in this sharing, you can use the filtering mechanism of your Twitter client to avoid those tweets.
…or your can use the search feature of your client to follow the tweets of all the invitees. Isn’t metadata great that way?
Subscribe via E-mail
- Doing It Right: Performance Monitoring and Troubleshooting - SQL Server - SQL Server - Toad World on 10 Tips for the Minimalist DBA
- Doing It Right: Performance Monitoring and Troubleshooting - SQLRockstar - Thomas LaRock on 10 Tips for the Minimalist DBA
- Robert L Davis on Trolling the #24HoP
- Cindy Gross on Strutting: We all Know When You are Doing It. So Stop.
- K on 10 Things I Hate About Interviewing with You–Follow Up
- December 2013 (1)
- November 2013 (1)
- October 2013 (3)
- September 2013 (3)
- August 2013 (2)
- July 2013 (4)
- June 2013 (5)
- May 2013 (7)
- April 2013 (5)
- March 2013 (4)
- February 2013 (7)
- January 2013 (12)
- December 2012 (2)
- November 2012 (3)
- October 2012 (3)
- September 2012 (13)
- August 2012 (5)
- July 2012 (17)
- June 2012 (2)
- May 2012 (4)
- April 2012 (4)
- March 2012 (8)
- February 2012 (11)
- January 2012 (3)
- December 2011 (10)
- November 2011 (8)
- October 2011 (5)
- September 2011 (3)
- August 2011 (9)
- July 2011 (5)
- June 2011 (5)
- May 2011 (5)
- April 2011 (9)
- March 2011 (4)
- February 2011 (9)
- January 2011 (8)
- December 2010 (15)
- November 2010 (27)
- September 2010 (2)
- August 2010 (1)
- July 2010 (4)