How to Manage Magento 2 Database Bloat Before It Slows Your Store

Magento 2 stores accumulate millions of stale database rows over time in tables such as customer_visitor, report_event, and quote, leading to slower admin pages, longer reindex times, and larger backups. A mid-sized store handling 200 orders and 5,000 visitors daily can generate 20–40 million redundant rows within a year. Magento's built-in log-cleaning tool, found under Stores > Configuration > Advanced > System, handles core report tables automatically but leaves customer_visitor, customer_log, and catalogsearch_result unaddressed. Custom cron-based scripts can fill this gap by deleting records older than a defined retention period, typically 7–14 days. Regular monitoring using database size queries and scheduling cleanup during low-traffic windows are recommended as part of a long-term maintenance strategy.