• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Mysql User Limitations

Q

queueless

Guest
Greetings.

I am currently scripting a migration program to transfer domains to a Plesk 8 Linux system. My problem is that the Plesk MySQL interface is lacking functionality in that it will not allow a common database user among multiple databases. For example:

Originating server:

I have 3 databases

db1
db2
db3

I have 1 user that accesses these databases

dbuser

On the Plesk side, I have no option of, say, choosing an already existing user when adding a user to a database. I must have 3 distinct users for each database, which is less than optimal.

Now, I'm fully capable of duplicating the configuration on the backend (i.e. mysql db table); however, these users won't neccessarily be listed as users for secondary databases in the Plesk GUI.

I am wondering if anyone has any thoughts or encountered this problem, or how I might go about solving it.

Additionally, I'm (going to be) using the /usr/local/psa/bin/database to create the databases and users on a mass scale.

Thanks.
 
Well it seems this is a common problem with no solution.
 
Back
Top