• Ray K (10/21/2010)


    Okay, that's what I figured.

    I ended up just creating a simple SELECT statement for the column immediately following the INSERT. I'm just writing a quick 'n dirty, and it's insignificant enough that having to create a TABLE variable for it would be unnecessary overkill.

    Thanks!

    Say what? Overkill???

    DECLARE @test-2 TABLE (Col1 uniqueidentifier);

    INSERT INTO .....

    OUTPUT i.MyUniqueIdentifierColumn INTO @test-2

    ....

    SELECT * FROM @test-2;

    Wayne
    Microsoft Certified Master: SQL Server 2008
    Author - SQL Server T-SQL Recipes


    If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!
    Links:
    For better assistance in answering your questions
    Performance Problems
    Common date/time routines
    Understanding and Using APPLY Part 1 & Part 2