Things I Know Now


I was tagged by Joe Webb for this question circulating through the inter-tubes.

Joe and I shared a cab to the airport after the PASS Summit 2008. If you’ve never had the opportunity to share a cab with Joe, I highly recommend it. He’s one of those people. You know the type – they talk to you for a few minutes and impact the rest of your life in a positive way. A way that still has you thinking months later. Thanks Joe.

My List

Well, I have to admit I saw some good stuff when following the links to others who’ve answered this question. I’m going to repeat some of theirs here, but only because I’ve learned (usually the hard way) the same thing.

1. Learn constantly. There are fields out there where you can get trained and then do that work most of your life without having to learn much more. Database work is not one of those fields. Plan to spend some of your time – your own time – keeping up with what’s new and on the horizon.

I’m not asking you to fall instantly in love with every new feature you encounter. That would be absurd. But equally absurd is dismissing every new feature – especially the stuff you don’t understand or cannot think of a good use for at the moment. Features are added for a reason. Most of them are good reasons, at least to someone. It might not be for you, but will it kill you to learn something new? If I don’t understand it, I can’t use it – ever. If I do understand it, it becomes another tool in the toolbox.

2. Dream big. I was struggling with my new career as a DBA. I felt I was in over my head and, any minute, I was going to be discovered and fired. I am not making this up. About the time I attended the PASS Summit 2004 I got a few successes under my belt – enough to feel more secure in my job but not enough to convince me I knew anything about very large databases in SQL Server.

It was The Year of the Storms in Florida. Orlando looked like it had been bombed. It was ugly, but the conference went on. I stood in line at the hands-on labs to meet Ken Henderson. I was devouring The Guru’s Guide to SQL Server Internals and Architecture along with Kalen Delaney‘s SQL Server 2000 Performance Tuning Technical Reference. I credit both authors with saving my career, incidentally.

I heard Ken dispensing no-nonsense advice to people. I think some thought to “teach him a thing or two,” and he respectfully but firmly resisted this with the gentleman in line in front of me (poor guy). I was next, and was probably visibly shaking in my shoes. I explained to Ken that I was pretty new to large SQL Server databases and was a web developer that had been thrust into a new position at work. I told him about my approach – relying on my engineering training and testing heavily – and explained the symptoms I was seeing. Ken made a few excellent suggestions, which I wrote down and which, unsurprisingly, put me right on top of the issues I was describing. I thanked him profusely and started away. He said “Hey, you’re approaching this like I would.”

I felt like the kid on the old Coke commercial – the one where Mean Joe Greene throws him his jersey. I know it sounds cheesy, but I entered that room as a guy learning databases and left it a database professional. The difference for me was the confidence that I was approaching this problem like Ken Henderson would.

3. Live transparently. I blogged about this recently but it bears repeating. Treat others like you want to be treated, in public and private. Work hard. Admit your mistakes and do everything you can to correct them and mitigate the damage – all as soon as possible. Help as many people as you possibly can. Don’t lie. When the honest answer is “I don’t know,” lead with that – you can tell folks your best guess after stating you don’t know. It’s ok, no one knows it all.

4. “If it was easy…” My Granny used to say “If it was easy, anyone could do it.” (This was the same lady who told me “Son, God gave you a [backside] so you’d have somewhere to land when you fall.”) I’ve experienced failure and I’ve watched others experience it. It ain’t pretty and it’s no fun to live through or deal with. Bad things happen when people fail. That’s a fact. But you’re not judged by how many times you fall down, in my opinion and estimation; you’re judged by whether you get up or just stay there.

Get up.

If nothing else, you now know at least one thing that doesn’t work. Use that. Leverage it. Build a way that will work from it’s ashen rubble. Don’t just sit there on your ash.

5. Take good advice. A good skill to cultivate is the ability to recognize good advice when you hear it. Note: You may not want to hear good advice. I can guarantee you it’s unpleasant when you’ve messed up.

I’m blessed to be surrounded by people who care about me enough to tell me “Andy, that was a mistake.” When they do, I usually don’t want to hear that. But I recognize the motive and hear the heart, and know it’s good advice.


That’s all I can think of for now. There are no magic formulas or guarantees in life. These are the things I’d share with my younger self if I could write a letter to me and send it back in time.

:{> Andy

Andy Leonard

Christian, husband, dad, grandpa, Data Philosopher, Data Engineer, Azure Data Factory, SSIS guy, and farmer. I was cloud before cloud was cool. :{>

3 thoughts on “Things I Know Now

  1. Excellent article — I needed a shot of confidence this week, so the timing is good for this one.  Thank you very much!

Leave a Reply

Your email address will not be published. Required fields are marked *

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