A few years ago, I wrote about my first experience speaking at SQL Saturday. Recently I had a conversation with one of our first-timers speaking at SQL Saturday Rochester 2020 and realized I should do a follow-up with some additional tips.Continue reading “First Time SQL Saturday Speaker Tips”
I presented a few times in 2019, and I’m starting off 2020 with several as well. Here’s what’s on the schedule for Q1.
- 2020-01-06 1Yep, ISO8601 format. That’s how I roll. – I’ll be giving a lightning talk at work titled “What Does a Database Administrator Do, Anyway?” This one isn’t open to the general public (though I might tweak it for use at community events), but The Bobs and “It Depends” both make an appearance in the deck.
- 2020-02-01 – I’m thrilled to announce that I’ll be presenting Keys to a Healthy Relationship with SQL Server at SQL Saturday Cleveland. This is incredibly exciting while at the same time, nerve-wracking. Cleveland is home to quite a few people who I look up to in the SQL Server community, and being selected to speak there is an honor. At the same time, getting up in front of those same folks…I have to keep reminding myself that they’re my friends, they want me to succeed, and they’re in my corner.
- 2020-03-27 – I will be presenting Keys to a Healthy Relationship with SQL Server via webinar for SQL Professionals of Chattanooga. I met Heather Durham (twitter), one of the group organizers, at PASS Summit 2019, asked if the group would be open to me presenting remotely for them, and a few weeks later we were setting things up! Travel isn’t always easy for me, so if this works well hopefully I can add more presentations to my schedule.
That’s what’s booked so far for 2020. I’m hoping to submit sessions to a few more SQL Saturdays later in the year. Once I get another session worked out I’ll be presenting that (those? we shall see…) at our local user group and hopefully adding them to my SQL Saturday submissions. I’m shooting for couple more lightning talks and lunch & learns at work as well!
It feels like SQL Saturday Albany just wrapped up, but I have another announcement to make. I am proud to announce that I have been selected to speak at SQL Saturday Boston on September 14th, 2019. I will be presenting “Keys to a Healthy Relationship with SQL Server” at 11:15 AM.Continue reading “SQL Saturday Boston: I’m Speaking!”
Thanks to everyone who came out to see dbatools for the Uninitiated at SQL Saturday Albany on July 20th, 2019. I had a lot of fun sharing dbatools with you and hope you’re ready to start exploring on your own!
The slides and demo scripts are available in my GitHub repository.
If you have any questions about the session, please feel free to contact me via:
Probably a bit late getting this posted but I will be speaking at the March 5, 2019 meeting of the Rochester SQL Server User group (RSVP link). I don’t have a great title or abstract for the talk (yet!), but here’s the gist:
The first edition of the PSPowerHour is in the books and it looks like it was a big success. This one was dbatools-heavy but I chalk that up to the dbatools community having lots of free time because we’ve automated so many of our tasks 🙂
I signed in about half an hour ahead of the webcast and was the first one there. Shortly thereafter, I was joined by Michael Lombardi (t, then Jess Pomfret (b|t) and Chrissy LeMaire (b|t). After ironing out a few glitches, we got everyone in the right place and kicked off the broadcast. Everything ran very smoothly, especially considering the number of people involved – Michael and Warren F. (b|t) did a terrific job of orchestrating everything.
While watching and listening to Chrissy, Doug, Andrew & Jess give their demos, I ran through my own in my head a couple times, adding and rearranging a few things as I observed how they were doing theirs. The big dilemma for me was whether or not to run the camera or exclusively screen share (I ended up going with the screen share only). Having not rehearsed my demo enough in the weeks leading up to the event, I was still not sure where to dip into more detail or dial things back and seeing what others were doing helped quite a bit. Having familiar faces & voices ahead of me in the queue put my nerves to rest.
I wasn’t able to watch the sessions after mine in their entirety due to family commitments. Joshua’s Burnt Toast module looks like it’ll be fun to experiment with and add some nice functionality to scripts (I got to see about half of his demo), and I’m really looking forward to catching a replay of Daniel’s demo of PowerShell on the Raspberry Pi – I didn’t realize that it had been ported already!
Invoke-DbaSqlQuery and why one should use it over
Invoke-SQLCmd – primarily for protection from SQL injection. Things didn’t go exactly the way I’d practiced; I ran short of time despite feeling like I rushed things and cutting back on some of what I had planned to say. The latter was in part because of the lead-ins from Chrissy, Andrew, and Jess. Because they did such a good job introducing dbatools, I was able to skip over it. But I was able to throw in a teaser for Matt Cushing’s (b|t) demo at the next PSPowerHour.
Running the demos inside a VM and screen-sharing just that VM made things easier for me as opposed to flipping between apps. My scripts will be available on GitHub along with the other presenters’ once the pull request is approved.
I achieved my goals:
- I did it
- I successfully demonstrated a SQL injection problem and explained why it’s so bad
- I demonstrated how to make database queries from PowerShell both more reliable and safer
- I learned about some new stuff that I desperately want to experiment with.
Next time around, I definitely need to rehearse more and get my timing down better but overall, I’m happy.
If you’re working with SQL Server from PowerShell, either as a DBA, analyst, or anyone else running queries, you’ve probably used Invoke-SqlCmd. But depending on how you’re building your queries, this can be error-prone or a huge security exposure! With the help of the dbatools module, I’ll show you how to write and run these queries better and safer – and make them easier to work into your scripts to boot.
I’m excited to be a part of this – it’s been far too long since I’ve done a presentation. Please join us on the YouTube channel/stream next Tuesday!
Earlier this week, the PowerHour was announced. What is it? It’s kind of like a virtual user group. One hour, 6(ish) lightning demos (10 minutes or less), centered on PowerShell. All community-sourced and driven – anyone can submit a proposal for a demo and if accepted, you’ll be slotted into an available spot.
They’ve already set up a YouTube Channel so you can either watch live or catch up later on, and the whole deal is being organized and managed through GitHub. Got something you want to show off? Log an issue using the template!
It’ll be fun for speakers and attendees alike! You can even use your demo(s) for user group meetings or SQL Saturdays – anywhere lightning talk/demo spots are available. Several SQL Server community folks have tossed proposals in and with so many DBAs getting hooked on PowerShell, it’s a great way for these two communities to come together.
Consider this the outtakes from my previous post about speaking at SQL Saturday.
It took a while for me to build up the courage to finally get up in the front of a room at SQL Saturday. As I mentioned in my prior post, I did quite a bit of studying of other peoples’ sessions, read peoples’ studies of other peoples’ sessions (Grant Fritchey’s “Speaker of the Month” series) and talked to a few people at the speakers’ dinner. Here are a few of the key things I learned which put me more at ease.
Everyone gets a little nervous
Feeling a little twinge of nerves is completely normal, even for seasoned speakers. Those feelings are what keep you on your toes. Get “comfortable”, get complacent, and you’ll probably overlook something.
Your audience is there for you
If you’ve only ever spoken previously in a classroom setting or making a pitch at work, SQL Saturday is very different. In those other scenarios, you have a mandated audience. People are there because they have to be there. They don’t really care much about you or what you have to say. At SQL Saturday, your audience is has opted into your session. They’re there because you have something they want. They’re receptive. They’re giving you their time and attention.
It’s OK to unwind after you speak
I don’t mean you should run out of the room as soon as you’ve finished the last slide. People may have questions they want to ask you. But if you need to go to the speaker’s room for a bit to decompress and unwind afterwards, it’s OK.
You’ll never finish the slide deck
I completely redid one slide on Thursday night, and was still fiddling with a few others Saturday morning. Just don’t tell people that you were working on it right up until the last moment; as long as what you say matches up with what’s on the screen, they don’t have to know.
It’s only SQL Saturday
That’s not meant to diminish SQL Saturday at all. But you’re not hosting the Oscars. If something goes wrong, it’s not happening live on TV with 50 million people (including your parents and kids) watching. You aren’t a paid professional speaker – you’re just there to share with people. People will give you some slack if you aren’t perfect.
It’s important to look at the feedback you get (attendees: please fill out those evals!). Reflecting on what went well is just as important as looking for areas of improvement.
What went well
- I hit all but one of the points I wanted to hit. The one I missed wasn’t critical.
- I didn’t run short on time. I think I paced myself pretty well, and took a sip of water when I felt I needed to slow myself down.
- All my demos & equipment worked. My demos depended upon Azure, and RIT (our hosts) made major improvements to their guest network since last year.
- I picked up a Logitech R400 remote so I wasn’t tethered to the podium for changing slides. I’m a “fidgety” kind of person, so in addition to achieving that goal, it gave my hands something to do without attracting attention
- I didn’t spontaneously combust
What I need to work on
- People want demos, not talk and slides. I’m already working on trimming the deck down to give myself more time to show and explain code.
- I had trouble reading the audience. This is something I have trouble with elsewhere as well. Maybe I need to pick up a book on body language.
- Most of my attempts at levity fell flat. I knew I was rolling the dice and while I didn’t roll snake eyes, I didn’t roll a 7 or 11 either. I also had one obscure reference which I knew only one person in the building would be likely to pick up on, but he wasn’t in the room. That one didn’t hurt me, but had I been able to find the image I really wanted, it would have worked better.
- I didn’t move around as much as I wanted or expected to. I thought I was going to make more use of the notes I’d written in PowerPoint but to read them, I would have had to stay too close to the podium. Next time, fewer notes & more moving around.
I’m looking forward to working on that last point. I was disappointed with how few demos I had for my session, and that feeling was backed up by some of the feedback I got. Next time, it’ll be better.
I’m not sure when the next time will be. Unfortunately, the SQL Saturdays that are close enough for me to get to interfere with other obligations on my calendar.