Post reply

set up data archiving

  • October 10, 2019 at 7:15 pm

    #3687843

    Hi,

    We have a purging job from Vendor where it deletes data older than 90 days from several tables. Before we enable this job, we want to archive the data into Archive database.

    Can we just copy data older than 90 days into Archive database and leverage Vendors purging job? Or I should create a procedure where copy and delete happens together and not use Vendor's purging job?

    Can you please shed some light what approach should I follow?

    Please provide me some examples.

  • October 11, 2019 at 8:10 pm

    #3688136

    Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • October 13, 2019 at 5:03 am

    #3688272

    Maybe you can simply modify the vendor's purge job by adding OUTPUT/INTO to their deletes to write to your archive tables.  It would save you from reinventing the wheel.

    Be advised that you should watch page density for indexes on the affected tables.  A starting point would be to rebuild any indexes that fall below 82% page density even if they suffer very little fragmentation.  Don't use reorganize for this if you can help it.

    Of course, if the vendor is doing RBAR deletes, then you should probably roll your own.

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

  • October 28, 2019 at 4:46 pm

    #3692468

    So, just out of curiosity, what did you end up doing here?

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

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply