Use phpMyAdmin in cPanel

With phpMyAdmin you can manage your web hosting databases directly via the browser. You can view databases and tables, browse records, run SQL queries, and import and export databases.

phpMyAdmin is a powerful tool. Changes are made directly in the respective database and can therefore have an immediate impact on your website or web application.

In this guide, we will show you how to open phpMyAdmin in the CURIAWEB cPanel, navigate the interface, view tables and records, and safely use typical functions.

Attention: Do not delete or modify tables or records in a production database on mere suspicion. Always create a current backup before making major changes.

What is phpMyAdmin? #

phpMyAdmin is a web-based management interface for MySQL-compatible databases.

Instead of executing database commands exclusively via a command line, you can perform many tasks using a graphical user interface.

This includes, for example:

• Select databases
• Show tables
• Examine table structures
• Search and browse datasets
• Execute SQL queries
• Export databases
• Import SQL files
• Optimize or repair tables, if supported

When do you need phpMyAdmin? #

In normal daily website operations, you often don't need to open phpMyAdmin at all.

Typical areas of application include, for example, a website migration, a database backup, a targeted error analysis, or an administrative change that cannot be made via the web application itself.

Basic rule: If a change can be made safely via WordPress, an e-commerce system, or another application, this method is often better than a direct change in the database.

1. Log in to cPanel #

Log in to your CURIAWEB cPanel.

Then open:

Databases → phpMyAdmin

cPanel will then open the phpMyAdmin interface for your hosting account.

No separate access credentials required? #

When you open phpMyAdmin via the corresponding function within cPanel, access typically occurs in the context of your logged-in hosting account.

You should therefore not try to enter other database access credentials into an unfamiliar phpMyAdmin login page on suspicion.

2. Understanding the phpMyAdmin interface #

After opening, you typically see a navigation on the left with the databases available for your account.

Depending on your selection, information and tools are displayed in the main area.

The exact appearance may vary slightly depending on the installed phpMyAdmin version, language, and screen size.

Left navigation: Databases and tables #

The left sidebar is particularly important for navigation.

There you can select a database and then open its tables.

A simplified structure could look like this, for example:

kunde_wordpress
├── wp_options
├── wp_posts
├── wp_postmeta
├── wp_users
└── ...

Important: In WordPress, the table prefix does not wp_ loudly. An installation can use a different prefix.

3. Select the correct database #

Click on the database you want to work with in the left-hand navigation.

Check the full database name carefully.

For example, a cPanel database name can look like this:

WordPress customer

If multiple websites are hosted within your hosting account, several similarly named databases may exist.

Attention: Before every change, check whether you really have the correct database open. A change to the wrong database can affect another website.

How do I find out which database my website is using? #

The database used is usually specified in the configuration of the respective application.

In WordPress, you can usually find the database name in:

wp-config.php

There, the database name is passed via:

DB_NAME

determined.

If you need to set up databases first, you can find the procedure under Create MySQL database in cPanel.

4. Display database tables #

After selecting a database, phpMyAdmin displays the tables it contains.

A table stores data in a structured form of columns and rows.

An application typically uses multiple tables for different tasks.

What does a table mean? #

Simply put, you can think of a database as a container holding multiple structured tables.

Database
├── Table A
├── Table B
├── Table C
└── Table D

Each table in turn has a defined structure and contains data records.

Detect WordPress tables #

For example, in a WordPress installation, there may be tables with names like these:

wp_posts
wp_postmeta
wp_options
wp_users
wp_usermeta
wp_terms
wp_term_taxonomy
wp_term_relationships

Depending on the installation, plugins, and table prefix, the actual names may vary.

The WordPress prefix is not always wp_ #

Many examples on the internet use:

wp_

as a table prefix.

However, that is not mandatory.

An installation could, for example, include tables such as:

abc_posts
abc_options
abc_users

use.

Therefore, base your approach on the actual installation and not exclusively on examples from manuals.

Plugins can create additional tables #

WordPress plugins can create their own database tables.

If you see tables whose names are unknown to you, this does not automatically mean that they are redundant.

Attention: Never delete unknown tables just because you do not know their name. They might be required by an active plugin, theme, or another function.

5. Open table content with „View“ or „Browse“ #

