Every so often, I want to try a new location to go to, and possibly speak at, a SQL Saturday event. This year, my new experience will be to go to Jacksonville, FL for their event. It will only be the second time I have been in the city, the first time being on my way from Virginia Beach, VA to vacation at my favorite place, Disney World (and yeah, I am going to stop by and see the mouse after I am finished with the event!) 

The sessions I will be doing are, first session of the day at 9:00 AM, my session about concurrency. I like this session, though it is the hardest session I have to get through the demos (though some of the tricks I note in my recent blog about SQLCMD, really help!)

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, in the final session of the day, I will be doing my old favorite:

Database design isn’t the sexiest of topics, but it is the most important of them. Hope to see you there!