• Rechana Rajan (10/23/2016)


    Eirikur Eiriksson (10/23/2016)


    Rechana Rajan (10/23/2016)


    We are creating a data archive plan for one oof our big table which have more than 8 million records in jusst 8 months . Planning to keep only 6 months record in this and to move rest to another table in another DB

    The advantage in moving to another DB I see is that we ccan reduce the size of existing DB and also the backup size of existing DB will reduce. Do we have a better plan?

    My concerns are both insert into new table and delete from existing table is logged operation which will cause log to grow. Have to do a shrink file to reclaim the space, How can I avoid or better do this?

    Thanks

    If you run the archiving process frequently enough then the sizes are manageable, 1 million rows per month are only 1370 rows an hour on average, suggest you try to set it up to run hourly.

    😎

    Thanks Eirikur. So you think the plan is good? Also how to reclaim space?

    Yes, I think this will do the job with minimum complexity.

    😎

    Reclaiming the space, if necessary, depends on few factors such as the complexity of the schema, number of tables, file and file group setup etc. As a "general" rule, create a new file and file group, move all the user data to the newly created file and then truncate the original file.