In theory, before you introduce a new system - database server, load balancer, virtualization infrastructure, etc - you build a robust runbook that documents how you'll handle every conceivable scenario. When there's any kind of failure, you'll simply turn to chapter X and start going through a precise checklist that will guide you to the promised land of uptime.
When you run into problems at work, how do you tell your manager what you did? Typically you would write up the problem, the solution, and a quick summary of the outcome. If you're like me, this isn't a lot of fun. And, if your manager is anything like most managers, they don't want to read a summary of the problem, your actions, and try to figure out how big or small of an impact you had.
You need to poop. Maybe not right now, but in general, you need to breathe, eat, drink, sleep, and poop. If you can't do any of those things, then the rest of your needs will take a back seat until you can accomplish the basics.
Psychology professor Abraham Maslow designed Maslow's Hierarchy of Needs to illustrate how us meatbags prioritize our daily tasks. It's usually visualized with a pyramid:
When I want to check out a piece of software, one of the first things I look for (after the price tag) is the support matrix. I want to know what versions of SQL Server and Windows they support. I lined that up with the available machines I had in-house, picked the right platform, and got started.
In a recent webcast on disaster recovery planning for small businesses, I talked about building a bug-out bag.
Every IT professional should have a bug-out bag in the trunk of their car with enough stuff to let them hit the road for 24-48 hours straight. This gear helps you react more confidently to minor problems and major disasters. Here's what I've got in my bug-out bag:
All databases are not created equal. Learn how to find greedy databases - ones that are using up more IO than others - and learn what options you have for reducing their loads.
