I Didn’t Hyperventilate!

I gave what is officially my second presentation this week. I presented at the Triad SQL BI (Twitter | PASS) user group meeting and I didn’t hyperventilate! That’s a huge deal for someone like me, who is petrified of public speaking.

It started out a little rough though.

Timeline
Friday, 8/22 (just 4 days before presentation date) – I met Katherine Fraser (SQLSassy) for lunch and she mentioned that their scheduled speaker had just cancelled on them the day before. I asked her what she was going to do and she said unless I wanted to present for her, she had no idea. I jokingly said, “Yeah, sure, I’ll present”. Do not EVER, tell a chapter lead you will present, even if joking around because they will pounce on you! Lesson learned there. I agreed to present a very introductory session on SSIS. I then went home and started to panic.

Saturday, 8/23 – I woke up with a horrible sinus headache and thought I was in the beginning of nasty sinus infection. Now I really started to panic. I sent Martin to the drugstore to buy every sinus medication they had on the shelf. There was no way I could be sick, I could not cancel on Katherine after I had just agreed to present the day before. I proceeded to pound down some Emergen-C and drink about a gallon of water an hour for the rest of the day.

Sunday, 8/24 – I woke up at 4:30 a.m. to take part in the upgrade of major system at work. I felt about the same as Saturday. I pounded some more Emergen-C and worked until 11:30am. After we got the green light from the testers at 3:30 p.m., I went to bed and collapsed.

Monday, 8/25 – Woke up feeling much better, but not great. Pounded more Emergen-C. Started to work on my presentation. Did I mention that I didn’t have anything prepped for a presentation? I’m not a speaker, why on earth would I have a presentation ready to go? Got a call from my boss that the system upgrade wasn’t going so smoothly and had to start firefighting in production.

Tuesday, 8/26 – Presentation day. Got the word from my boss that the system upgrade was still up in the air, but none of the pieces that were broken were anything I could help with or fix. I started to work on my presentation. Just before lunch time I was told I had two conference calls I needed to participate in. Great, another two hours I don’t get to work on my presentation! Finally done with conference calls, when I got a call from my boss, we are rolling back the upgrade and I need to bring the old server back online. Luckily I had been able to create the content of the presentation and test it. I just didn’t have any time to do a practice run through. That was going to have to be enough, it was time to go to Winston-Salem.

I arrived in plenty of time, but I forgot: the power supply for my laptop, my external mouse, speaker evaluation forms and my list of things I needed to take with me to the meeting. Luckily my laptop was fully charged and didn’t die during the presentation (in fact I could have gone on for another 2 ½ hours, thankfully no one wanted to stay that long!). A mouse was provided by our wonderful host, Matt Clepper of Inmar, but not before I had a slight mishap using that @!#$%^& embedded mouse on my laptop. Katherine was well prepared and brought speaker evaluation forms. As for my list of things I needed to bring with me, well, I just had to “adapt and overcome”.

The presentation went pretty well, I didn’t hyperventilate. Sometimes you have to have a very simple goal, just survive without a trip to the ER.

Wrap up
Overall it was a good experience. I think I did a good job of presenting and the feedback I got reinforced that. There were some great ideas on what I could have done better and some great comments on what I did well.

Will I speak again? Probably. I’m not sure I’m ready for a SQL Saturday quite yet, but maybe another couple of times at UG meetings and I’ll think about it. A huge “Thank you” goes out to Katherine for taking a chance and believing in me.

Of course I didn’t sleep at all Tuesday night. I kept thinking, “I forgot to tell them…”

Disheartening Apples

Question:  How many Oracle DBAs can you fit in Madison Square Garden?

Answer:  None, their egos won’t fit through the door.

No, this blog is not a slight towards Oracle DBAs.  I have several friends who are Oracle DBAs and they are some of the nicest, most humble people you will ever meet, but in my experience, they are the exception.  Early in my career I had to administer Oracle and the person I was supposed to learn from was a hard core Oracle DBA and had been for years.  Probably one of the smartest people I’ve ever worked with but only barely tolerable to be around because his ego was larger than the Goodyear Blimp.  When I was introduced to SQL Server way back in 1996 (yes, I am dating myself), there really weren’t any experts in the field readily available when questions came up.  The internet was just starting to flourish and Google hadn’t even been invented yet.  There were a few guys that I had heard of that were willing to help, Brian Knight, Andy Warren & Steve Jones.  I knew about them because Steve Jones was a local guy in Denver, where I was living at the time.  They created this thing called SQLServerCentral.com.  These few are the epitome of SQL Server stewards, for both knowledge and professionalism.  Smart, humble, easy going, willing to share knowledge freely and did I mention smart?  Honestly, they have been my role models for “lifting as you climb” in my career.  Okay, now I sound like some creepy stalker, so we’ll move on to the point of this blog.

