Quite often , in a write - intensive system , data will turn historical and needs to be archived . There are performance gains , such as less records to scan , and reindexing. The sql statements related to deciding which data to archive is application specific. I'm outlining in this post , some cheap and effective ways of saving and storing large amounts of data.I will keep adding to this list
1)Use a tool such as SQLLiteSpeed which can compress 40 GB down to 2 GB.
2)Alternatively you can split the 40 GB into small chunks of a CD size using
some free tool like HJSPLIT