BEGIN:VCALENDAR VERSION:2.0 PRODID:-//SQLBits/com CALSCALE:GREGORIAN METHOD:PUBLISH X-MS-OLK-FORCEINSPECTOROPEN:TRUE BEGIN:VEVENT DTSTART:20170407T143000Z DTEND:20170407T153000Z LOCATION:Dome 1, SQLBits 2017, The International Centre SUMMARY:Designing for Concurrency DESCRIPTION:SQL Server normally relies on concurrency models in order to maintain the Isolation in ACID. As systems scale, this method can go from being a benefit to a hindrance, limiting the concurrency for our applications and hurting performance. X-ALT-DESC;FMTTYPE=text/html:
Designing for Concurrency
SQL Server normally relies on concurrency models in order to maintain the Isolation in ACID. As systems scale, this method can go from being a benefit to a hindrance, limiting the concurrency for our applications and hurting performance. Throwing hardware at the problem can help, but does not address the fundamental issues. These can only be resolved with better database design and the correct configurations. Join John as we work through the different design patterns that exist for increasing concurrency. From using specific data types, and partitioning, to how In-Memory OLTP can help. By the end of this season you will understand the different methods available to boost concurrency regardless of the size of your environment.
John Q. Martin
John (@SQLDiplomat)John is a Product Manager for SentryOne, responsible for the SQL Sentry and Plan Explorer solutions. Working to understand what Data Professionals need and looking to deliver these capabilities effectively and efficiently.
Prior to joining SQL Sentry, John worked as a Premier Field Engineer for Microsoft based in the UK, working with a wide array of customers in many different industries that make use of SQL Server and the Microsoft Azure platform. Having worked with SQL Server for the last decade, John has gained a level of experience as a DBA, Developer and in the Business Intelligence sphere and has a broad understanding of how you can use, and misuse, SQL Server.https://blogs.sentryone.com/author/JohnMartin/ UID:SQLBITS3359SEQUENCE:0 DTSTAMP:20170524T003541Z END:VEVENT END:VCALENDAR