For those that know me personally, you know I am not a speaker type, so I give back to the SQL community by volunteering behind the scenes in any way I can.  So when I was selected to work on the program committee for PASS Summit 2014, I was so excited I did a little happy dance in my cube at work.  My co-workers are used to seeing my head bob to the music of my headphones, but seeing me do a happy dance was a little startling for some.  This will be my 5th year on the committee, more specifically the abstraction review team.  I love being on the abstract review team, getting to read what people are passionate about teaching is always so exciting.  It kick starts my love of SQL Server and learning.  However, just because I had been on the committee in previous years, I never assumed I would be selected again.  It is such a privilege to be chosen, and trusted, with this huge task.

Recently there has been a lot of chatter in social media about the selection process (or lack thereof according to some).  It saddens me to see some people’s true colors.  Being chosen to speak for any engagement, not just the PASS Summit, is a privilege, not a <insert deity here> given right.  The selection process has improved over the years and has become more streamlined thanks to the investment made by the PASS IT team.  It still has room for improvement, but most things do.  One of the things I like best about this year is the increase in the amount of time we have been given to review the abstracts.  In years past, we’ve had a very small window in which to review the abstracts.  That small window made it very difficult to coordinate team members’ schedules to discuss final rankings and assign rejection reasons.  I am hoping we can do a much better job this year of providing useful feedback to speakers.  Another improvement that was implemented last year was the removal of the speaker from the abstract.  This is a huge deal.  In years past, we could see who submitted the session and I fear that it swayed team members’ opinions of abstracts, both good and bad.  Some would be chosen because they were “well known” speakers and/or authors, it didn’t matter that their abstracts were poorly written, which in my experience often translated into poorly presented sessions.  Some would be excluded for the exact same reason.   As a speaker you need to have enough respect for your audience to provide them with the best written abstract you can, it’s the surest sign of respect.

I congratulate all those that have submitted sessions for the Summit; it’s a huge step just submitting a session for the PASS Summit.  If you are selected to speak, I ask that you remember that it’s a privilege and an honor and that you treat those attending your session(s) with the respect they are due.  If you are not selected, I ask that you not give up.  If you have questions about why your session was not selected, ask.  I have been asked in the past and am always glad to provide additional feedback.

Question:  How many SQL Server DBAs can you fit in the Seattle Convention Center?

Answer:  Unlimited, as long as they remember why they attend and/or speak at the PASS Summit.

Saving Grace

According to Merriam-Webster the definition of grace is:

1a : unmerited divine assistance given humans for their regeneration or sanctification; b : a virtue coming from God; c : a state of sanctification enjoyed through divine grace; 2a : approval, favor <stayed in his good graces>; b archaic : mercy, pardon; c : a special favor : privilege <each in his place, by right, not grace, shall rule his heritage — Rudyard Kipling>; d : disposition to or an act or instance of kindness, courtesy, or clemency; e : a temporary exemption : reprieve; 3a : a charming or attractive trait or characteristic…

That’s quite a lengthy definition; in fact, I captured less than half of what was in the dictionary.  It seems like a lot of words to describe something so simple.

So what does grace have to do with a blog about SQL Server?  Quite a lot actually.

When I first went to college, I wanted to be a teacher; in fact, I wanted to be a math teacher.  I had this great math teacher who inspired me in high school.  He was not only brilliant, but he was infectious with his desire for learning.  He was a young guy, I think it was his first teaching job, but you could tell that teaching was what he was meant to do.  He would explain things in a way that made sense (that’s a gift when teaching high school sophomores abstract algebra).  If he could see that the class was completely lost, he would change mid stride and go a completely different direction.  I don’t think a single person failed that class, he wouldn’t let them.  He was the definition of grace, “..disposition to or an act or instance of kindness, courtesy, or clemency…a charming or attractive trait or characteristic”.

There was another math teacher in my high school.  He was old (probably forty or something crazy like that) and a bit pompous; he had the letters “PhD” behind his name.  His attitude was that he had the credentials, so if you didn’t understand what he was talking about, maybe you didn’t belong in abstract algebra.  He also had a reserved parking space close the entrance, because he had those three little letters after his name, “PhD”.  He was the exact opposite of grace and almost half his class failed.

The point I’m trying to make is that for some people, their driving force is ego, not love of learning and therefore they have no grace.

I recently attended the SQL Saturday event in Atlanta.  I love these events because they are so personal.  You have smaller classes and you can actually interact with the presenters and most of them are just like you and me, regular people.  However, in Atlanta I noticed a very disheartening trend.  Ego is taking hold and grace is losing ground.

