I’ve been getting these emails daily from DigitalOcean:
Our systems have indicated that your MySQL cluster, [placeholder], has tables without primary keys. We have identified that MySQL tables without primary keys can lead to service replication issues that jeopardize performance and availability. If primary keys are not present for database tables exceeding 5,000 rows, data-loss can occur.
We urge you to take the following actions to ensure that your database [placeholder] continues to operate correctly:
- Review the following product documentation which details the issue and provides clear mitigation strategies for all impacted users.
- Implement primary keys for all database tables as described in the documentation.
See the full details at the following link: https://www.digitalocean.com/docs/databases/mysql/how-to/create-primary-keys/
We will continue to notify you of this issue until all MySQL tables have primary keys.
I used the following SQL query to find tables without indexes:
SELECT t.*
FROM INFORMATION_SCHEMA.TABLES t
LEFT JOIN INFORMATION_SCHEMA.COLUMNS c ON c.TABLE_NAME = t.TABLE_NAME
AND c.COLUMN_KEY = 'PRI'
WHERE c.TABLE_SCHEMA IS NULL
AND TABLE_TYPE NOT IN ('SYSTEM VIEW', 'VIEW', 'CSV');
I found a few tables that didn’t have primary keys, corrected the issue, and now the only remaining tables are:
I created a brand new database and did the same query on the new DB and the results on the new DB matched the results on the old DB. Like both queries returned 51 results.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
DigitalOcean support gave me this alternative query to run to find the problem tables:
It sound one table mine didn’t. The difference between mine and this one is that mine was looking at INFORMATION_SCHEMA.COLUMNS.COLUMN_KEY whereas this one is looking at INFORMATION_SCHEMA.TABLE_CONSTRAINTS.CONSTRAINT_NAME
Hi @jimwigginton,
From you’ve written, I think you’ve corrected the missing primary keys, is that correct? As such you shouldn’t be getting such messages already or are you still getting them?
Hi there,
In addition to what has already been mentioned here, you can now add scalable storage to managed database clusters as shown in this video here:
Best,
Bobby