Home > Forum > Database > How to handle big BPS_Config database

How to handle big BPS_Config database
0

Hello,
we have a huge AdminServiceLog table in the BPS_Config db that is constantly growing. Is it possible to archive or delete these records without causing side effects?
Are there further optimization possibilities to avoid large data records in advance or to adjust them afterwards?

MVP
In reply to: Celina

Hi Daniel,
thank you for your answer, we do have configured these settings.
Are there other possibilities?

Hi Celina,

since the records should be cleared by the system after 30 days, it should be fine to delete them.

Did you check whether you have more than 100,000 entries in this table?

If this is the case, then the whole maintenance mode is not working well. Maybe the time window is to small and therefore the table doesn't get cleaned up.

Best regards,
Daniel

Did you know that with WEBCON you can automate virtually any process? Even baking cookies 🍪
 
Speaking of cookies: we use the ones that are essential for our website to function properly, as well as additional ones that help us customize our content to your preferences. If you don’t mind cookies, click Accept. If you want to learn more, explore settings.
Settings