Site icon Brent Ozar

My #PASSsummit 2017 Session Evaluation Ratings & Comments

My general session (boy, is it rare and awesome for a speaker to have a photo from this camera angle)

After big conferences, I like to share my session evaluations to talk about what worked and what didn’t. Let’s see how we did this year.

PASS’s evaluation form this year had 6 questions with a 5-point ranking (I love that):

PASS Summit 2017 evaluation form

So how’d we do?

Pre-Con: Expert Performance Tuning for SQL Server 2016 & 2017

This was an all-day session I co-presented with Erik Darling. 362 attendees, 152 surveys filled out – great completion rate, thanks attendees!

Ouch. If you’re not a frequent speaker, those numbers might sound good, but they’re actually not so hot in the grand scheme of things. So what went wrong? Let’s check out the comments:

Event logistics comments: (room temperature, size, capacity, sound, etc.):

Ugh – and I’m not even showing all of them, there were dozens more of these. The AV was extremely frustrating, and I heard similar issues from other presenters.

For the “Session or speaker comments,” I’m going to group these together by theme:

As a reminder, here’s the abstract:

Expert Performance Tuning for SQL Server 2016 & 2017

Your job is making SQL Server go faster, but you haven’t been to a performance tuning class since 2016 came out. You’ve heard things have gotten way better with 2016 and 2017, but you haven’t had the chance to dig into the new plan cache tools, DMVs, adaptive joins, and wait stats updates.

In one fun-filled day, Brent Ozar and Erik Darling will future-proof your tuning skills. You’ll learn our most in-depth techniques to tune SQL Server leveraging DMVs, query plans, sp_BlitzCache, and sp_BlitzFirst. You’ll find your server’s bottleneck, identify the right queries to tune, and understand why they’re killing your server. If you bring a laptop with SQL Server 2016 and 120GB free space, you can follow along with us in the Stack Overflow database, too.

This is not an introductory class: you should have 2-3 years of experience with SQL Server, reading execution plans, and working on making your queries go faster.

When Erik & I wrote the abstract, we wanted to make it clear this was not a 100-level session: it was specifically for experts. We were going to cover a lot of complex stuff, fast.

Content & pacing comments:

There were dozens more than this on the same themes, just trying to pick a representative sample:

When Erik & I talked about this afterwards, we agreed that we went way too fast, and went too far in depth for a 1-day class where the public can sign up with no prerequisites. It’s really tough to balance this – everybody says they want expert-level material, and they want a lot of topics covered in a day, but there’s going to be a lot of people who overestimate their expertise level when choosing a pre-con.

For the SQL Bits delivery, we’re using a lot of these comments to help reshape some of the delivery. We’ll scale back on the level of detail, and introduce the topics more gradually.

The funniest part is that after the pre-con finished, Erik & I brainstormed on next year’s pre-con and thought we’d do an entire day on advanced parameter sniffing causes & solutions. However, several of the comments said we spent too much time on parameter sniffing, hahaha. It’s one of our favorite topics, and we could probably even spend a week on it. We may have to revisit that plan.

Slack Q&A:

Yay, that worked.

Advertising comments:

I’m always really conscious of this and start the session by saying look, we don’t want your money: this session is about teaching you to use the same free open source tools we use every day. (They’re even mentioned by name in the abstract, and I had to go to bat with PASS to make sure of that – I wanted attendees to make sure they understood that we use tools.)

There weren’t a lot of comments on this, but as a presenter/blogger, I think it’s important to mention that they’re out there, because this is a reality when working with company-sponsored open source projects:

I’m a firm believer that in the year 2017, you shouldn’t be writing your own DMV queries from scratch. I’m determined to drag folks into the open source community to learn to share their work and leverage the shared work of others. We’re not going to be like those other database platforms where the DBAs try to hide their work so no one else can take advantage of it. We’re a community – let’s share like one.

So I know I’m going to get dinged, and I’m okay with that.

Humor comments:

I’m happy with the balance of comments there.

In summary, I’m happy with the ratings overall. Here’s what we’re tweaking for Bits:

General Session: “But It Worked In Development!” – 3 Hard Performance Problems

485 attendees, 131 survey responses:

Woohoo! Love those numbers.

Event logistics comments: (room temperature, size, capacity, sound, etc.):

With ~500 folks, you’re gonna have to have a huge room, and that means some people are going to have great video/audio, but late-comers at the back won’t. (Tables are out of the question if you need to fit that many people in a room, unfortunately.)

No projector issues though! This was the exact same room Erik & I were in on Tuesday, and it sounded like the AV techs finally had the event fixed up by the last day of the conference when I spoke.

Comments about having Pinal onstage to ask questions:

I tried a new trick this year of bringing Pinal Dave up on stage with me to be an audience member, asking questions. Here’s what attendees wrote:

There was exactly one negative comment about the technique. That’s awesome! Thanks again, Pinal – you did a great job.

Content comments:

I wrote this session with only a few slides to explain concepts – the rest was done in one big long demo script. I try to write my demos the same way I talk, explaining the concepts in the T-SQL as I go so that people can follow along later as they run the queries.

Then, at the start of the session, I explain that the demo is open source, and here’s where you can go download it from. That way if you miss stuff, you can revisit it later. Here’s what folks wrote – not a lot of stuff, but I’m not surprised because they tend to just bookmark it and come back to it later:

Cool. I was worried that the pacing might be too fast, but it seemed to work here.

Delivery comments:

Well, looks good. I’m a happy camper.

Exit mobile version