This seminar will be held July 11 – 12, 2018 (Online, 8:00 AM – 12:00 PM PDT each day).
Are your users seeing bad data?
If you’re using the default isolation level of read committed in SQL Server, chances are that sometimes your users get incorrect results — and that blocking can slow down their queries. If NOLOCK hints lurk in your code, the odds are even higher that sometimes your customers see information that just isn’t right.
What you’ll learn
In this demo packed seminar, you’ll learn why a single statement may read rows twice, miss rows entirely, or return combinations of data that never existed in the database — and why that’s not a bug. You’ll learn what “read phenomena” are, which isolation levels are vulnerable to them, and the performance trade-offs (also known as the risks of blocking) which come from raising your isolation level to protect your users from bad data.
You’ll see how isolation levels work with newer technologies such as columnstore indexes, In-Memory OLTP, and Always On Availability Groups.
You’ll discover why version-based isolation levels can be awesome for reducing blocking and providing data integrity. But you’ll also learn when some of these isolation levels may produce– you guessed it– incorrect results.
At the end of the seminar, we’ll pull together all this information into a guide. You’ll leave the seminar with the tools and knowledge to choose the right isolation levels for new and existing applications based on business and performance requirements.
This course is taught by me, Kendra Little
My study of isolation levels began more than 10 years ago, when I was a database administrator who showed up as a candidate for a Senior level job knowing nothing more about isolation levels than that the world “NOLOCK” wasn’t always good– but I didn’t know why.
Since that hilariously disastrous afternoon, I’ve learned a ton about isolation levels, locking, blocking, and deadlocks – and I love teaching other how to optimize concurrency and avoid incorrect results.
Why does this online seminar take two days?
I find that people come back to day 2 of a class with new ideas and fresh questions — plus, it’s easier for you to keep up with your day job if class doesn’t take all day.
Having two four-hour sessions over two days helps you learn more than a single eight hour session, without letting your Inbox get too out of control.
Can I watch the SQL Seminar later?
Yep! I’ll make the GoToWebinar recordings of the sessions available for the class after the seminar completes. You’ll have access to the recordings for a year.
What’s the experience like?
When you register for this seminar, you’ll get registered in an online GoToWebinar meeting scheduled for the two days you select in the dropdown. The invitation makes it easy for you to block out the session times on your calendar.
Prior to the seminar, I’ll send you information on how to test your connection and make sure that you’re ready for class.
The days of the seminar, you’ll join the live GoToWebinar session. I’ll be live with my webcam and shared demo environment. You’re invited to follow along with your scripts, if you’d like — or you can simply watch and ask questions in the GoToWebinar chat window, if you learn better that way.
We’ll take a 10 minute break every hour or so during the seminar. This makes sure you can stay caffeinated, hydrated, etc.