Archive vs Delete and Separate Database

  • Resolved ianstudio

    (@ianstudio)


    4 months, 3 weeks ago

    Hello, we're using the free version on a site, but the database is getting very big due to Burst stats.

    I'm thinking of deleting all the data, but it's kind of sad losing it.

    I don't understand the functionality Archive versus Delete, what does it entail?

    Is it a file that can be downloaded? As a CSV, for example ?
    What does Automatically Archive entails exactly and what happens when you Automatically Delete using your tool? Is it instantaneous ?

    Or should I remove the plugin completely and it would delete its Tables in the database ?

    I can't find very specific answers as to how to handle this.

    But what I do know is that I want to trim the size of that database because the Burst stats are getting way out of hand.

    Also, maybe with the pro version, is there a way to handle the data in a separate database that is not crowding that of the site itself ?

    Thanks

Viewing 1 replies (of 1 total)
  • Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    4 months, 3 weeks ago

    Hi @ianstudio,

    The difference between deleting and archiving is that deleting removes the data without option to restore it, and archiving stores the data in zip files in the uploads directory. It can be restored again using the archiving interface. You can download the files in the meantime to clear up space, and upload them back later.

    If you delete the plugin, and choose the option to delete all data, all tables will be deleted.

    It is possible to set up Burst in a different WordPress website, so you have your own cloud. If you use cookieless tracking this means that you can’t use hook goals, as hook goals are tracked server side, and it’s not possible to link cookieless visits to server side goals on such a cloud setup (yet).

    This feature will be released in Burst Pro soon, but is currently only available in beta. If you’d want to use that, best to contact us through support to set this up.

    As the table size doesn’t really impact the rest of the site performance wise, you can also choose to leave it as it is. But if your host puts restrictions on the database size you can choose from the above options.

    Let me know what you prefer!

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.