Performance - Separate log tables or leave them in the same database

Asked

Viewed 31 times

-1

everything jewel?

I have a mysql database approximately 180mb in size. Each month the application automatically creates a new table with access logs and actions, which in 14 months are totaling 80mb of disk space.

In my specific case, for some reasons, I find it more interesting to create a new database only for the logs, but in terms of performance and stability (in case of many requests at the same time), what is better? Keep everything together in the same database, or put the log tables in a new database?

Thank you very much!!!

php mysql performance log

  • I also have this question. I even work with two clients whose logo banks are overloaded.

  • The log is the data and events logging engine of a system. In case of failure the log is used as a repair guidance tool. If the database is catastrophically damaged and cannot be restored by you and then have to use an obsolete bkp. How to restore your contractor’s system the current conditions since the log was lost with the database (because it is included in it)?

1 answer

1

Hello, I believe that keeping the logs in the same database becomes better in the matter of separating company or applications through them. But if your concern is to gain storage, I recommend performing backups of this information and once confirmed that they are safe, perform the TRUNCATE

Browser other questions tagged php mysql performance log

You are not signed in. Login or sign up in order to post.