SQL Server optimizer doesn't use and index seek for execution of your query although the quer is high selective? What is better, when and why: LIKE vs: SUBSTRING, IN vs. EXISTS, SUBQUERY vs. JOIN. Why you should not use the UPPER or LOWER functions? How to avoid non-SARG-able WHERE clauses? Which query takes about 3 minutes in SQL Server 2008 and only one second in SQL Server 2012?

In this session we will answer these questions and show how bad designed queries lead to poor execution plans. We will offer recommendations and tips how to avoid performance problems caused by poor query design (functions in WHERE clause, data type conversions…) and explain how local variables and parameters affect the generation of execution plan. We will discuss and compare different query approaches and operators (IN vs. EXISTS, EXISTS vs. COUNT(*), UNION vs. UNION ALL, IN vs. BETWEEN…)  and give appropriate recommendations. We’ll also cover database constraints from the performance point of view.
Slide Deck 327 KB , MP4 Video Low 72 MB , Demo Code 18 KB , MP4 Video Med 68 MB , MP4 Video High 208 MB , MP4 Video HD 435 MB