History repeats itself…

This week, I will be attending my second SQLBits. I had my rookie year last year, where I learned the most important fact about SQLBits: Every session is a winner you don’t wanna miss. I had a hard time deciding which sessions to attend last year, but finally boiled it down. This year, I made a plan up front, mostly going with my instincts, but also coordinated sessions with two other co-workers who is attending.

My final schedule is looking like this:

Thursday (pre-con):
Real World SSIS: A Survivial Guide, by Tim Mitchell (blog|twitter)

Friday:
KeyNote by Conor Cunningham (blog), Seeking SQL Server Secrets by Kalen Delaney (blog|twitter), Moves Like Jagger :  Upgrading to SQL Server 2012 by Mark Broadbent (blog|twitter), Quantifying the Cost of Compression by Fuision-IO, The Developer Side of Master Data Services by Sascha Lorenz (blog|twitter), Why APPLY? by Christina E. Leo (blog|twitter) and rounding the day of with insights into Advanced Micrtosoft Certifications for the SQL Server Professional by Gavin Payne (blog|twitter).

Saturday:
War Stories from Implementing SQL Server 2012 AlwaysOn by Dan Stillwell (blog|twitter), SQL Server 2012 Memory Management by Neil Hambly (blog|twitter), An Introduction to the wonderful world of OData by Wesley Backelant (blog|twitter), Advanced SQL Server 2012 HA and DR Architectures by Christian Bolton (blog|twitter), Incremental Processing of SSAS Multidimensional Databases by Dr. John Tunnicliffe (blog|twitter) and finally Estimation, Statistics and Oh My! by Dave Ballantyne (blog|twitter)

Again this year, the team behind SQLBits have done a terrific job on getting great speakers and the speakers have submitted some really great sessions.
I am really looking forward to learn a bunch of new stuff about SQL Server, and of course to flash the medieval costume I’ve borrowed from a friend who’s into reenactment, so it should be somewhat authentic 🙂

One thought on “History repeats itself…

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.