Recently we had Microsoft Risk Assessment Program (RAP) completed on some of our SQL Server instances. This is where Microsoft deploys some software that performs a similar function to when you go to the doctor for an annual physical. There’s a lot of poking and prodding, they draw samples, and at the end they tell you everything that is wrong. Your servers have high blood sugar, your databases need to take up yoga, etc. It’s pretty much everything except having the MS technician stroke his chin, saying “Hmmm.”
You are going to a doctor for a regularly scheduled checkup, right? Ok then.
I have a confession to make: Historically speaking, I don’t like deployments. I dread them with an unavoidable pessimism that asks “so what is THIS going to break?”
Now, I have worked with a lot of smart people who knew how to write some fabulous code. I don’t doubt that one bit. But I’ve also worked in several places where that code wasn’t rigorously tested before it was time to be deployed in Production. Maybe the business wanted a fix deployed immediately. Maybe the deployment instructions were incomplete. Maybe velociraptors invaded your workplace.
For most of my career I’ve been the only DBA, which means each and every time one of my colleagues encountered a perception that the database is slow, they would form the words “Hey Jeff. . .” As Stan Lee said, with great power comes great responsibility. Which is another way of saying in times of strife, both real and imagined, your Inbox and Voicemail get flooded.
If you’re a DBA, you probably secretly wish that you could have one of those cool red and black portrait graphics like those folks at Brent Ozar Unlimited get. But that’s not important right now. You probably also enjoy the privilege of performing the installation of every new SQL Server instance. And if you don’t, well, you can still keep reading, I guess.
Hey, I’m new at this SQL blogging stuff. I’m still working out the kinks.