Of course, technically, I live in Thompsons Station, about 20 miles south of Nashville, and technically this event will be held in Murfreesboro, also 20 miles south of Nashville, and 30 miles south of Thompsons Statiion. But this is splitting hairs. I am leaving the Nashville area for the Chattanooga area (again, 20 miles away in Cleveland, TN) at the end of the month, and this one is going to be sad for me. It has been a great ride working with Robert Verell (@sqlcowbell), Tamera Clark (@tameraclark), Jon Boulineau (@jboulineau), Kerry Tyler (@airbornegeek) and Daniel Glenn (@danielglenn) these past few years. It stinks leaving the area, but I expect to see these folks quite often in Nashville, Chattanooga, and other SQL Server venues like the Summit (and sooner or later I expect to see a few more of those names at the MVP Summit, assuming I am still attending!)
This year, I will be doing two sessions. The first is my concurrency session that I premiered last year for SQL Saturday in Nashville. It has improved a lot with stuff I have learned over the year, and it is one of the best written presentations I have ever done (if it still tries to teach too much in an hour.)
Let Me Finish... Isolating Write Operations
OLTP databases can be constantly written to and reporting databases are written to at least periodically. In order to ensure consistent results, connections must be isolated from one another while executing, ideally with the lowest possible cost to concurrency. How this isolation is handled is based on the isolation level, whether the classic lock based or the newer optimistic scheme of the in-memory OLTP engine is used, or even if both engines are enlisted in the same transaction. In this session we will look at examples of how SQL Server isolates reading and writing operations from other writing operations to explore how this may affect your application through error messages and performance hits.
Then I am doing a second professional development session at lunch with Robert Verell:
Discuss Your Career (Panel)
As a database professional, you have plenty of choice in your career path. Should you stay at the same company for 20 years, or change every few years? Much depends on what matters most to you. Do you want higher income, regular work hours, training, vacation time, group insurance, job security, lots of travel, telecommuting, or the possibility to advance to management? The panel will give their observations and experience over decades of experience. Discussion will include at least one person who has spent over 19 years with the same employer, one person who has changed careers very recently, and everyone in attendance who is willing to give an opinion.
The goal of this session will be to have a discussion about career matters. If attendees have questions about how to manage their career, we will discuss. Or there will be slides with different priorities to discuss if no one has questions. I would note that this session is not specifically about whether or not to change companies, positions etc. The goal is discuss the pros and cons of staying in one place, changing frequently, etc. There are so many factors to consider that it is maddening. Come with questions, answers, opinions, and the crunchiest lunch choices that Tamera and team have served up. If you don't learn anything, at least you will have something to eat and a seat to sit and eat