There are scenarios where multiple databases for multiple domains have to be restored.

In such cases, it would be great to be able to mass import dumps from database backup files instead of going one by one manually importing them on a domain basis

The possibility to setup a replication for MySQL

phpPgAdmin support was dropped starting from Plesk Onyx 17.8
This means that Plesk does not have any management tool for Postgres databases shipped with it.

I suggest to include pgadmin in Plesk installation since the latest ve
rsion of this software (2018-09-06 - pgAdmin 4 v3.3 Released) has just been released, with adequate security. More info about it you can find here:
https://www.pgadmin.org/

Allow setting more granular permissions for the DB users
For example to allow a user to only edit certain tables of the database.

Add .accdb and newer Excel versions to ODBC DSN. Currently, only .mdb and .xls up to Excel 8.0 are available (beside MySQL). Newer versions of database file formats should be supported by this feature.

At the moment it is not possible in Plesk for Linux to limit the MySQL database size.

Like stated in this article:
https://support.plesk.com/hc/en-us/articles/115000821325-How-to-limit-MySQL-databases-size-for-Plesk-subscription-

In Plesk for Windows apparently this feature is already implemented.

I would really look forward for this function.

What I have seen so far in the changelog for Plesk Obsidian, this is not listed so I assume this feature has not made it in to the new Plesk version.
:(

show the php conection string when setting up a mysql database.

the old hosting would show you a connection string that could easily be copied over to the config files.

Hi all you must provide some dba level db command to database user. This can help lot, in indexing and shrinking database

Plesk repair db should fix issue "Integrity constraint violation: 1062 Duplicate entry for key 'PRIMARY'"
https://support.plesk.com/hc/en-us/articles/115003292185-Unable-to-create-object-in-Plesk-SQLSTATE-23000-Integrity-constraint-violation-1062-Duplicate-entry-for-key-PRIMARY-

It should be a simple matter to incorporate the default collation as a feature in the "Tools & Settings: Database Servers: Database Hosting Settings" section. This also needs to be available as an option when a WordPress site is set up within Plesk.

Add support for PostGIS out of the box

Implement the Contained Databases MS SQL feature in order to limit the database users ability to see MS SQL database names which are not owned by him.

For external databases, I can connect to my server, but when I need to add a new user my SaaS database provider from Azure requires the username have an @%. Because of that the connection string in Plesk never works and fails every deployment of any CMS.

It's not always feasible to add the mssql.<domain.tld> DNS entry for the websites hosted in Plesk.

Adding an option to configure a custom url/dns name to access the MyLittleAdmin tool with would be preferrable.

And make sure that "MyLittleAdmin" button under Databases would take the user to the global url if it's set.

I would like to see support for the upcoming MySQL 8.
Currently there is no support inside plesk and using a possible workaround with docker isn't possible out of the box.

MySQL Community Server 8.0.4 is already a Release Candidate.

Add the ability to create ODBC DNS for ODBC Driver 17 for SQL Server in Plesk.
Disabling TLS 1.0 breaks compatibility with earlier versions.

According to a ticket I just opened (80693) Plesk currently doesn't support a clustered MySQL server, e.g. an active/active Galera cluster.
To avoid data-loss or corruption in a server crash, I'd like to run MySQL in a Galera cluster to automatically sync the data again once Plesk's MySQL started after a crash.

Hello,

Please add functionality to disable PHPMyAdmin access to users.
PHPMyAdmin is vulnerable for bruteforce attacks.

When mysql database size reaches it's quota e.g. 1GB insert,update permissions are removed for that databases users. permissions are restored when database is within quota.

in short it should stop the ability of the database growing in size but not stop basic functions like reading existing data...

this would be fine to run on the quota check cron or somethng.