Home Forums SQL Server 2005 Development BCP Trigger Hangs up Insert Statement RE: BCP Trigger Hangs up Insert Statement

  • April 25, 2008 at 7:28 pm

    #807463

    Another problem other than the ones already stated is that even if all of this worked correctly, BCP destroys existing files and overwrites them.

    I may have a work-around for this, but I need to know... why do you only want 1 of the inserted rows instead of all that have been inserted?

    --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)