ssossossosso

Forums

Covering OroCRM topics, including community updates and company announcements.  Subscribe

This topic contains 1 reply, has 2 voices, and was last updated by Ivan Klymenko Ivan Klymenko 1 year, 4 months ago.

  • Creator
    Topic
  • #17627

    modli
    Participant

    DB at OroCRM server became really big, so that oroCRM instance can not start. It looks like the reason is oro tracking extension. Can you advise how to keep DB in reasonable limits? Is there a ready solution for it? Smth like: keep records of registered users only, keep records of the last 30 days only…

Viewing 1 replies (of 1 total)
  • Author
    Replies
  • #17694
    Ivan Klymenko
    Ivan Klymenko
    Oro Core

    Hi modli,
    unfortunately we don’t have any cleanup procedure or command for the tracking data. And this will be good improvement, so we added it to our backlog.
    For now, you can cleanup this data by SQL query in tables oro_tracking_data and oro_tracking_event. We store raw tracking data there. By default we don’t have any tricky relations there, but in this case if you have some in your instance – you should do this carefully.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.