• I find it extremely annoying that this does not work:

    DECLARE @Weight FLOAT = 0

    ,@STDate DATETIME

    ,@EDate DATETIME

    SELECT @STDate=MIN(DATECOL), @EDate=MAX(DATECOL) FROM #SAMPLETABLE

    ;WITH Tally AS (

    SELECT TOP (1+DATEDIFF(day, @STDate, @EDate)) n=number-1

    FROM [master].dbo.spt_values Tally

    WHERE [Type] = 'P' AND number BETWEEN 1 AND 100)

    MERGE #SAMPLETABLE t

    USING Tally s

    ON t.DATECOL = DATEADD(day, n, @STDate)

    WHEN MATCHED THEN

    UPDATE SET @Weight = WEIGHTS

    WHEN NOT MATCHED THEN

    INSERT (DATECOL, WEIGHTS)

    VALUES (DATEADD(day, n, @STDate), @Weight);

    SELECT *

    FROM #SAMPLETABLE

    ORDER BY DATECOL

    DROP TABLE #SAMPLETABLE

    When BOL (http://technet.microsoft.com/en-us/library/bb510625.aspx) says that you should be able to SET assign to a local variable.


    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