InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comFri, 24 May 2013 18:24:03 GMT20http://www.sqlservercentral.com/Forums/Topic1085228-2904-1.aspxGreetings, As I have just read this part of articles. A question arise in my mind :-D about figure 5. As my I understanding after reading untill part 9 is:with query below[code="sql"]SELECT C.LastName, C.FirstName, C.MiddleName, C.Title, H.SalesOrderID, H.OrderDateFROM Person.Contact CJOIN Sales.SalesOrderHeader H ON H.ContactID = C.ContactIDWHERE Suffix is null ORDER BY Title [/code]I think the query plan should be [b]still[/b] like figure 4 (not changing). This is because index IX_ContactID which added later does not give more advantage (lack field SalesOrderID to show for final output). How come with new index IX_ContactID and Clustered Index of table Contact, we can produce field SalesOrderID for final result?Please give me enlightenment here :-).Fri, 04 Nov 2011 00:38:22 GMTpermono.samhttp://www.sqlservercentral.com/Forums/Topic1085228-2904-1.aspxIn the 'Viewing Parallel Streams' section you claim that both 'streams' are read in parallel. A hash join is a partially-blocking iterator: it consumes all rows from the build input to create the hash table, and then probes for matching rows one at a time from the probe input. This is clearly documented in Books Online - see [url=http://msdn.microsoft.com/en-us/library/ms189313.aspx]Understanding Hash Joins[/url].Wed, 05 Oct 2011 04:52:55 GMTPaul Whitehttp://www.sqlservercentral.com/Forums/Topic1085228-2904-1.aspxComments posted to this topic are about the item [B]<A HREF="/articles/Stairway+Series/72441/">Stairway to SQL Server Indexes: Step 9, Reading Query Plans</A>[/B]Mon, 28 Mar 2011 15:53:40 GMTDavid Durant