Category Archives: SQL Saturday

We had our fifth sql saturday at Louisville – this time at a much bigger location, the school of business at University of Louisville. We also had a day of pre cons (our first pre con was by Kevin Kline last year, and was moderately successful with an attendance of 23 people. This year we tried 4 pre cons – we were unsure of which subject area to pick mainly, and all the 4 speakers were rated highly previously and among our loyalists). Some of the lessons learnt on the pre cons are as below:

1 The day started with a bit of confusion – one of the speakers had to move their room from what was originally scheduled since there was a class going on. We were relieved to be given an alternative.But much to our dismay this happened one more time, in the afternoon, actually disrupting an ongoing class. We learnt later that the reason was that the school actually has classes, and many happen without schedule. They helped us out greatly the next day by posting notices on doors that our classes cannot be interrupted. We also learnt not to host classes on premises that have their own events going on, particularly on working days.

2 We didn’t have the room number printed on the ticket – this was a gotcha on our part while setting up the ticketing with Eventbrite. Several attendees turned up without reading the email info on pre cons and those of us at the reception didn’t have them on us although our signboards had them. Our lesson was to keep room numbers printed on tickets going forward.

3 Some candidates walked to their rooms directly without checking in. (We assumed they would register/check in). Although we did not find anyone attending without payment – this indicated a possibility of that happening – lesson is to keep the check in process directly outside the room instead of in a common spot.

4 We learnt later from pre con speakers as well as other sql saturday organizers that having 20 attendees is generally considered good for pre cons – and we did nearly touch that number with 3 of them. The lesson to take away is possibly that two pre cons are the best way to go for us – possibly one on BI and one on the DBA track. That might give an above-average count of people for each class and also ease manageability issues.

5 One of the pre cons had an offer for multiple attendees to attend for the price of two. Initially it seemed like it sold well and brought in a few numbers, but many of those who signed up on this deal simply did not show up. Perhaps they did not get the day off or perhaps they thought it was not worth their time – we had to give away the extra lunches we bought for these people. The lesson here is to reduce ‘deals’ since there does not seem to be accountability with no payment.

All that said,  most attendees seemed very happy with what they learnt and wanted to do this again. The teachers seemed happy too since the attendance was well above average. Overall, we would call this event a success and hope to do it again, incorporating the lessons learnt. Our thanks to our teachers – Kevin Kline, Eddie Wuerch, Bill Pearson and Dave Fackler, and to all the students who attended. We don’t have a spot yet to upload their presentations but will email attendees with them – you may also want to follow their blogs for the downloads.

We had our 3rd sql saturday at Louisville on 28th October 2011.  It was a huge event with over 230 people attending, 5 tracks and six sessions each. There were many things we learnt out of running an event like this (when i say ‘we’ i am referring to me as key organizer and our volunteering team). Let me start with what went well –

1 282 people registered, 230 showed up. More than double since last year, and very unexpected. Our feedback shows several people impressed with sql saturdays in general is the reason, and that is a great trend.
2 Number of sponsors was much higher, double than normal (although amounts of sponsorship were lower). I still consider this a great trend.
3 Local sponsors (Teknetx and Ebits) were very impressed and want to come back. Building local sponsors is a very difficult task and I consider it very significant that we succeeded this year.
4 Most speakers (other than one or two) seemed happy and wanted to return. This is also a great trend.
5 There was definitely a lot of interest in non technical subjects – toastmasters and women in technology sessions showed good attendance and this is something we want to continue to do.
6 Seating sponsors near lunch area seemed to attract good crowds to them, this is also something we want to continue to do.
7 Buffet lunch went very smoothly and was a great idea compared to boxed lunches.
8 Pre conference with Kevin Kline – had a great turnout – again much higher than expected and was very smooth. Most people including volunteers enjoyed it greatly. We definitely want to do more of these,  perhaps with speakers who are close to town and can get in easily.
10 I got some great feedback on quality of speaker shirts, some internal signage especially posters, and printed schedule book. We will continue doing them, although the printed schedule would depend on the budget.
11 Costumed volunteers and speakers seemed to go down very well. Even met an attendee at a crowded Trader Joe’s today who asked me if I was the ‘lady in the pink hat’ at sql saturday, and complimented us for turning out in colorful costumes. I am definitely going to save that hat , perhaps wear it next time around also 🙂 In short this means creativity is appreciated and we will definitely look at this further.
12 Timing was good in terms of weather and other logistics, not to mention creativity added on by Halloween. This looks like a good time to have the event every year.

