• You are probably better off using a Tally table for this:

    CREATE TABLE #TempBet

    (High int, Low int)

    INSERT INTO #TempBet (Low, High)

    SELECT 1, 3 UNION ALL

    SELECT 2, 3 UNION All

    SELECT 5, 8

    ;WITH Tally (n) AS (

    SELECT TOP 100000 ROW_NUMBER() OVER (ORDER BY (SELECT NULL))

    FROM sys.all_columns t1 CROSS JOIN sys.all_columns t2)

    SELECT High, Low, Bet=n

    FROM #TempBet

    CROSS APPLY (

    SELECT n

    FROM Tally

    WHERE n BETWEEN Low AND High) a

    DROP TABLE #TempBet


    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