Identify the database engine, related website and users. Check application configuration and retain a recent verified export outside the hosting account. Agree a retention period and recovery owner before deleting customer or business data.

1. Open Databases in the correct subscription and locate the exact database.
2. Compare its name and server with the application configuration. Pause or retire any dependent application through its normal process.
3. Export the database and confirm that the archive can be read. Record associated users and required connection details without exposing passwords.
4. Use the database Remove action and read the confirmation carefully. Confirm only the intended database; do not select unrelated entries in a bulk action.
5. After removal, review remaining database users and automation. Remove a now-unused user separately only after checking whether it also serves another database.

Confirm the database no longer appears and that the websites intended to remain active still function. Review application logs for unexpected connection attempts to the removed name.

If Plesk prevents removal because an application or managed relationship owns the database, investigate that dependency instead of deleting files from the database server. If the wrong database was removed, stop affected writes and restore from the approved export into the correct engine. Restoring an older database does not automatically preserve transactions created after that recovery point.

• Exporting and downloading a database dump in Plesk
• Creating a website database in Plesk
• Removing an unused database user in Plesk
• Adding a database user with appropriate permissions in Plesk

• Plesk: Creating Databases
• Plesk: Exporting And Importing Database Dumps