SQL Server, PASS, and other data mishaps
How deep can you dive?
After last years Summit we launched a feedback site http://feedback.sqlpass.org in hopes of gathering all of the feedback about the event in one place. The number one thing people have asked for on that site is for there to be a track of sessions in the 400-500 level range. The problems with the community desire for higher level sessions are twofold, one we dont normally get a huge number of session submissions that are at the 400-500 level. Two, I’ve been told by those who are qualified to present those types of sessions that an hour and fifteen minutes (spotlight) is often not enough time.
Cramped for space
In the past our conference size has dictated the floor-plans at the conference center and we’ve been maxed out at 14 concurrent sessions. This year however, because of anticipated attendee growth, the logistical geniuses at PASS HQ were able to add another session room (I’m looking at you Anika and Craig). With this new room I have options on what to do with the extra session rooms!!
Changes for the Summit 2011
This year we’ll be using the space we gained from the new room addition to have longer deep dive sessions. The current idea is to offer these longer sessions in hopes that they will attract presenters who are qualified to present these deeper dive sessions. Currently, the plan is to have a maximum of 6 deep dive (lvl 400 or 500 only) 3 hour sessions. Because of the way the schedule is laid out, we will run 2 of these sessions concurrently every conference day.
Rules… Yeah there’s always rules
We will accept abstracts for this new session type in the same manner as a regular abstract. That is to say anyone can submit a half day abstract. If you submit an abstract for a 1/2 day session it will count as one of your 4 allowed abstract submissions. The session selection for these sessions will be handled by the regular respective abstract review teams. Even though we are going to allow anyone to submit abstracts for these sessions, it should go without saying that if you don’t have prior experience or reputation for being able to give an extended, strong 400-500 level session it may be best to focus on a regular summit session. What I mean by this is for these particular sessions we will be instructing the review teams to weigh the speakers perceived ability to deliver the session higher than we normally would for a regular session.
Possible Hiccups i.e. Changes
Two things could change with these sessions.
- I am considering making the sessions 4 hours long (roughly 3 regular session slots). If we do that the maximum number of sessions would drop to four. I’m leaning heavily away from this but, if anyone has a strong opinion on this I’ll listen
- Depending on the quantity and quality of the abstracts we receive, we may have less than the maximum sessions shown above (4 or 6)
- Im still considering a single DBA 101 “Accidental DBA” type session for one of these sessions but havent been swayed that there is more interest there than there is in deep dives
| Print article | This entry was posted by Allen Kinsel on March 24, 2011 at 8:52 am, and is filed under SQLPASS, Summit, Syndicated. Follow any responses to this post through RSS 2.0. You can leave a response or trackback from your own site. |



about 2 years ago
So, is that a picture of you diving? Wow.
Good idea on the extended sessions, though!
about 2 years ago
No, I thought that picture was of you diving, you didnt follow the link to your Flickr Profile?
about 2 years ago
Allen, I would hope that at least one break period is contained within the three hour session. I also think that 3 hours is probably better than the 4 hour session.
Glad to see changes and experimentation in the Summit.
about 2 years ago
I don’t have a strong opinion on the length. One could make a case for either, although a short break should be included.
Regardless of length, I implore you to *not* run these sessions concurrently! More seasoned attendees will be drawn to these sessions and The Summit. Making them choose between session X and session Y greatly reduces that appeal.
about 2 years ago
Dexter and Eric,
I doubt we will work in an official break, if we do that, it would basically become a Session X pt1 and Session X pt2 which isnt the point. as always though, youd be free to leave if needed.
To the not running them concurrently point, I dont have a choice, unless I want to only have 3 sessions. The reason is Ive only got 3 days to work with, and of those 3 days, I’ve only got the afternoons where there are 2 sessions back to back. Logistically, Im kinda stuck on this one but, the same thing could be said where we are already making attendees choose between 14 other sessions in the same timeslot
Thats a problem I dont necessarily mind having, too many good sessions to choose from!
about 2 years ago
Re: running two sessions at once, that’s what the DVDs are for.
about 2 years ago
Allen –
Your point about the scheduling is well taken; I forgot the morning sessions aren’t long enough to contain a longer session.
Not sure if there’s interest in starting earlier to accomodate a morning session or not. I’m an early bird, so I would be for it, but I suspect I’m in the minority…
As Denny points out, that what the DVDs are for.
Not the same as being there, but a lot better than missing the session completely!
about 2 years ago
About the “Accidental DBA”, wouldn’t that be better served by a pre or post conference? There is just so much stuff to go into…
I’m all for having longer sessions if thats what we need to attract 4-500 level submissions.
about 2 years ago
You could ask the people that will probably be the ones submitting (and approved for) the sessions. I’m sure you’ve got a pretty good idea as to who will be submitting them (its a pretty short list) if they think 3 or 4 hours would be preferred to get their content across.
about 1 year ago
The other option would be to offset the break slightly between part 1 and part 2. Maybe the longer session would break 15 minutes earlier and take a shorter break. Hopefully they would all be back in the room before the full break started.