On Premiss Server Slowing Down - SQL Log files ?

Hi Thibaut,

1. The purpose of the Tracker is explained here: https://support.sugarcrm.com/Knowledge_Base/Reports/Understanding_Tracker_Reports/index.html 

2. The Tracker usage is configurable via Administration (navigate Administration -> Tracker)
It looks like this:

3. If Tracker is enabled, it can collect A LOT of data. For such case, there is out-of-the-box Job that does clear the table regularly

I'd suggest checking whether Job is Active and actually run 

If the Job is active and running regularly, the Tracker itself may contain important information useful for finding the performance bottle-neck and that is from what performance optimization starts.
What performance optimization usually includes you can read here: SugarCRM Performance Tuning. Optimize Your CRM System | Integros 

If you have any questions feel free to reach out to me dch@integroscrm.com 

All the best,

Dmytro Chupylka

Hello, 

Just in case someone reads this discussion while being in trouble with his data base, if found the tables and the fixing commands to get rid of these over sized tables, 

1st command :  mysql -u [user] - p 

2nd command : use [database];

3nd Command : 

SELECT        table_name AS `Table`,      round(((data_length + index_length) / 1024 / 1024), 2) `Size in MB`  FROM information_schema.TABLES  WHERE table_schema = "[database]" ORDER BY `Size in MB`;

4th Command : to truncate the over sized  table, 

truncate [table names];

I got rid of  "tracker" and "activities" 

don't forget to replace the data base and user name in the commands. 

Thank you for reading 

Hello, 

Just in case someone reads this discussion while being in trouble with his data base, if found the tables and the fixing commands to get rid of these over sized tables, 

1st command :  mysql -u [user] - p 

2nd command : use [database];

3nd Command : 

SELECT        table_name AS `Table`,      round(((data_length + index_length) / 1024 / 1024), 2) `Size in MB`  FROM information_schema.TABLES  WHERE table_schema = "[database]" ORDER BY `Size in MB`;

4th Command : to truncate the over sized  table, 

truncate [table names];

I got rid of  "tracker" and "activities" 

don't forget to replace the data base and user name in the commands. 

Thank you for reading 

Thibaut, did truncation fix the slowdown observed?