If you want to view the stored records of a table, select the corresponding table and open the function to view or browse the contents.

Depending on the language setting, the function can, for example, be Ads or Browse be designated.

phpMyAdmin then displays the existing data records in tabular form.

Data sets are single rows #

To put it simply, a table row corresponds to a data record.

The individual columns contain its values.

In an application, such values can contain, for example, IDs, names, settings, time data, or other structured information.

6. View the structure of a table #

About the function Structure or rather Structure can you see which columns a table consists of.

There, depending on the table, you will find information on, for example:

• Column names
• Data types
• Default values
• Indices
• Primary keys
• additional database properties

This view is especially helpful if you want to understand how a table is structured.

Important: You should not change the table structure of a production application on a whim. An incorrect change to columns or indexes can damage the application.

„Differentiate between “display„ and “structure" #

These two areas are frequently confused by beginners.

Browse displays the saved records.

Structure shows the technical structure of the table.

Displays → What data is stored?

Structure → How is the table structured?

Search records #

With the search function of phpMyAdmin, you can specifically search for values within a table.

This is much safer and more efficient than manually scrolling through thousands of records in large tables.

Select the relevant table and open the search function.

Then enter the desired value or search criteria.

Select the correct table before searching #

First, consider in which table the requested information is likely stored.

In WordPress, for example, different types of information are located in different tables.

A general search or modification across all tables should not be performed without a specific reason.

8. Edit single record #

phpMyAdmin allows existing records to be edited directly.

To do this, select the relevant data record and the editing function offered.

Only change the value that you actually want to change.

Check before saving:

• correct database
• correct table
• correct data set
• correct field
• new value

Attention: Direct database changes bypass the checks and business logic of the respective web application. A technically storable change is therefore not automatically a valid change for the application.

Why changes through the application are often better #

For example, if you can change a setting in WordPress via the administration area, this change should normally be made there.

WordPress or a plugin can perform additional checks, calculations, or dependent changes in the process.

When making direct changes via phpMyAdmin, such application steps might not take place.

9. Delete dataset #

phpMyAdmin also allows the direct deletion of individual records.

You should use this function with special caution.

A data record may be linked to other data. Manual deletion can therefore lead to inconsistencies or functional problems.

Attention: Delete a data record only if you know exactly why it needs to be removed and what impact that has on the application.

10. Using SQL Area #

About the area SQL you can send custom SQL statements directly to the selected database.

This can be used, for example, to query or modify data.

A simple read query can generally correspond to a form like this:

SELECT * FROM tablename;

However, SQL can also modify or delete data.

Important: Do not execute SQL commands from internet forums, AI answers, or unknown guides if you do not understand their effect. A single command can alter or delete large amounts of data.

SELECT, UPDATE and DELETE are not the same #

SQL commands have different tasks.

Simplified:

SELECT → Read data

UPDATE → Modify existing data

INSERT → Insert new data

DELETE → Delete records

A reader SELECT-command must therefore be evaluated fundamentally differently than a UPDATE- or DELETE-Command that modifies production data.

WHERE clause particularly important during modifications #

In SQL statements that modify or delete data, a condition frequently determines which records are affected.

An error in such a condition can modify significantly more data records than intended.

Therefore, do not perform manual mass changes on a production database unless you are fully confident in your SQL skills.

11. Export database #

About the area Export Can you export a database or selected tables into a file?.

Such an export is often used for:

• manual backups
• Website migrations
• local development environments
• Backups before database changes

used.

We cover the complete procedure under Export database with phpMyAdmin.

Export first before making changes #

If you want to manually edit a production database, you should create a current export beforehand.

This way, at least you have an initial backup of the database before your change.

Practical Tip: When you think „This is just a small database change,“ exactly then an export before the change is quickly done and especially useful.

12. Import database #

About Import for example, you can import an existing SQL file into a database.

This is frequently needed during website migrations or restorations.

You can find the exact procedure at Importing a database with phpMyAdmin.

Attention: Before an import, make sure to select the correct target database. The contents of an SQL file can create, alter, empty, or drop tables.

13. Using operations #

Depending on whether you have selected a database or a table, phpMyAdmin provides in the area Operations additional administrative functions available.

