|
|
|
SSChampion
        
Group: General Forum Members
Last Login: Today @ 1:03 AM
Points: 10,990,
Visits: 10,543
|
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Today @ 12:39 PM
Points: 5,103,
Visits: 20,220
|
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Tuesday, April 30, 2013 7:26 PM
Points: 254,
Visits: 277
|
|
Looks like I am the first to get it right! 
Makes a change.
I am normally the last person to get it wrong.
Nice question, with lots of interesting articles.
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Yesterday @ 7:43 PM
Points: 2,174,
Visits: 3,586
|
|
This might be the toughest QotD.
Mohammed Moinudheen
|
|
|
|
|
UDP Broadcaster
      
Group: General Forum Members
Last Login: Friday, May 10, 2013 3:15 AM
Points: 1,476,
Visits: 1,943
|
|
Going to stick my neck out and say that its wrong.
Yes the stream aggregate gets called first... but it hasnt finished. So is the important part which gets called first or which gets finished first? Personally i think its the part that gets finished first thats important (or more precisly the thing that performs its purpose first). I cant say a function has been executed when it hasnt actually done anything.
Could be a language thing though that i put a different meaning into "executes" then everyone else 
/T
|
|
|
|
|
SSChampion
        
Group: General Forum Members
Last Login: Today @ 1:03 AM
Points: 10,990,
Visits: 10,543
|
|
tommyh (10/27/2011)
Going to stick my neck out and say that its wrong. Yes the stream aggregate gets called first... but it hasnt finished. So is the important part which gets called first or which gets finished first? Personally i think its the part that gets finished first thats important (or more precisly the thing that performs its purpose first). I cant say a function has been executed when it hasnt actually done anything. Could be a language thing though that i put a different meaning into "executes" then everyone else  The learning point today was about execution order (hence the title). Query plans are pipelines, and the intention was to highlight something that most people misunderstand about that. I'm sorry the way I phrased it differs from your intuitive understanding of 'executes', if I could give you your two points, I would. That's not to say that I agree with you (I don't) but points are free, and I like people to be happy
Paul White SQL Server MVP SQLblog.com @SQL_Kiwi
|
|
|
|
|
SSCarpal Tunnel
       
Group: General Forum Members
Last Login: Yesterday @ 8:17 AM
Points: 4,804,
Visits: 8,074
|
|
|
|
|
|
SSChampion
        
Group: General Forum Members
Last Login: Today @ 1:03 AM
Points: 10,990,
Visits: 10,543
|
|
Gianluca Sartori (10/27/2011) Great question, Paul, and great explanation. Looks like you tricked most of us (myself included). Thanks, but I want to say that I really really really didn't set out to trick anyone with this. It was intended as a follow-on question to my previous one (Table Access Order) but the scheduling meant they came much further apart in time than I intended. The formatting also got messed up in the explanation, but hey ho. Hopefully there's enough value in the learning point that I get away with it.
Paul White SQL Server MVP SQLblog.com @SQL_Kiwi
|
|
|
|
|
Say Hey Kid
      
Group: General Forum Members
Last Login: 2 days ago @ 4:28 AM
Points: 695,
Visits: 1,023
|
|
| Great question. I got it wrong but learned something which is a good start to the day.
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Yesterday @ 2:48 AM
Points: 1,088,
Visits: 693
|
|
Nice one. I got it right - yay! - though I had to spend 20 minutes reading up (sorry work) first, as I was determined to get it right.
I think the setter was quite correct. If he had said which FINISHES executing first that would be a different matter.
|
|
|
|