Extra tables ... how to know what's rubbish and what to keep [#2033749]

Hi there,

After an upgrade from D6 to D7 I find that there are 107 extra tables (and a couple of mismatches that I've already fixed) but I don't really know what to do with that.

I guess that if they are spare they could be deleted from the database, can they? Just to keep things cleaner and save database & back up space.

However I read this just before the list of extra tables;

Tables in the database that are not present in the schema. This indicates previously installed modules that are disabled but not un-installed or modules that do not use the Schema API.

I have un-installed all disabled modules (eventhough some of them were not able to un-install and had to simply delete them)

So, how can I know which tables I must keep and which ones I can get rid of?

Thanks

extra tables

Comment	File	Size	Author
	schemaextratables.jpg	97.37 KB	manoloka

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

manoloka CreditAttribution: manoloka commented 3 July 2013 at 10:33

Looking into the tables seems that all the "field_deleted_data_#" and "field_deleted_revision_#" are tables that were created for the upgrade, most of them has no entries at all.

So I have deleted those ones and everything seems to work fines.

So, I still got 47 extra tables that a I'm not sure what to do with them.

Any suggestions?

Comment #2

jsibley CreditAttribution: jsibley commented 3 September 2013 at 15:38

After upgrading from D6 to D7, I have a similar issue, with 105 tables that are listed as "extra".

Can we assume that tables that are considered core in D7 would not be listed as extra and that, therefore, tables listed in this report are either from D6 core (and no longer necessary) or from contributed modules?

If that's the case, is there any easy way to go from table name to modules that might use that table? Sometimes it seems obvious from the table name (e.g., creativecommons_node) and sometimes it is not obvious. If we can see that a table name belongs to a module that is no longer being used in D7, it might be a good candidate for being dropped (particularly, if there are 0 rows in the table).

Also, what is the risk that there are modules that haven't properly documented the tables they are using and that this could lead to necessary tables appearing in the extra tables report?

Thanks.

Comment #3

ronline CreditAttribution: ronline commented 18 January 2014 at 23:23

I have just dropped 244 extra tables and my site keep on going, so I would say : “Yes the extra tables is rubish and can be deleted”.

Comment #4

Stealth CreditAttribution: Stealth commented 4 March 2014 at 01:47

Issue summary:

View changes

I wont be using this module anymore I deleted the extra tables and it broke my site,I am fortunate that I backed up my data base before I deleted the extra tables.