Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Database Performance Analyzer (DPA) > DPA - Knowledgebase Articles > Missing MySQL statistics and performance_schema.events_statements_summary_by_digest table is full error in the log file

Missing MySQL statistics and performance_schema.events_statements_summary_by_digest table is full error in the log file

Created by Anthony.Rinaldi_ret, last modified by MindTouch on Jun 23, 2016

Views: 1,163 Votes: 0 Revisions: 2


The DPA log contains a statement like this:

The performance_schema.events_statements_summary_by_digest table is full, some statistics [73 executions] will be lost. Please see the following KB article for more information.


  • All versions of DPA


MySQL statistics are calculated by querying the performance_schema.events_statements_summary_by_digest table. This table has a fixed size that can be changed, but when the table becomes full, any new values not already in the table get grouped in a special NULL row. This allows MySQL to still account for statistics, however it may represent multiple DIGESTS and DPA cannot report which DIGESTS accounted for the changes.

If DPA determines that there is a NULL row within the events_statements_summary_by_digest table that is accumulating statistics, it will report it in the DPA logs. 


To get accurate statistics in DPA, it may be desirable to increase the size of the events_statements_summary_by_digest table in your MySQL instance. This can be done by setting the performance_schema_digests_size system variable to a larger value in the my.ini or my.cnf file and restarting your MySQL service.


To see the current value or to ensure that your change was honored, you can issue the following SQL:

mysql> SHOW VARIABLES LIKE 'performance_schema_digests_size%';

Example Result:


| Variable_name                   | Value |


| performance_schema_digests_size | 10000 |






Last modified