What did not go well – am afraid this was a little more than what we expected this year. There were two main reasons – one of them was that we needed lot more volunteers than what we had for an event of this size. Finding committed volunteers is a very hard task. Our existing volunteers were stretched to the bone,and last minute efforts at finding more people did not succeed. Most people on the sign up list did not respond to emails and we only had those who had been with us through the event planning. Second, we really did not expect double the number of people. This is very hard to plan as around 60% of registrations happen in the last month or so, when we are set in terms of planning location, budget and volunteers. We assumed a 50% or so increase, but not this much and this is what caught us off guard in many respects.

1 Breakfast – any event organizer’s nightmare come true, happened to us. The caterer was known for their reputation and quality, but just happened that they had a staff turnover and the new team had us as their #1 client. So breakfast showed up 40 minutes late – after several desperate calls. The driver had lost his way and gone to the other side of town. When it arrived the coffee was cold, there was no cream, bagels had no sides. We asked for a second delivery of coffee, and it was delivered again, but with no cream! (talk of software programs with bugs, looks like people have them too). Anyway, the caterer and several people on their side called repeatedly to apologize.

2 Registration – our volunteers were caught up in sorting raffle tickets which apparently sorted wrongly by the print shop on a batch basis instead of a person basis. This made it very hard to hand over a batch of tickets to the right attendee. Lots of people also showed up earlier than opening time, and with no coffee around it made it seem really long for them.

3 Lunch was delivered early – again this was an issue arising due to some logistics. There was a tailgating party/soccer match in the vicinity and we were warned of traffic holdups in the area. Despite checking with several people we were unable to get a good idea of how bad this situation was and how much we needed to plan around it. So we decided to play it safe and ask the caterer to deliver early. The caterer messed up breakfast and was eager to make us happy, he delivered more than an hour early. This left several people displeased although there was plenty of food to go around.

3 Session scheduling – this was a blunder on our side. We used the default template PASS had which had no breaks between sessions. We also had several sessions that seemed too good and limited rooms to work with so we went with 45 minutes per session (which is by the way how we do it at user groups). This was definitely a bad idea, and a couple of speakers were really put off. We will have to work with lesser sessions per track but more tracks/more rooms next time.

4 Location was crowded, registration area small and so on – This was some of the feedback we received from attendees. Again the turnout was unexpected and the location was clearly not built to handle such a crowd. We will definitely look for bigger locations next time.

5 Post event social was not on premises – One attendee suggested a party on premises including an open bar 🙂 I guess with the growing number of well funded sql saturdays lot of people tend to forget that some events may not have funds, and secondly our event was on school premises, there is no chance of having an open bar there even if we could have afforded it. The problem with post events generally is that again we don’t know how many people are going to show up. We planned one the first year and there were only about 20 people. That number is not enough to book a restaurant or any place, especially around halloween when there is a lot of demand. The second issue we have is that volunteers were extremely tired and none of us had any energy to do a social. We will address both issues with next event.

6 Raffle drawing – This was scheduled for 5 30 pm. By 4.45 or so several vendors started to pack up, did their own drawings and gave me the gift with winner’s name and left. I was not sure if waiting until 5.30 pm was a great idea so we had it early, at 5 pm. This left out several attendees who were in the other building attending a session that went over a little. This is an issue we plan to address both with vendors and advisors of sql saturday. There was also some feedback regarding ‘more gifts and prizes’ – again I believe this arises out of some events having a lot of funding to play with. We had three Ipads, one XBox Kinect and several small prizes. It was good for an event of this size, and don’t plan to address this any further.

Takeaways:
1 Find a bigger building and have all sessions in the building. Have more tracks and less sessions with 15 minute gap between each session.
2 Divide breakfast between coffee and food, again I may be paranoid here but I think we should make arrangements for that java to arrive and be ready before people do.
3 Get more student type volunteers or those who have no interest in sessions to sit in all day at registration and at food table.
4 I hate to say this but I want to – that is not pick speakers who are hyper critical or not understanding of effort that goes into organizing a free event. Granted some things did not work as expected but to remember these events are free and done with huge amounts of effort.Atleast try to talk to organizers cordially, offer some feedback in encouraging ways, not just dump us and take a high handed stance. If you are so demanding our response would be ‘sorry, we want to work with friendly people next time’ – there is no shortage of them in the sql community.
5 Do more precons – particularly with speakers who are close to our area and do not have huge demands on number of attendees.
6 Work harder on hosting a good post social.

SQL Saturdays are a huge amount of work. But to date, i have not met one volunteer who regretted doing it. Most of us feel empowered in fact to do more and better. That is in itself proof of community and learning. So here is a huge thank you to all of you who supported us and worked with us, and hope to see you again until next year!!