Export_task db is huge

Anna Lycett asked on April 24, 2019 16:55

Our client has had issues with database size for their website. We've managed to deal with object versioning, resolving the first issue, but can't seem able to solve the issue with the second largest table, Export_Task. What could be causing it to grow significantly? I've requested an update from them to give me an indication of the DB size change rate since they've logged their ticket and I'm still waiting to hear back from them but when they notified us first, it was at >700k rows, or 30GB worth of data. I've checked scheduled tasks for the site and couldn't see an obvious culprit. Their site is running on Kentico v. 10. Any advice would be welcome!

Correct Answer

Roman Hutnyk answered on May 1, 2019 11:39

Anna, I'd recommend to check what exactly sits in that table, figure out most occurring records in that table - this will give you an idea of an action/event that produced most of the records.

You might want to disable logging of delete task following documentation @ https://docs.kentico.com/k11/configuring-kentico/gdpr-compliance/personal-data-in-kentico#PersonaldatainKentico-Synchronizationtasks

0 votesVote for this answer Unmark Correct answer

Recent Answers

Roman Hutnyk answered on April 25, 2019 07:39

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!

1 votesVote for this answer Mark as a Correct answer

Anna Lycett answered on April 25, 2019 09:54

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.

0 votesVote for this answer Mark as a Correct answer

Anna Lycett answered on May 1, 2019 11:34

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.

0 votesVote for this answer Mark as a Correct answer

Anna Lycett answered on May 1, 2019 12:19

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.

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.