Is it efficient to archive legacy data from MySQL to another TABLE or should it be another database file?

Posted on by

I’m celebration of a mass a PHP as well as MySQL 4th book by Welling & Thomson. It mentions to be fit we should repository or inform interpretation that isn’t being used often. we was meditative about archiving a bequest interpretation as well as was wondering if in MySQL, does it need to be store in an additional TABLE to do this for a consequence of efeicency or should it be stored in an additional database record itself? Does carrying TABLES that aren’t used mostly in a same database delayed it down? Thanks!

One thought on “Is it efficient to archive legacy data from MySQL to another TABLE or should it be another database file?”

  1. To hit the nail-

    Let the unused data be stored on the different data base.

    If the MySQL provides the option of creating multiple main database file, then you can create one with different file group and create a new table with the same table structure of the table where the unused data exists now, but mention to store this table in a new file group.

    This will reduce the burden on the main database file and also all the primary table exists on this MDF.