I’ve had this idea for some time. It’s been bugging me, but I haven’t really been pressured to write, nor inspired. That changed a bit with the announcement of the rules change for SQL Saturdays, as well as a few discussions I had with people.
I dislike the announcement for a few reasons, which you can read if you like.
Of What does a SQL Saturday Consist?
Like my grammar? I was desperate to avoid the preposition at the end. However, I’m wandering away from what I want to write about.
What does a SQL Saturday consist of each week? I think this is a high level view of the tasks that have taken place at many of the events I’ve attended in the last few years.
- Get a venue
- Sell sponsors some advertising/exhibition package
- Perhaps put together pre-con events (get more space and manage logistics)
- Get speakers to come speak
- Market the event
- Put together a speaker dinner
- Have some sort of speaker gift
- Order shirts for speakers and/or volunteers
- Contract for some sort of lunch
- Get volunteers to help with logistics
- Buy some prizes
- Teach people in sessions
- Have a closing and give stuff away.
- Get people to come to an after party, often providing some food and drinks.
Now, what do we need to have a SQL Saturday?
- Get a venue
- Get a few speakers
- Market the event
- Teach people in sessions
The core of this event is teaching people. It’s about touching many people that may never go to the PASS Summit, or DevConnections, or SQL Intersection. It’s about helping people get inspired in this business, learn something, meet colleagues. It’s about building a community.
Everything else is gravy.
Let’s be clear. I have no issue with events that can put on a fancy dinner for speakers, or give nice gifts, or cater lunch, or give away XBOXs to an attendee. I have no issue with any of that, and if you can, do it. However, please don’t feel you have to. Please don’t compete and build an event based on the budget you want, or have seen elsewhere. Please don’t make this event about stuff.
Remember the attendees.
Money is Tight
Money is tight with product vendors, and it’s tight with recruiters, and it’s tight with venue sponsors. I have been worried about this for a few years now, as I think vendors have gotten caught up in the SQL Saturday excitement as much as organizers, speakers, and attendees. There has been lots of easy money, and as a result, I’ve seen competition and effort put into making a SQL Saturday more like a mini-Summit than a free, grassroots, one-day event.
I am not complaining about anyone’s efforts. Many of you have done amazing jobs putting on events, and I’ve been impressed, and also quite humbled by your efforts. You really care and do a great job.
However.
The easy money isn’t sustainable, and I want many of you to be cognizant of that. I want you to ensure that you run another event next year, based on the budget you have, not the budget you want.
Most of all, I want you to feel successful with your event because attendees came and learned something. Attendees don’t care about the extras that much, at least not overall. Someone will always complain. Extras are nice, but people come to learn and interact. They come because they’re hungry to be better at their jobs.
Please don’t expect that you need to raise, or spend, $10,000, or even $5,000. Raise what you need, but build the event that suits you. I won’t think any less of you if I need to buy my own breakfast, coffee (yes, that’s a separate meal), dinner, and drinks.
I promise you, the attendees won’t think less of you either if there’s a room, a speaker, and a slice of pizza for lunch.
Voice of the DBA 