• John Rowan (10/8/2015)


    Great solution Jeff. I'd say that would work great as long as the OP has the ability to create tables for their ETL. I've worked on projects where all of the ETL has to be done within SSIS so the option of staging the data and pulling it back out is not always available. This is one of those things that ETL developers go back and forth on....how much of the work can/should we do on the DB engine versus solely in SSIS. Speaking for myself, I sometimes have blinders on when it comes to things that could more easily be done in the DB engine just because I develop in SSIS so often.

    Thanks for the feedback, John.

    I think the reason I'm so DB Engine prone rather than using SSIS is that I don't have the same sometimes unreasonable fear of using xp_CmdShell to do the exports that a lot of people have. To wit, I've never personally used SSIS myself. About the closest I've come is to write scripts/procs for folks that needed it.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)