SQL Server Blog

SQL University – Troubleshooting Week

I was about to write another bunch of comments on why I think troubleshooting skills are important. I’ve changed my mind – I’ve done that before. So let’s start SQL University Troubleshooting week off with a couple reminders from past posts that say what I wanted to say this week already.

If You Can’t Troubleshoot – Don’t Apply –> I relate the experience of finding and repairing a broken starter to IT troubleshooting skills. Seriously, if you can’t troubleshoot, don’t apply to work with me. Read on to see why.

Avoid Using Those Troubleshooting Skills –> Sometimes the best troubleshooting is the kind you don’t have to do because you did it right the first time.

Troubleshooting Methodology – Get One –> This was one of my very first blog posts a few years ago. I think it still rings true

Jorge is also posting this week and I’ll hope to get some more out soon but for now, ask yourself if you can troubleshoot. Ask yourself if you exhibit any of those shotgun troubleshooting methods. Then figure out what you can do to fix it.




Mike Walsh
Article by Mike Walsh
Mike loves mentoring clients on the right Systems or High Availability architectures because he enjoys those lightbulb moments and loves watching the right design and setup come together for a client. He started Straight Path in 2010 when he decided that after over a decade working with SQL Server in various roles, it was time to try and take his experience, passion, and knowledge to help clients of all shapes and sizes. Mike is a husband, father to four great children, and a Christian. He’s a volunteer Firefighter and EMT in his small town in New Hampshire, and when he isn’t playing with his family, solving SQL Server issues, or talking shop, it seems like he has plenty to do with his family running a small farm in NH raising Beef Cattle, Chickens, Pigs, Sheep, Goats, Honeybees and who knows what other animals have been added!

Subscribe for Updates


Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Share This