Create Index Based on Query Plan
You use Query Store to optimize a query in a database. The query has two execution plans: ✑ Plan 2 is shown in the Plan 2 Execution Plan exhibit.
![](https://static.wixstatic.com/media/d400f8_66330da707f24af98784d282fe937e60~mv2.jpg/v1/fill/w_920,h_216,al_c,q_80,enc_auto/d400f8_66330da707f24af98784d282fe937e60~mv2.jpg)
✑ Plan 10 is shown in the Plan 10 Execution Plan exhibit.
![](https://static.wixstatic.com/media/d400f8_fb0762f7d4cd47838623b72e8a7587d3~mv2.jpg/v1/fill/w_911,h_230,al_c,q_80,enc_auto/d400f8_fb0762f7d4cd47838623b72e8a7587d3~mv2.jpg)
You create an index at 22:24 based on the missing index suggestion in Plan 2. The average duration statistics for the query is shown in the Tracked Queries exhibit.
![](https://static.wixstatic.com/media/d400f8_98d85c4e2c50416b80f06e99b0a7542d~mv2.png/v1/fill/w_624,h_188,al_c,q_85,enc_auto/d400f8_98d85c4e2c50416b80f06e99b0a7542d~mv2.png)
You need to analyze the operators in the two execution plans.
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
![](https://static.wixstatic.com/media/d400f8_0abe3f26c19e449f84699ac8b9c6ccdf~mv2.png/v1/fill/w_816,h_280,al_c,q_85,enc_auto/d400f8_0abe3f26c19e449f84699ac8b9c6ccdf~mv2.png)
Answer Given:
![](https://static.wixstatic.com/media/d400f8_196059b770ca42fa8462411ef2afc41e~mv2.jpg/v1/fill/w_816,h_280,al_c,q_80,enc_auto/d400f8_196059b770ca42fa8462411ef2afc41e~mv2.jpg)
Discussion:
Zikato
I see no clustered index scan there. Also the hash match operator didn't process morerows. By making the index seek more effective the percentage moved to other operator - number of rows is the same.
Bartek
Yes, in addition I think query throughpull II increase in plan 10. Just we can see it on Query Store diagram
Kuratko
NO (same or less -> smaller data & less data pages in NCI);
YES (Icons says "we are scans"; labels says: "we are seeks" -> seeks are *mostly* effec.)
YES ("same data" in shortest duration)