Identify the complete prefixed database name and verify which websites, scheduled jobs or integrations use it. Export a current backup and confirm it is readable. A similar-looking database name can belong to a different production site.

1. Review application configuration and installation records to confirm the database is no longer needed. Disable retired jobs that would continue trying to use it.
2. Download and label a final SQL backup, then store it outside the hosting account. If retention rules apply to its business data, follow the approved retention process.
3. Open MySQL Management and select only the intended database.
4. Choose Delete and read the confirmation. Check the full database name again before accepting the permanent removal.
5. Review the remaining database users and grants. Remove an unused user only after confirming it is not shared with another active database.

Confirm the intended database is no longer listed and that unrelated websites still function. Monitor logs for a forgotten dependency, and update your application inventory to show the retirement.

If the wrong database was deleted, stop unnecessary writes and contact support while preparing the verified backup for an authorized restore. Do not create empty replacement tables and assume the application data will return. If you are unsure whether a database is active, investigate its configuration and usage before deleting it.

• Downloading an SQL database backup from DirectAdmin
• Creating a MySQL or MariaDB database in DirectAdmin
• Creating an additional database user in DirectAdmin
• Restoring selected account data from a DirectAdmin backup

• DirectAdmin: Mariadb MySQL