These may concern table or database operations, for example.

Since some of these functions can make far-reaching changes, you should only use them if you know their exact effect.

„Do not confuse “Empty„ and “Delete" #

With database tables, there is a crucial difference between removing the contents and removing the table itself.

Empty or rather TRUNCATE removes the contained data records while keeping the table structure intact.

Delete or rather DROP removes the table itself.

Attention: Both actions can have serious consequences on a live website. Do not use „Empty“ or „Delete“ to clean up unknown tables.

What does DROP mean? #

An SQL command like:

DROP TABLE tabellenname;

removes the table in question.

This is not a normal cleanup of individual data records.

If an application requires this table, it may no longer function correctly afterward.

What does TRUNCATE mean? #

A command like:

TRUNCATE TABLE tabellenname;

basically removes the records from the table, but leaves the table structure intact.

This can also cause complete data loss within this table.

Do not „clean up“ the database by deleting unknown tables #

Older websites can accumulate many tables.

Some may come from plugins or previous extensions.

However, the table name alone is not enough to reliably determine whether a table is still needed.

If you do not clearly know the origin, you should not delete it.

14. Sorting tables #

When viewing a table, you can sort records by specific columns depending on the interface.

This can be helpful, for example, to:

• find latest datasets
• comparing IDs
• to present certain values more clearly

Sorting the display does not automatically change the saved data.

15. Adjust the number of displayed records #

Large tables can contain thousands or millions of records.

phpMyAdmin therefore usually displays only a limited portion at a time.

Use navigation, search, or filters instead of trying to render a very large table completely in the browser.

Large tables can be sluggish #

With extensive databases, certain operations can take longer.

This applies in particular to complex searches, large exports, imports, or changes to very large numbers of data records.

Do not unnecessarily abort such processes multiple times and restart them in parallel.

16. Check table information #

Depending on the view and database, phpMyAdmin can display information such as size, number of records, character set or collation, or table status.

This information can be helpful for a technical analysis.

Do not change the character set or collation of a production database on a whim.

Do not change character set and collation arbitrarily #

Character sets determine how text can be stored. Collations influence, among other things, comparisons and sorting of text.

An ill-considered change can cause problems with characters, comparisons, or data in existing applications.

If a website is working correctly, there is usually no reason to change these settings solely based on a recommendation from an outside guide.

17. Optimize table #

phpMyAdmin can offer administrative operations, such as optimization, for suitable tables.

Whether such a measure is sensible or even relevant depends on the database or table format used and the specific condition.

Do not perform optimizations regularly just because the feature is available.

18. Repair table #

For certain table types, phpMyAdmin can offer repair functions.

However, a repair is not a general solution for every slow or buggy website.

When a table is reported as damaged, the specific error message and the affected table type should be checked first.

Important: „Repair table“ is not a preventative maintenance function that you should regularly apply to all tables.

phpMyAdmin shows a warning or error message #

If phpMyAdmin reports an error during an operation, read the message completely.

For example, it can provide indications of:

• SQL syntax error
• missing permissions
• non-existent tables
• Import issues
• Size or runtime limitations

give.

Do not repeat the same failed operation without checking the cause.

phpMyAdmin import fails #

For larger SQL files, an import can fail due to upload, execution time, or other technical limits, for example.

We cover targeted troubleshooting under phpMyAdmin import not working: Errors and large SQL files.

phpMyAdmin is not a file manager #

phpMyAdmin manages databases and their contents.

Website files such as:

index.php
wp-config.php
.htaccess
style.css

does not manage phpMyAdmin.

For example, you use the cPanel File Manager or FTP access.

Database is not the same as website files #

On a WordPress website, for example, posts and many settings are located in the database, while themes, plugins, and uploaded media files reside in the file system.

For a complete manual backup or migration, you must therefore take both areas into account.

phpMyAdmin is not a complete backup system #

A database export via phpMyAdmin backs up the selected database contents, but not automatically your website files, emails, or the entire hosting account.

An SQL export is therefore only one component of a complete website backup.

Change WordPress URL directly in the database? #

Certain WordPress settings can in principle be stored directly in the database. Nevertheless, you should not change URLs recklessly via a blanket SQL search-and-replace action.

