Transfer a SQL Server database between Plesk and a SQL Server server with SSMS

Procédure

This guide explains how to transfer a Microsoft SQL Server database in both directions: from your Plesk hosting to another SQL Server, or from a SQL Server to Plesk.

SQL Server Management Studio, also known as SSMS, is used to create or restore the backup file used for the transfer. This procedure is based on the SSMS 22 interface and remains valid for its 22.x updates. Microsoft recommends using the latest available update.

Before you begin

To follow this procedure, you must have:

• a Microsoft SQL Server database on your Plesk hosting;
• SSMS 22 installed on a Windows computer;
• a local or remote SQL Server instance on which you are allowed to back up or restore a database;
• sufficient space in your Plesk plan to accommodate the imported database.

LWS Windows hosting currently uses Microsoft SQL Server 2019.

Transfer a database from Plesk to a SQL Server

Download the database from Plesk

1. Log in to your Plesk panel.
2. Open the Databases section.
   
3. [PERSON_NAME] the Microsoft SQL Server database you want to transfer, then click Export dump.
   
4. Check the Automatically download the dump after creation option.
   
5. [PERSON_NAME] the export.

Plesk creates a ZIP archive containing the database backup, [PERSON_NAME] computer.

6. [PERSON_NAME] the ZIP archive.
7. [PERSON_NAME] the name of the resulting file. If this file has no extension, add .bak to the end of its name.

For example:

ma-base-sauvegarde becomes ma-base-sauvegarde.bak

Restore the database in SSMS 22

1. Open SQL Server Management Studio 22.
2. Connect to the SQL Server instance on which you want to restore the database.
3. In the [PERSON_NAME] explorer, right-click Databases.
4. Click Restore Database.
5. In the Source section, select Device.
6. Click the … button.
7. Verify that the selected media type is File, [PERSON_NAME] Add.
8. Select the .bak file extracted from the Plesk archive.
9. Click OK to return to the restore window.
10. Verify that the backup set appears and is selected.
11. In the Destination section, check the name of the database that will be created.

If a database with that name already exists, use another name so as not to overwrite its contents.

12. Click OK to start the restore.
13. Wait for SSMS to display a message confirming that the database was restored successfully.

[ADDRESS] menus correspond to the restore procedure documented for the current SSMS interface.

Transfer a database from a SQL Server to Plesk

Create a backup with SSMS 22

1. Open SQL Server Management Studio 22.
2. Connect to the instance containing the database to transfer.
3. In the [PERSON_NAME] explorer, expand the Databases section.
4. Right-click the database concerned.
5. Click Tasks, then Back Up.
6. In the Backup type field, select Full.
7. In the Destination section, check that the Disk type is selected.
8. Click Add.
9. Specify the name and location of the backup file.

Use a [PERSON_NAME] ending with .bak, for example:

ma-base.bak

10. Confirm the location, then click OK to start the backup.
11. Wait for SSMS to confirm that the operation was successful.

Import the backup into Plesk

Before importing, make sure the backup was created with SQL Server 2019 or an earlier compatible version.

1. Retrieve the .bak file created with SSMS.
2. [PERSON_NAME] only this file into a new ZIP archive.

For example:

ma-base.bak must be inside ma-base.zip

3. Log in to your Plesk panel.
4. Open the Databases section.
5. [PERSON_NAME] the SQL Server database into which you want to import the backup.

The destination database must already exist. [PERSON_NAME], create a new SQL Server database before continuing.

6. Click Import dump.
7. Select the Upload option, depending on the language of your interface.
8. Click Browse, then select the ZIP archive containing the .bak file.
9. Leave the [PERSON_NAME] you do not want to delete the existing database. option.
10. [PERSON_NAME] the import.
11. Wait for Plesk to confirm that the operation is complete.

Plesk accepts the upload of a ZIP archive containing the backup file. The source database and destination database must use the same database engine.

Verify that the transfer was successful

After a restore in SSMS

In Object Explorer:

1. Right-click Databases, [PERSON_NAME] Refresh.
2. [PERSON_NAME] appears.
3. [PERSON_NAME], then open the Tables section.
4. Verify that the expected tables are present.
5. [PERSON_NAME] complete.

After an import into Plesk

1. Check that Plesk displays no error.
2. Open the database with the SQL Server management tool provided in Plesk.
3. Verify that the expected tables and data are present.
4. Check the connection settings used by your site.
5. Test a page or function that uses the database.

Common issues

The backup file does not appear in SSMS

Make sure you have:

• extracted the ZIP archive downloaded from Plesk;
• added the .bak extension to the extracted file if it had none;
• placed the file in a folder accessible by the SQL Server instance.

If your SQL Server instance is remote, the file must be placed on the remote server or in a network location accessible from it.

SSMS says the backup version [PERSON_NAME] is incompatible

[ADDRESS] backup was probably created with a newer SQL Server version than that of the destination server.

A SQL Server 2022 or 2025 backup cannot be restored directly on SQL Server 2019. You must then transfer the structure and data using compatible scripts instead of directly using the .bak file.

The import is refused by Plesk

Check:

• that you are indeed uploading a ZIP archive;
• that the archive contains the .bak backup file;
• that the destination database is a Microsoft SQL Server database;
• that the database size complies with your plan limit;
• that the maximum allowed number of databases has not been reached.

Current limits vary depending on the Plesk plan: the maximum database size ranges from 50 [ADDRESS] to 750 MB.

The database is imported, but the site does not connect to it

After the transfer, check the connection settings saved in your site:

• the SQL server name;
• the database name;
• the username;
• the password;
• the port, if entered manually.

The credentials used on the original server are not [PERSON_NAME] those of the database created in Plesk.