Download to read offline
Uploaded byFlorin Cardasim
Sql Server execution plans
This document discusses SQL Server query plans, including how to read graphic, XML, and text query plans. It covers one-table and join SELECT queries as well as INSERT, UPDATE, and DELETE queries. The tools for viewing query plans like Management Studio and Server Profiler are presented. Clustered and non-clustered indexes are defined, with clustered indexes physically sorting data in a B-tree structure and non-clustered indexes sorting index columns without changing data ordering. The document contains an agenda, overview of SQL Server architecture, demo section, and availability for questions.
Sql Server execution plans
- 1. SQL Server 2005– Reading and Interpreting Query PlansFlorin CardaşimLead developerRomSoft, IAŞI,http://www.rms.ro
- 3. AgendaGraphic, Xml andText query plans
- 4.
- 5.
- 6. INSERT, UPDATE, DELETESqlServer Architecturehttp://en.wikipedia.org/wiki/Microsoft_SQL_Server
- 8.
- 9.
- 10. Tuning AdvisorExecution plansrepresentations:Text (SHOWPLAN_ALL, SHOWPLAN_TEXT, STATISTICS PROFILE)
- 11.
- 12. GraphicalClustered index: storesthe data along with the lookup values of the index and sorts the data physically; implemented as B-tree(balanced)Non-clustered index: sorts the columns included in the index, but it doesn’t sorts the data
- 13.
- 14. Thank you!Florin CardaşimLeaddeveloperRomSoft, IAŞI,http://www.rms.ro
Editor's Notes
- #5 Startamdiscutia cu imaginea care descriearhitectura SQL Server. Din multitudinea de componente ne indreptamatentiacatre Query Engine(Processor) si Storage Engine. Pescurt, Query Engine ia in primire un statement SQL, ilparseazasi in urmaunoranalize produce ceeace se numeste Query Plan.Acest plan estetrimis (in format binar) la Storage Engine care esteresposnsabil cu accesulfizic la date. Discutia de astazi se limiteaza la Query Engine sioutputulacestuia Query Plan. Vomintelegeimpreunaceeste un Query plan, cum se poateobtine, citisiinterpreta.
- #6 Scopulunui Query Plan esteacela de a descoperipasiiprin care rezolva query-ulcu un consum minimum de apeluri de I/O (disk) si CPU. Cost-based plan.Serverulcreazamaimulte Query Planurisi decide pe care ilutilizeazasianumepecel cu costul minim.Serverulmentinestatisticidespredistributiasiselectivitatea (unicitatea) valorilor din coloanesiindecsi.Implicit, statisticile se mentin automat la fiecare insert, update, joinsiasamaideparte.Planulestepasatcatre Storage Engine, care ilexecuta. E posibil ca planulsa nu fie respectatde Storage Engine in cazul in care statisticile nu maisuntactuale in momentulefectiv al rularii.Planul actual siplanulestimatcelestimatestecalculatfara a rulaefectiv query-ul, cidoarpebazastatisticilorcel actual esteplanulutilizat la rularea query-uluiPlanul actual poatediferi de celestimat, in principal din doua motive: statisticilesuntincorecte (in timpelesuntalterate un urmaoperatiunilor de insert, update, delete) sau e vorba de planuri care utilizeazaparalelismsi care la momentulrulariidecid ca paraelismul nu se maipoateefectua din motive cum arfilipsamemorieisau a threadurilorlibere.Planurile de executiesunt cache-uite cu scopul de a fireutilizate. Cum crearea un pan esteO operatiecostisitoare, intr-un sistem in care se ajunge la o bunareutilizare a planurilor, se obtincastiguriconsiderabile de performanta. Exista o schema de imbatranire a planurilor deexecutiepebazacareiaplanurilesuntscoasetreptat din cache (pentru a nu se consumainutilmemorie)DBCC FREEPROCACHE – curata cache-ul, util la testare
- #7 Cum se vizualizeazaplanulestimatsicel actual in format Text, XML siGraficCum se automatizeazaproducerea de planurifolosind Profiler; cum se salveaza un plan XML pentru a fireutilizatmaitarziuCum se foloseste Tuning Advisor;.trc, .sql