OroCRM Forums

Covering OroCRM topics, including community updates and company announcements.

Forums › Forums › OroCRM › OroCRM – Installation/Technical Issues or Problems › DB issue with oro tracking extension

This topic contains 1 reply, has 2 voices, and was last updated by  Ivan Klymenko 7 years, 11 months ago.

Starting from March 1, 2020 the forum has been switched to the read-only mode. Please head to StackOverflow for support.

  • Creator
    Topic
  • April 20, 2016 at 6:19 am #27092

    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…

  • Creator
    Topic
Viewing 1 replies (of 1 total)
  • Author
    Replies
  • April 26, 2016 at 11:39 am #27093

    Ivan Klymenko
    Spectator

    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.

  • Author
    Replies
Viewing 1 replies (of 1 total)

The forum ‘OroCRM – Installation/Technical Issues or Problems’ is closed to new topics and replies.

Back to top