Creating a database in Plesk is a straightforward task, but the exact steps depend on your hosting plan, database engine, and permissions. In a managed hosting environment, the hosting provider often preconfigures the database server, limits resource usage, and assigns database access based on the subscription. This guide explains how to create a new database in Plesk, how to choose the right database user, and what to check if the database does not appear or cannot be created.
How to Create a Database in Plesk
Plesk lets you create and manage databases from the control panel without using command line tools. This is useful for websites, content management systems, custom applications, and staging environments that require a dedicated database. Most users will work with MySQL or MariaDB, although PostgreSQL may also be available depending on the server configuration.
To create a database in Plesk:
- Log in to your Plesk control panel.
- Open the website or subscription where you want the database to be used.
- Go to Databases.
- Click Add Database.
- Enter a database name.
- Select the database server if more than one is available.
- Create or assign a database user.
- Save the changes.
Once the database is created, you can connect it to your application, import data, and manage users and permissions directly from the same section in Plesk.
Before You Create a Database
Before adding a new database, it helps to confirm a few details in your hosting environment. This avoids configuration issues and makes sure the database will work with your site or application.
Check your hosting plan limits
Some hosting plans include a limit on the number of databases you can create. If you reach the limit, Plesk may prevent you from adding another database until you remove an existing one or upgrade the subscription.
Confirm the supported database engine
Plesk can manage different database servers, but not all hosting platforms enable all engines. The most common options are:
- MySQL — widely used for web applications and CMS platforms.
- MariaDB — a popular MySQL-compatible option.
- PostgreSQL — used by applications that require advanced relational database features.
If your application requires a specific engine, make sure it is available before creating the database.
Prepare the application details
If you are setting up a database for a website or app, collect the following information in advance:
- Database name
- Database user name
- Database password
- Database server host name
- Database port, if needed
You may need these credentials when configuring WordPress, Joomla, Drupal, Magento, Laravel, or a custom PHP application.
Step-by-Step: Create a Database in Plesk
The interface can vary slightly depending on the Plesk version and hosting provider branding, but the general workflow is the same.
1. Open the Databases section
After logging in, select the domain, subscription, or website where the database will be used. Then open the Databases section in the left menu or under the website tools.
2. Start the database creation process
Click Add Database or a similar button such as Add New Database. This opens a form where you can define the database details.
3. Enter a database name
Choose a descriptive name that is easy to identify later. Good naming helps when you manage multiple databases for one or more sites. For example:
- site1_wp_db
- clientportal_prod
- staging_shop
In many environments, Plesk automatically prefixes the database name with your subscription or system account name. This is normal and helps prevent naming conflicts.
4. Select the database server
If your hosting platform provides more than one database server, choose the correct one from the list. In most shared or managed hosting environments, there will be only one available database server. If you are unsure which one to use, keep the default selection.
5. Create a database user
Every database should have at least one user account. This user is used by the application to connect to the database. In Plesk, you can either:
- Create a new database user during database setup, or
- Assign an existing user to the new database.
Use a strong password and store it securely. Avoid reusing the same password across different services.
6. Set access permissions
Plesk typically lets you choose which privileges the database user should have. For most web applications, the user needs full access to the database it will use. However, if you are creating a user for reporting or read-only tasks, limit permissions to only what is required.
7. Save the database
Click OK, Create, or Save to finish. Plesk will create the database and show it in the database list. From there, you can manage users, import SQL dumps, and open tools like phpMyAdmin if available.
How to Choose the Right Database Name and User
Good database naming and user management are important for long-term maintenance, especially in a hosted environment where multiple sites or staging copies may exist under one account.
Use clear naming conventions
A database name should tell you what the database is for. If you manage multiple environments, include an environment label such as production, staging, or test. Examples:
- shop_prod
- shop_staging
- blog_test
Assign one user per application
It is usually better to create one dedicated user for each website or application instead of sharing one user across several projects. This improves security and makes troubleshooting easier.
Use strong passwords
Choose a password that is difficult to guess and long enough to resist brute-force attacks. If your hosting platform supports password generators, use them. Avoid simple patterns, reused passwords, or credentials stored in plain text.
Where to Find Database Connection Details in Plesk
After the database is created, you may need the server name, database name, user name, and password to connect your application. In Plesk, these details are usually displayed in the database overview.
Typical connection information includes:
- Database name
- Database user
- Password
- Database host or server address
- Port if the application requires it
If your application is hosted on the same server as the database, the host is often localhost. In some managed hosting setups, a remote host name is provided instead. Always use the host value shown by your hosting provider or in Plesk.
How to Connect a Website to the New Database
Creating the database is only one part of the setup. Your website or application must also be configured with the correct connection settings.
For content management systems
For applications like WordPress or Joomla, update the database settings file or follow the installer wizard. Provide the database name, user name, password, and host. If the credentials are correct, the application will connect automatically.
For custom applications
Developers typically define connection settings in a configuration file or environment variables. Make sure the database driver matches the selected engine, such as MySQL or PostgreSQL.
For imported sites
If you moved a site from another server, import the old database into the new Plesk database and then update the application configuration to point to the new credentials. If the application still points to the old database server, the site may display connection errors.
Importing Data into a New Database
In many hosting migrations, you create an empty database first and then import content into it. Plesk usually provides tools for this workflow, often through phpMyAdmin or a built-in database management interface.
Common import steps include:
- Open the database in Plesk.
- Launch phpMyAdmin or the available database tool.
- Select the import option.
- Upload the SQL backup file.
- Run the import and wait for completion.
If the SQL file is large, the import may time out in a browser session. In managed hosting environments, the provider may offer alternate import methods or larger upload limits. If needed, split the backup into smaller parts or ask support for help with the migration.
How to Manage Database Users and Permissions
After the database is created, user management becomes important for security and maintainability. Plesk makes it possible to adjust users without recreating the entire database.
Add a new user
If a different person or application needs access, create a separate user instead of sharing credentials. This helps track access and reduces the impact of password changes.
Edit user privileges
You can often grant or revoke permissions for a user in the database settings. Use the minimum access necessary for the application to function. For example, a site that only reads data should not have write permissions.
Remove unused users
Delete users that are no longer needed. This reduces security risk and keeps the database list cleaner.
Common Problems When Creating a Database in Plesk
Even though the process is simple, users may still run into issues related to hosting limits, server configuration, or incorrect permissions.
The Add Database button is missing
If you do not see the option to create a database, the feature may be disabled for your subscription, or your hosting plan may not include database management. In some cases, the provider restricts database creation to prevent overuse of shared resources.
Database creation fails
Failure to create a database can happen for several reasons:
- You reached the database limit for the plan.
- The database server is unavailable.
- You do not have permission to create databases.
- The database name conflicts with an existing object.
Check the error message carefully and compare it with your plan limits or subscription permissions.
Wrong database type selected
If your application expects MySQL but you created a PostgreSQL database, it will not connect correctly. Verify the engine requirements before setup.
Connection error after creation
If the database exists but the site cannot connect, check:
- Database name spelling
- User name spelling
- Password correctness
- Correct host name
- Database user privileges
A single typo in the configuration file can cause a connection failure.
Permission denied errors
If the database user lacks the required privileges, the application may load but fail when trying to read or write data. In Plesk, review the user permissions and ensure the account has access to the database it should use.
Best Practices for Database Management in Plesk
Following a few operational best practices helps keep your hosting environment organized and secure.
- Create separate databases for production and staging.
- Use unique users for each database or application.
- Change passwords when staff or developers leave a project.
- Keep database names readable and consistent.
- Back up the database before making major changes.
- Remove unused databases to reduce clutter and risk.
These habits are especially useful in managed hosting environments where many websites may be hosted under one control panel account.
How to Back Up a Database in Plesk
Although this article focuses on database creation, backups are part of good database administration. Before editing tables, changing application versions, or importing a large file, create a backup first.
Depending on your hosting platform, you may be able to back up the database using:
- Plesk backup tools
- phpMyAdmin export
- Provider-level backup service
A backup gives you a recovery point if something goes wrong during configuration or migration. This is particularly important for live sites with active traffic.
FAQ
Can I create more than one database in Plesk?
Yes, if your hosting plan allows it. Many subscriptions support multiple databases for different websites, environments, or applications.
Which database type should I use?
Use the engine required by your application. MySQL and MariaDB are common for most PHP-based websites, while PostgreSQL may be required for specific frameworks or custom software.
Do I need a separate user for each database?
It is recommended. Separate users improve security and make access management easier, especially when multiple sites are hosted on the same account.
Why does my database name look different in Plesk?
Plesk may automatically add a prefix based on your subscription or system account. This is normal and helps keep database names unique on shared servers.
Can I change the database name later?
Renaming a database is not always supported directly through the interface. In many cases, you would need to create a new database, import the data, and update the application configuration.
What should I do if the database does not connect after creation?
Check the database name, username, password, host, and permissions. Also confirm that the application is configured for the correct database engine.
Is phpMyAdmin available in Plesk?
Often yes, but availability depends on the hosting provider and server setup. If it is enabled, you can usually open it from the database management section.
Conclusion
Creating a database in Plesk is a basic but essential part of hosting website and application infrastructure. Once you know where the Databases section is, how to choose the correct engine, and how to assign a secure user, the setup process becomes fast and repeatable. In most managed hosting environments, the main things to watch are plan limits, correct permissions, and accurate connection details.
If the database is created successfully but your site still cannot connect, review the host name, credentials, and application configuration carefully. For migrations, remember to back up the database before importing or changing live data. With the right setup, Plesk provides a reliable way to manage databases for production sites, staging environments, and custom web applications.