Everyone has seen the meme that the cloud is just someone else’s computer. Or that people don’t understand the cloud. I think either has become too simplistic of an explanation. The fact of the matter is, we all have embraced the cloud in some fashion.

cloud outageThink about our Google or iCloud drives that we save documents, music, or photos to. How many of us subscribe to a music app that delivers music over the net? Streamers? Do we have TV streamers around? The cloud is taking over for sure. It’s starting to become the platform of choice in business. It’s fast to ramp additional resources, it simplifies the infrastructure, and all you need to do as the consumer is to feed it money.

No ground under the cloud

What happens to your music, documents, pictures, or SQL server if the internet is down? Or there is an outage because not only did a fiber line get cut, but the electrical grid had a massive failure? How resilient is the cloud then? What’s the cost associated with that outage and is it worth it?

Obviously the cloud is here to stay….but jumping all in may not be the best practice either. As a DBA, I always work at leaving myself an out. If code goes bad, a server crashes or some other unplanned nuisance rears its ugly head, I generally have an alternative in mind. We should be adopting that same strategy with the cloud as well. If Amazon, Azure, or someone else goes down for an extended time…..what’s the fall back plan other than just being down? In other words, do you have a parachute, and is it working?

#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.