Home Forums SQL Server 2008 SQL Server 2008 - General Best Way to avoid duplicate rows insertion RE: Best Way to avoid duplicate rows insertion

  • December 13, 2012 at 8:28 pm

    #1568541

    saravanakumar-485245 (12/13/2012)

    But I dont want to delete the records after insertion. Instead I want to skip the duplicate rows while inserting large number of rows.

    You could change your PK to "Ignore Dupes".

    The real key is that I would never ever import data directly to its final resting spot. I ALWAYS use a staging table because I ALWAYS validate the data first. If there are dupes present, it's good to know what they are and how many there are. You might also find out that what you're calling a duplicate, really isn't and that you may have selected an incorrect set of columns as the PK.

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