This week I discuss a question that I’ve gotten in many forms over the years - a lot of the scenarios are so specific that it’s hard to keep them anonymous, but they can be generalized as a bigger problem: how do I deal with being responsible for things that I can’t fully control?

DBAs have huge responsibilities, so this is a common, frustrating scenario. In this episode, I talk about a few times that I’ve experienced this in my own life, what techniques didn’t work, and what strategies were more effective.

Subscribe: If you’d rather listen on the go, subscribe on iTunes or plug this URL into your favorite podcasting app: http://dearsqldba.libsyn.com/rss#

My notes for the session

Everyday Dilbert Moments

The Bug Nobody Caused

Committing to an SLA I couldn’t meet

The Case of the Weak KPIs

Techniques That Haven’t Worked for Me

“No” “This is not my responsibility” “-TICKET CLOSED”

If other people keep tagging you and saying “you’re it”, just saying “not it” or “I’m not playing this game” doesn’t stop them from continuing.

Techniques That Can Work

First: Chill

Being responsible for things you can’t control frequently triggers stress

Stress triggers knee-jerk responses

• Knee jerk responses don’t go anywhere
• Not taken seriously
• Generally don’t have thoughtful, supporting data

You need to be more strategic

Find a Way to De-Personalize the Issue

Think outside your current role

If you were the CTO of the company, what would you want to see happen?

Don’t limit your thinking to what you can do now

Do What You Can

Outline and document the limitations to what you’ve done

“Here’s what I can do for you” (even if it’s to try to help escalate)

Sometimes… Sketch Out an Approach to Narrow the Gap

Even if it’s not you who could carry it out

Ask for help to narrow the gap

Who do you think could help make this happen?

Raise the Flag High When Needed

Security risks

Risks of data loss

Ethics breaches