I am not a speaker and I never will be.  I have a horrible phobia of public speaking (which is the reason I didn’t become a teacher).  But I want to give back to the community that has helped me get where I am today, so I volunteer behind the scenes for many things.  Atlanta was no different.  I was attending, but I was also a volunteer.  There were some great nationally and internationally known speakers presenting, in addition to the local and regional people and it was so exciting to be part of the largest SQL Saturday event to date.  As it turns out, it was probably the most disappointing PASS event I’d attended to date.  Not because I was disappointed in the content of the sessions I attended or even in the speakers that presented them, but because there were many other speakers who seem to have lost their grace.

I’m not going to give specific examples or name names (that just elicits finger pointing).  But what I am going to do is ask you, as a speaker, why do you do it?  Is it because you have those three little letters, “MVP”, after your name or is because you want to share your knowledge and inspire others to learn more?  If it’s the latter, I applaud you and ask that you keep on doing what you are doing.  We in the community appreciate all your hard work and your generosity in sharing.  If it’s the former then I might suggest you try to save grace and have a slice of humble pie, it never hurt anyone.

Angela Henry

@SQLSwimmer

Certifiable?

I have recently begun to contemplate pursuing the MCSA Certification.  I have been working with SQL Server for almost 20 years and have never considered getting a certification before now.  I have met so many people through the years who have the certifications and were quite frankly “dumb as a box of rocks”.  They just happen to be good at regurgitating information on an exam but had no practical experience.  Throw them an unusual situation and they stare back at you with blank eyes.

I know having those extra letters behind my name could give me a boost if I was in the job market, but I’m happily settled at my current employer, with no plans to move on.  I realize that anything could happen and I could be out looking for a job tomorrow, but if that were the case maybe I could have used that $450 I spent on certification to pay for groceries.  I am not saying the tests should be free, but it is a hard pill for me to swallow when I’ve managed just fine without those letters after my name this long.

Who knows, I may have missed opportunities that I didn’t even know about because I didn’t have those letters, but how can you miss what you’ve never had?

The Long and Winding Road

TSQL2sDay150x150

“The Long and Winding Road” is one of my favorite Beatles songs, it reminds me of my dad, he was a huge Beatles fan.  My dad passed away almost five years ago, but I still miss him like it was yesterday and I still remember the advice he gave me when I was a kid, “Work hard and don’t let anybody tell you you can’t do something, there’s always a way.  It may not be easy, but there’s always a way.”  I credit that advice for the success I’ve had in my life, both personal and professional.

I started working with SQL Server back on Windows 3.11 (version 4.21a).  I know I’m dating myself here, but that’s kind of the point of this post.  We thought Windows 3.11 was so cool after having to deal with DOS for so many years, we didn’t think it could get any cooler.  But it did.  We got Windows 95, then 98, XP, 7 and now 8.  I can’t wait to see what they come up with next.

The same goes for SQL Server.

We started out with what I thought was a great tool, then they made it better.  We went from having to create devices to hold our database files and keeping track of each file growth, to just being able to create our database files and let them grow on their own.  I don’t know about anybody else, but that made me so happy.  No more sp_helpdb every night to make sure I could recreate my databases if needed in a disaster.

It used to be very hard to write T-SQL code if you weren’t familiar with the database objects, the old iSQL query window didn’t have an object browser so you couldn’t see a list of your tables, let alone column names.  Now we have intellisense built right in to the query window.  This feature alone is with worth its weight in gold.  It allows me to be so much more productive, type the first few letters and hit tab.  “BAM!” as Emeril would say.

BCP really used to be the only way to get data in and out of your database, then they gave DTS.  Once again it’s like going from DOS to Windows.  Then they came out with SSIS.  Holy Cow, I thought I’d won the lottery after writing my first package in under 5 minutes.  It truly was an amazing transformation (pun definitely intended).

There are so many other features that have improved along the way, too many in fact to list them all here.

It’s been a long road,

The wild and windy night
That the rain washed away
Has left a pool of tears
Crying for the day.
Why leave me standing here?
Let me know the way.

There were definitely many tears shed along the way to where I am today, tears of frustration and of joy.  But I wouldn’t change my long and winding road for anything, it’s made me who and what I am today.

SQL Server let me know the way…

Summit 2012 is over, but not forgotten

What a whirlwind last week was.  There were so many sessions to attend and only one of me.  I needed to clone myself a couple of times over in order to catch all the sessions that I wanted to see.  Unfortunately, that technology is nowhere near ready, so I had to choose wisely.

I attended Jason Strate’s (@StrateSQL) session on Extended Events, which was awesome.  I have used extended events in the past, but not to the extent in which he covered.  Wearing the DBA hat again after so many years of not wearing it, this session will be a time saver for sure.

