What is the best practice for import set tables not being used and import sets in a Loaded State?

[Cupcake]

I was testing loading some data which created an import set table. It is only test information, which is in a state of "Loaded".

a) Is there a way to deactivate it vs. delete? If not, what are the drawbacks if any if you delete the import set table?

b) Also, I have an import set that I really will be using in a catalog item as a Lookup Select Box (which references the table created via the import set). That import set is also in a Loaded state. What happens if you don't transform the data?

Thanks,

Karen

[Mike Allen]

There is a Cleanup module for deleting import set tables.   I always name my import set tables with a TEMP suffix so I can easily spot them and remove them in the Cleanup process.

[Mike Allen · Accepted solution]

[Cupcake]

Thank you Mike. I am marking this as the correct answer. Not sure if you saw part II (b) of my questions:

Also, I have an import set that I really will be using in a catalog item as a Lookup Select Box (which references the table created via the import set). That import set is also in a Loaded state. What happens if you don't transform the data?

[Mike Allen]

I think that the Import Set Deleter under Schedules Cleanup deletes records older than 7 days, so it will not be a permanent table.