2

This question already has an answer here:

I have a content type with 20 different fields.

Now the project requirement changed and I dont need 15 fields of them. So I removed all those unwanted 15fields from content type.

But the database is still holding all the 15 tables and also the revision table, Why? What happens if I remove it?

I feel like having these many unused tables in database might impact the performance. Will it really have impact on the performance?

marked as duplicate by kiamlaluno 7 Dec 16 '16 at 9:18

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

3

I feel like having these many unused tables in database might impact the performance

That's very unlikely, unless the extra disk space used will somehow affect your server's performance.

Deleted fields and data are cleared up on cron runs (by field_purge_batch()), so running cron a few times will probably get rid of them. Exactly how many runs it takes will depend on the number of fields, amount of data in each, etc.

I'd advise against removing it manually unless you're quite familiar with the internals of the field API, and understand the implications.

  • So, it will have implication if I tried to remove it manually? – pown Sep 17 '13 at 10:44
  • 1
    Yes, it might very well. If you have a file field for example, the related files won't be deleted if you just remove the data/revision tables manually. Other modules may have related data that needs to be purged too, which won't happen i f you manually delete. Unless you really, really know what you're doing I'd strongly recommend using the 'proper' method – Clive Sep 17 '13 at 10:46
  • well, I'm looking for 'proper' method to get rid of those tables – pown Sep 17 '13 at 11:01
  • 2
    @pown See the answer - run cron a few times. That's how core does is, so that's the 'proper' way – Clive Sep 17 '13 at 11:02

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