CiviCRM Community Forums (archive)

Each import generally takes at least a few attempts before all of the errors are corrected. For data sets that include individuals, organizations, memberships, participation, and so on, a fair number of temporary tables get created when importing from csv files. Shouldn't we be dropping these tables? Or is my db filled with a few dozen because we've doing something wrong?

I’m hesitant to add a hard table cleanup to every failed import, as the tables’ contents might hold some clues why the import failed (and imports shouldn’t fail to begin with).

I’m definitely happy with Lobo’s idea to clean the import tables on upgrades; that makes a lot of sense – first, that’s a point when one’s either generally happy with their imports or wants to try from scratch with the new version; second, I can foresee us changing the tables’ schemas at some point, and having legacy import leftover tables would only add confusion.

I filed CRM-5645 to track this.

In the mean time, I had a question about this, as my DB is growing, I found these tables and was wondering if it is safe to delete them from the DB?

We have been actually in production for over two months now, and the contact db seems fine. I think these were the result of fine tuning imports, in particular duplicate or invalid emails.

Thanks a lot Piotr. Did it and everything looks fine.