13. 1 2 3 The result is ALL Sales Territory Country

15. Source Table GROUP BY Expression to evaluate

16. Compute sub-totals at the Year level

25. Optimizing means using the SE and avoiding FE

28. 28

30. Catches events from SSAS Queries Events Query Processing

36. EVALUATE CALCULATETABLE( SUMMARIZE( 'Internet Sales', Geography[State Province Code], "Sales", SUM( [Sales Amount] ) ), FILTER( Customer, Customer[Last Name] = "Anand" ) )

40. Slower queryOptimized query Always put extended columns in ADDCOLUMNS parameters. Just use SUMMARIZE for its group by and when the evaluation context of SUMMARIZE is required (i.e. when a TOPN has to be executed for each group) http://www.sqlbi.com/articles/best-practices-using-summarize-and-addcolumns/ http://www.sqlbi.com/articles/best-practices-using-summarize-and-addcolumns/

42. Using one SUMX, the optimizer pushes the calculation in VertiPaq

43. These two measures are slow to compute The filter is applied after computation

44. 44 This query runs 7 times faster, even if it computes [Sales] twice

46. If you heavily hit Formula Engine, the cache will not be really useful.

49. Windows Azure

50. http://microsoft.com/msdn www.microsoft.com/learning http://channel9.msdn.com/Events/TechEd http://microsoft.com/technet