WordPress, themes, and plugins can store data in various formats. Among these can also be serialized or otherwise structured values.

Attention: Blindly searching and replacing domain names directly throughout the entire WordPress database can corrupt stored data. Use a method that correctly accounts for the application's data structures.

Edit WordPress users directly in phpMyAdmin? #

WordPress user data is stored in the database. However, this does not mean that changes to user accounts should generally be made directly via phpMyAdmin.

If the WordPress administration area is accessible, use the WordPress functions provided for normal user management.

Direct database interventions should be limited to specific problem cases.

Do not write passwords as plaintext into database fields #

Applications can store passwords in a specially processed form.

If you overwrite a password field directly in phpMyAdmin with a plaintext password, it does not automatically mean the application will be able to use that password correctly afterward.

Use the password change or recovery function of the respective application if possible.

Accidentally selected a database – is that dangerous? #

Simply opening or selecting a database does not change its contents.

Displaying a table is also fundamentally a read-only action.

Functions that actually modify data or structures become especially dangerous.

This includes, for example:

Edit
Delete
Empty
DROP
TRUNCATE
UPDATE
DELETE
INSERT
ALTER

Distinguish between read and write operations #

For safe work with phpMyAdmin, a simple distinction helps:

Action	Typical effect
Select database	Navigation only
Show table	Read data
View structure	Reading structure
Search	Search data
Export	Output data
Edit	Modify data
Import	Can modify data and structures
Empty	Remove table contents
Delete	Remove table or object
SQL	Effect depends on the executed command

Create an export before making manual changes #

When you have to work directly on a production database, a prior export is an important security measure.

Therefore, the order should ideally be:

Check the correct database
        ↓
Export database
        ↓
Check planned change
        ↓
Perform change
        ↓
Test website

Test website immediately after a database change #

When you have made a change, test the website or function in question immediately afterward.

Do not wait until after many more changes to check if everything still works.

This makes it much easier to trace an error back to the change that caused it.

Do not make multiple changes at once #

When diagnosing an error, do not change multiple database values at the same time.

Change one point, save it, and then test the application.

This is how you can track which change actually had an effect.

Close phpMyAdmin after work #

When you have finished your database work, you should not leave phpMyAdmin open unnecessarily—especially on shared computers.

After administrative work, also end your cPanel session when you leave the computer.

Recommended procedure for safe working with phpMyAdmin #

1. Log in to cPanel.
2. Open Databases → phpMyAdmin.
3. Identify the correct database.
4. Check the complete database name before making any changes.
5. Open the required table.
6. First use reading functions like view, structure, or search.
7. Create a current export before making any writing changes.
8. Change only the actually required value.
9. Check the change.
10. Test the website immediately afterwards.

Recommended procedure for an unknown table #

1. Do not delete the table.
2. Check their name and the table prefix.
3. Check which website the database belongs to.
4. Check if a plugin or an application uses the table.
5. Create a backup before every planned removal.
6. Remove the table only if its function and dispensability have been clearly determined.

Basic rule: In phpMyAdmin: First understand, then back up, then modify. Not the other way around.

When should you contact support? #

If you receive an error message during a database operation or are not sure which database belongs to a website, you should not modify or delete tables on guesswork.

For an analysis, the following information is particularly helpful:

• affected domain or application
• full database name
• affected table, if known
• desired action
• exact phpMyAdmin error message
• whether any changes have been made previously
• whether a current backup exists

Do not transmit any database passwords or complete configuration files containing access credentials.

Summary #

You open phpMyAdmin in the CURIAWEB cPanel under Databases → phpMyAdmin. There you can select the databases of your hosting account and manage their tables, structures, and data records.

The functions Ads, Structure and Search help you analyze data. About SQL direct database commands can be executed against it, the effect of which can range from a simple query to the modification or deletion of large amounts of data.

Special care must be taken with functions such as Edit, Empty, Delete as well as with SQL commands like UPDATE, DELETE, TRUNCATE or DROP required.

With WordPress, you should also note that the table prefix is not necessarily wp_ and plugins can create additional tables. Unknown tables must therefore not simply be regarded as redundant.

Create a current export before making manual changes to a production database and test the website immediately after every change.