SQL Track at Orlando Code Camp

One of the things I worked on as part of SQLSaturday Orlando last year was increasing the engagement with the local .Net group (ONETUG). One of the offshoots of that is that they’ve invited the SQL groups to chair the SQL track this year for Code Camp. Kendal asked for feedback on what kind of SQL content they wanted and we got back the notes below. Will be interesting to see how well we can fill that list! We can also start thinking about topics we want to see on a Developer track at SQLSaturday Orlando. I’d like to see content that educates DBA’s/data people on what/why developers need, are doing, hate doing, challenges with databases, etc. I also want to repeat something I try to say a lot – there is always interest in SQL at Code Camps. Speakers, it’s another place to go to practice your skills and share your enthusiasm.

Here’s the note, or close, that Kendal will be sending out to the Orlando speaker list today:

The Orlando Code Camp is coming up on March 28, 2015 and they have asked oPASS/MagicPASS to chair the SQL track this year. We asked for feedback on the type of SQL presentations they wanted and we received this:

  • A DBA’s guide to dealing with Code First EF
  • Version controlling your database objects
  • Troubleshooting the database side of a slow application
  • Things that every developer should know when working with a database
  • Top database mistakes made by developers and how to avoid them
  • SQL and the Cloud – Good/bad/ugly
  • Why all developers should learn how to work with SSMS
  • SQL vs NoSQL
  • Avoid topics on installation and pure administration
  • Audience is primarily developers, but will include some QA, managers, and of course DBA’s

The call for speakers closes on January 25th and we expect the schedule to be published by February 2nd. Priority will go to sessions that most closely match the list above and we have seven slots to fill. If you don’t have an exact match we encourage you to submit the presentation you have ready that you think would be most interesting to a developer audience. Attendance at the event is typically 600+ and we’ve always seen good attendance at the SQL presentations.