Home Forums SQL Server 2008 SQL Server 2008 - General help with a instead of trigger RE: help with a instead of trigger

  • March 12, 2014 at 7:19 pm

    #1696609

    gfoulks (3/12/2014)

    okay so the table in question has the following columns

    DateTime

    Acct_Number

    SSN

    Script_Code

    Div_indicator

    first_name

    last_name

    ani

    terminate_area

    transfer_area

    Periodically we are getting records in this table where ani = 614xxxxxxx

    We want to prevent all records with the ani = 614xxxxxxx from ever being inserted into the table.

    We thought about doing a scheduled job and purging those records out on a schedule but we thought that if there was a large number of records it could cause some issues with performance and we also have a sync process where this table is being synced to another server which is used for reporting and we don't want to risk having a sync catch these records before our scheduled job had a chance to run and purge the records. It seemed like purging these records in realtime was the best option for us.

    What on Earth do you have against the Columbus, Ohio area? 😉

    Shifting gears back to the problem, is anything in this table encrypted?

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