Mike Walsh 
It’s day four of the two weeks to a healthier SQL Server series. If I were making this ten-day plan even just three years ago, I would have had this lower on the list. With the security and compliance needs of the world today and the way Microsoft services SQL Server – it’s important to … Read more
When I decided to go off and join the world of SQL Server consultants, I wrote a blog post. Eleven years ago I wrote this post. It was an urge to myself, and a call to others. It’s one of my favorite two blog posts I’ve ever written. That’s germane to the topic here. In … Read more
A monster’s worse fear is being found. – Richelle Goodrich This is part of the Two Weeks to a healthier SQL Server series. Today we’ll address SQL Server Corruption – or hopefully how to find and deal with it before it finds and deals with you. Data loss and user deletes are expensive and difficult. … Read more
I held my breath and opened Twitter today. I scrolled around and somehow landed on a tweet from Casey Toner of a media watchdog group in IL. He saw something that seemed a little odd over there at Inc. It seems there were a bunch of articles with similar headlines. All seemingly having to do … Read more
It’s 5 AM on Wednesday. Your CIO has called your cell phone at home. “We need you to log in right now! Someone or something deleted all of the inventory. I tried to help out the team right before the inventory disappeared, and I was running some SQL commands I found and a couple of … Read more
Give me six hours to chop down a tree and I will spend the first four sharpening the axe. Abraham Lincon Welcome back to the Two Weeks to A Healthy SQL Server series of posts! This is the official “Day One” post. This first step may not be the most glamorous or the biggest payoff, … Read more
Many companies have the wrong people managing their databases. It sounds mean, out of context. But note we didn’t say “bad people” or “mean people,” just the wrong people to ensure a healthy SQL Server. Sometimes it’s even worse than that. It’s not the wrong person, it’s “no person.” Nobody owns its uptime, recoverability, or … Read more