You keep getting warnings and emails about deadlocks, but let's be honest: you're not really sure how they happen or what to do about it. Brent Ozar will show one, use sp_BlitzLock to analyze it, then fix it.
We will see two important case studies where the optimizer is obviously a criminal who has killed the query performance. We will together with carefully investigate inside the query optimizer understand the reason.
With the grow of the SQL Graph surface in 2017-2019 (incl. the ShortestPath() function) we have a chance to do some pretty exciting calculations and start analysing different types of Networks such as the Social ones.
When do we get improvement in the performance, and when should we better not choosing partitioning but some other optimization techniques instead? Shall we optimize by using partitioning or yet another index?
<<1>>