Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a write heavy application. Approx 5lac+ inserts per day in a MySQL table. I have master <> master -> slave. Performance is not an issue here.

I need your inputs with regards to management of the data. After a certain ammount of time I'd see the table becomes bulky and I would like to discard old records; though I'd be needing them later. I want to discuss the best way to keep this data.

Partitioning on monthly basis is the one way I can think of.

share|improve this question

You need to implement some type of archiving. This can be done in several ways:

  1. Your application can insert in two tables instead of one (active + archive). When you need to remove some data from the active table, you will be fine as you have another copy.
  2. You can implement some type of DB triggers on delete from the active table. The trigger will insert the deleted records in the archive table.
  3. You can use DB partitioning.
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.