How to Find Your WordPress Database Name

If you need to know which database your WordPress site uses—for troubleshooting, backups, or moving your site—this guide shows you where to find it.

Method 1: WordPress Manager in Dashboard (Easiest)

The quickest way to find your WordPress database name is through the WordPress Manager.

Steps

1. Log in to your Ecenica Dashboard
2. Click Manage next to your Ecenica hosting service
3. Click WordPress Manager
4. Find your WordPress site in the list
5. Click the down chevron (▼) to expand it
6. Click Database Details to expand the information
7. Your Database Name is shown

To access the database directly:

Click View Database to open phpMyAdmin for that database.

Method 2: Check wp-config.php

Your WordPress database name is stored in the wp-config.php file.

Steps

1. Log in to Ecenica Dashboard
2. Click Manage next to your Ecenica hosting service
3. Click File Manager
4. Navigate to your WordPress installation folder (usually public_html)
5. Find and right-click wp-config.php
6. Click Edit
7. Look for this line near the top of the file:

    define( 'DB_NAME', 'your_database_name' );

The database name is the value in quotes after DB_NAME.

Example:

define( 'DB_NAME', 'ecenic12_wp789' );

The database name is ecenic12_wp789.

Method 3: Check phpMyAdmin

If you have access to phpMyAdmin, you can see all your databases listed.

Steps

1. Log in to Ecenica Dashboard
2. Click Manage next to your Ecenica hosting service
3. Click phpMyAdmin
4. Your databases are listed in the left sidebar

Identifying the correct database:

Click on each database and look for WordPress tables like:

• wp_posts
• wp_users
• wp_options
• wp_comments

The database containing these tables is your WordPress database.

Understanding WordPress Database Names

WordPress database names on Ecenica hosting typically follow this format:

cpanelusername_databasename

Example:

• cPanel username: ecenic12
• Database name: ecenic12_wp789

The username prefix (ecenic12_) is added automatically to prevent database name conflicts.