I attempted to attend Bob Ward’s (@bobwardms) session on SQLOS, but was turned away 10 minutes before the session started because it was already full.  Lesson learned here:  Stake out my spot in Bob Ward’s sessions even earlier next year.  He is a smart dude and a great speaker.  Looking forward to the recordings being released so I can see it.

I attended a couple of sessions with Matt Masson (@mattmasson), including the BI Power Hour, which are always fun and educational – Thank you Matt (& Mr Wiggles) for making learning so much fun!

I was also able to attend one of my SQL Heroes’ sessions, Kalen Delaney (@sqlqueen), on the internals of columnstore indexes.  Kalen Delaney is so smart it makes my brain hurt.  I started out as a fan of hers when I purchased my first SQL Internals book about a million years ago.

After all these years, I finally got to attend a session with Kevin Kline (@KEKLINE) and David Klee (@kleegeek) on Virtualization.  Wow, the depth of knowledge between these two surpasses the Mariana Trench.

Wrapped up my Summit experience with a couple of sessions on Visual Studio 2012, a.k.a., SQL Server Data Tools.  I was looking forward to seeing Gert Drapers of MS, but his cohorts, Barclay Hill & Adam Mahood, did just fine without him.  Also picked up a few new things from Robert Cane (@arcanecode) on the GUI.

Thank you to all the speakers for taking the time to share your knowledge with the SQL world.

Thank you to all the volunteers and PASS HQ staff.  It would not have been as successful without you.

Policy-Based Management, How Sweet It Is

I have just recently changed employers and in doing so, I’ve changed my role from Data Architect to DBA/BI Developer.  I had been doing heads down development work for the last 4 plus years and not a lot of admin work.  Given that, I missed out on something that I think is just fantastic.  Policy-Based Management (BPM), it was a new feature with SQL Server 2008.  I spent a lot of time when I was a DBA figuring out how to monitor my servers.  I used to use a combination of home grown scripts and the SQLH2 utility.  But PBM makes a DBA’s life so much easier, especially when your shop can’t afford all the cool monitoring tools that are available today.

Basically PBM allows a DBA to manage multiple instances of SQL Server on a consistent basis.  You can use one server to create all your policies on and then export/import them on other servers.  While this is still better than the hodgepodge of scripts you had before, it’s still a bit cumbersome.  Enter Enterprise Policy Management Framework (EPM) from Codeplex.  It allows you to extend the PBM via your Central Management Server and provide some very cool SSRS reports.  Because EPM is driven by PowerShell, it can be used on SQL Server versions from 2000 to 2012.

I am so excited to be going back to a dual role of DBA/developer, and Policy-Based Management and Enterprise Policy Management Framework make it that much sweeter.

Paying it Forward

My company has recently put forth an effort to hire fresh college graduates and interns.  I think this is a great thing.  A long time ago, in a galaxy far far away, I was a fresh graduate, with no real world experience and my first employer took a big chance in hiring me.  I was really lucky with my first employer, I had a couple of fabulous mentors that taught me not just technical skills, but life skills, that I still use today.  Employers are getting in on the ground floor and it’s in their best interest to invest resources in what will hopefully be a long, successful and rewarding career.  “Paying it forward”, as it were.

As a data professional, there are some essentials will make your life so much easier down the road.  The first one is Standards and Best Practices.  Establish these early and they will become habit.  Now I could drone on forever about particular Standards and Best Practices, but that’s not my point.  My point is that if you start off your career by adhering to standards and best practices, it won’t come as a shock to you later when they are forced upon you.  You may not like the particulars of them, but it won’t feel so icky the first time you have to use them if you are used to following something.  In working with our new employees, I always take the time to point them to our standards and explain why we have them.   They are always appreciative of this, especially the explanation.

Another essential is code review.  This is a big bang for your buck.  It’s a learning experience for everyone involved.  We use an Agile Methodology in our development life cycle.  So our teams are fairly small, they usually consist of two to three general developers a technical architect and a data architect or DBA type person.  Following the Agile Methodology, anybody should be able to work on anything in the product/iteration back log.  For the general developer, they can usually write T-SQL, but most times it won’t be nearly as efficient (or dare I say pretty) as if the data architect/DBA type person wrote it.  Code review allows for the team to become familiar with a task they are not directly involved with and provides valuable feedback to the person who wrote it.  They may not be as familiar with the subtleties of the business rules or have no idea that when you use three nested select statements in the predicate you will most likely end up doing a table scan on that table with 30 million records, three times!  All they know is that their query returns and it returns the correct answer.

Take the time to “pay it forward”, it can only benefit you in the long run and the person you “paid” will be that much better for it.