Create and connect a database

Before you begin

Check whether the website needs a database

WordPress and many CMS, shop and membership applications store content and settings in a database. A static HTML/CSS website and a Sitejet-generated site normally do not need you to create one manually.

• Application requirements: Confirm the supported database type and version.
• Target domain: Open the Plesk subscription that actually hosts the website.
• Existing data: Keep the original SQL dump and export the current target before replacing anything.
• Configuration access: Know which application file or installer will receive the credentials.

Create the database

Add a database and dedicated user

1. Open the hosting service in Plesk. Use the Client Area Log in to Plesk shortcut.
2. Go to Websites & Domains, then Databases.
3. Choose Add Database. Enter a descriptive name and associate it with the correct related site when Plesk offers that choice.
4. Create a new database user. Use a unique name and generate a strong password.
5. Grant access to this database. Keep remote access disabled unless the application genuinely connects from another server.
6. Save the database. Record the database name and user securely for the immediate application setup.

Application connection

Use the details shown by Plesk

Open Connection Info beneath the database when available. A website running on the same hosting service commonly uses a local database host such as localhost, but the application's requirements and the value displayed in Plesk take precedence.

Database host

The hostname shown by Plesk or required for the local service.

Database name

The complete saved name, including any automatic prefix.

Database user

The dedicated user assigned to this database.

Password

The strong value created for that user; Plesk will not expose it publicly.

Existing website

Import an SQL dump carefully

1. Confirm the empty or intended target. An import can add to or conflict with tables already present.
2. Keep the source dump unchanged. Store a separate copy before editing or compressing it.
3. Open Import Dump for the exact database in Plesk, or use phpMyAdmin for an appropriate smaller SQL file.
4. Select the dump and start the import. Do not close the panel or submit the operation repeatedly while it runs.
5. Check the result. Confirm expected tables appear and review any reported SQL or character-set errors.

Large databases may exceed browser upload or execution limits. Open a support ticket with the dump size and database name rather than repeatedly attempting a failing import.

Verify the application

Update the configuration and test real functions

• Enter the host, complete database name, user and password exactly.
• Confirm the application can connect without exposing a detailed database error publicly.
• Test login, content editing, search, forms, orders or other database-backed functions.
• Review the application and Plesk logs if the site shows a generic 500 error.
• Remove installation scripts and temporary database dumps from the public document root.

Ongoing management

Back up before schema, user or password changes

Use Plesk to export an SQL dump or include the database in a hosting backup before application upgrades and major changes. If you change a database-user password, update every application or scheduled task that uses it at the same time.

Need help?

Send diagnostics without credentials

Include the domain, assigned UKC server, application, database type, database name, dump size, action attempted, time and exact error. State whether the database is new or contains production data. Never include its password or an unredacted configuration file.