phpMyAdmin is a free and open source website software package written in PHP intended to handle the administration of a database in a web browser.
Frequently used operations (managing databases, tables, columns, relations, indexes, users, permissions, and so on) can be performed via the user interface in addition to having the ability to directly execute any SQL statement.
DreamHost provides phpMyAdmin for customers on shared, VPS, DreamPress, and Dedicated Server hosting options. This article helps you access your databases using the DreamHost-managed phpMyAdmin software.
phpmyadmin.dreamhost.com no longer functions to open phpMyAdmin. Going forward, you must use either the correct hostname for your database shown in the panel (mysql.example.com), or use the official phpMyAdmin hostname of your data center. First, check the Data Center page. Scroll down to locate the data center your MySQL services are located in. It's either West coast or East coast. You can then use the following hostnames to connect depending on the location of your MySQL server.
Before you use phpMyAdmin at DreamHost, you must complete the following steps:
- Add a domain as Fully Hosted or Mirrored on the Manage Websites page.
- Add a MySQL hostname on the MySQL Databases page.
- Allow enough time after adding both the hostname and full hosting for DNS to propagate.
Once you complete these steps, phpMyAdmin will be available on your domain.
Logging into your database
View the following article for instructions on how to locate your database credentials and log into your database:
If you wish to drop/delete a database
You cannot drop a database at DreamHost using phpMyAdmin; you can only delete a database on the MySQL Databases page.
Differences in reported database sizes
Over time, the size of the database reported by phpMyAdmin will start to differ from the actual size of the database on your MySQL server's disk. This occurs because phpMyAdmin shows the database size using the indexes of the database, which can be smaller than the actual disk usage after many read-write cycles.
One possible way to resolve this issue is to optimize your database, although this isn't guaranteed. There are two relatively simple methods that you can use to optimize your database: