Your effectiveness and success on the job depend so much on your ability to solve problems. In fact, you get paid to solve technical problems every day. Effective problem solving is a very important skill as a SQL Server DBA and IT professional, isn’t it?

But . . .

How many times have you faced a technical problem and spent too much time analyzing it? Despite having dealt with something similar before? But you’re not making any progress. You’re stuck, trying to figure out what you’ve been doing wrong and why you cannot solve this problem. Even when you have the right experience and skill set to solve it.

What’s worse is when you are running out of time and your boss is bugging you for updates. Yet you’re terrified to provide any response. Because you don’t want him to find out that you couldn’t figure out a solution. Remember that outage you were trying to troubleshoot while your boss kept asking?

It happens to the best of us – even the smartest DBAs and senior, more experienced engineers. And when it does, it affects your confidence until you’re wasting time trying to research the right solution. And the one solution you think is going to solve it ends up crashing the system or causing performance issues.

On this episode of the Practical SQL Server HA/DR Show, I talk about the how your problem solving skills can cause more problems if not done right.

I’ll be doing this on a weekly basis so make sure you keep an eye out for announcements on my social media profiles (LinkedIn | Twitter | YouTube)