Export_task db is huge

According to documentation Kentico creates export tasks when an object is deleted. I'm 100% sure how it works, but I'd like to ask if you're using export at all? If you do not envision a need for an export you could disable logging into that table in Settings.

Another option is to process necessary task, so system deletes records, or simply clear it if you don't need to process them.

Other thinks those might cause DB size growth:

• online marketing activities tracking - see best practice here
• storing files into a database

Hope that helps!

Ahoj Roman, thanks for your help. I don't think export is being used much, if at all, so it could well be to do with objects being deleted. However, object versioning has been disabled - is it at all likely to have helped? Where in the settings would you switch the logging off if it's not in object versioning? Like I said, I'm still waiting for the client to respond with updated DB sizes, but in the meantime want to make sure that we've got it sorted for them as best as we can. Thanks again for your help.

Just heard back from the client, the number of export_task DB rows increased from 7186049 on 9 Apr to 7276468 on 29 Apr. I would appreciate if you could guide me in what might be causing this. Object versioning is currently off and the size of the DB it was saving to has plateaued, so something else must be causing this increase.

Thanks, Roman, I think that'll do it! Just checked that logging export tasks in Staging is enabled, so most likely that's the cause. Unlikely that the client will want to keep it enabled. Thanks again.