• In looking at this, I don't think you need to use a temp table. However in order to show you how, you'd need to provide:

    - DDL for your [EODVolumeStats] table

    - Some consumable sample data

    - Expected results

    Having said that, if the only issue you're facing is that the summary is occuring over all trade hours of the day, and you only want it over specific hours, perhaps something like this can be used to trim the time period down to an hour.

    DATEADD(hour, DATEDIFF(hour, 0, TradeHour), 0)


    My mantra: No loops! No CURSORs! No RBAR! Hoo-uh![/I]

    My thought question: Have you ever been told that your query runs too fast?

    My advice:
    INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
    The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.

    Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
    Since random numbers are too important to be left to chance, let's generate some![/url]
    Learn to understand recursive CTEs by example.[/url]
    [url url=http://www.sqlservercentral.com/articles/St