Steve Jones (t|b) wrote a blog post talking about the death of the title Database Administrator.Mind you, he was talking about the title of DBA, not the actual job of being a DBA. Semantics, right? If you look across the inter-webs, the death of the DBA has been a favorite on the tech prophets for a long time.  It seems to be an odd prophecy given the ongoing explosion of data being generated. In fact, it’s a reported 2.5 Quintillion Bytes of Data Created Daily. Is that accurate? I have no idea. I’m not sure how you could measure something like that. 2.5 quintillion is 2,500,00 terabytes. To be completely honest, I’m not sure how big that is. 250 zetabyte? 2.5 yoddabyte? Ya, no clue.

More false predictions?

Yes, the death of the DBA has been falsely predict for years, maybe even decades, this is true. Falsely predicted because the prediction is that the role of the DBA will no longer be needed in the traditional sense. Well, these days that prediction could be closer to reality. With the focus on the cloud, DBA’s will no longer be responsible for hardware or even possibly backups, which is going to leave DBA’s with a lot of time on their hands. So unless they want to retire or change careers completely, it means DBA’s are going to have to evolve.

Evolve? Evolve into what? My guess would be if you’re a DBA now, you better start brushing up on your development skills. DBA’s will always be needed, but I think the job is going to transform into more of a development type role. I think the continued push of the DevOps movement into the DBA world is going to be the driving force. Even if you don’t move out to the cloud, you’re still going to be treating builds as deployments.Of course there is also the Data Analytics and Data Science routes.

I suppose when you start seeing big names in the community starting to make moves, you should start considering your options. In July, Thomas LaRock announced his drift towards Data Science. That Brent Ozar guy gives a couple of interviews discussing some of these issues as seen below. All that being said, if you are happy working with data than you need to take a proactive approach in your career. It doesn’t matter what stage of your career your in either, you still need to get out in front of these new trends.

 

 

Some times I just want to kick myself. A very simple concept that I never thought about applying to work, I was bouncing around the internet trying to get a better understanding of how to use source control with my script library when I found a rabbit hole.

The rabbit hole in question was of the “How to write better code” / “How to be a better developer” variety when I came across an article about keeping a journal for programming. In fact, it was this article.

Dammit. Why hadn’t I thought of that sooner? I suppose it follows the advice about posting articles/resources on your blog for you to search against later. It just hadn’t occurred to me to keep a journal discussing ideas that weren’t ideal for blogs for various reasons.

 

#tsql2sdayThe 101st addition to the SQL monthly blog party is being hosted by Jens Vestergaard (b/t). For the topic this month, Jens has asked which tools are essential to our daily job. Or rather, which tools do I depend on as a DBA.

Interesting Topic

I would love to say I noticed the invitation last week and had an idea already in place. I would like to say that, but  I would be lying. In a moment of serendipity,.I’m testing my individual DR solution today How effectively can I work from a borrowed workstation. You’re probably sitting there thinking, “Wow, someone out there actually tests how to work from a borrowed machine? That’s hard core!”. While, I would suggest asking yourself what would you do if your main workstation become unavailable while you’re on call and have a plan in place, this isn’t that. I simply was to preoccupied this morning to realize I had forgotten my laptop bag.

So today, I’m thinking about how much I miss my work environment Things like:

  • NotePad++ that I use as a text editor and scratch paper.
  • My local script repo
  • Reference docs/ebooks I keep on the hard drive
  • SQL prompt
  • SQL Search

I also miss how I have various apps configured for my personal preference. But I’m also thankful that I have cloud tools like OneNote and LastPass that make this more bearable. Signing into Mozilla got me access to my bookmarks.

What this is teaching me

I am quickly realizing having my documentation/ebooks and scripts available in some kind of repository would be greatly beneficial (Why yes, I am embarrassed I haven’t put those scripts in a repository). It is also making me realize how dependent I am on a laptop that could fail or be stolen, and just how disruptive it is. So I will be working on a plan to resolve that.

I am also going to make sure I place my laptop bag in a more obvious spot before I walk out the door.