Resolved Remote MySQL database as default doesn't seem to work

[burnley]

OS ‪CentOS Linux 7.2.1511 (Core)‬
Plesk version 12.5.30 Update #53, last updated at Nov 15, 2016 08:38 AM

I've replicated the problem on 3 Plesk 12.5.30 Update #53 servers. After adding a remote database and checking "Use this server as default for MySQL" option, I go back to the "Database Servers" page and the new, remote database displays (default for MySQL) next to its host name. But when I log in as client and start installing applications (tested so far Wordpress, Joomla & Drupal) the databases are all deployed on the localhost instance.
Is this standard behaviour? Do we need to fiddle with the existing service plans / clients / subscriptions retrospectively to get Plesk to use the new, *default* MySQL server? What else needs to be done to get Plesk to use the default MySQL instance, instead of localhost?

 

[IgorG]

I suppose that you need to set up this default (remote) database server in Service Plan 'Hosting Parameters' settings.

 

[burnley]

Thanks Igor, figured out that might be the case. After modifying the service plan the customer can use the remote database instance as default. But there's something I don't quite understand in the logic. Why would you have the ability to set a default database server globally, from Tools & Settings -> Database servers, if the service setting plan takes precedence? If I have multiple Plesk servers and several dozens service plans & addons, do I have to go and modify each and every one? When is the default instance set in Tools & Settings -> Database servers in fact used?

 

[IgorG]

Let me clarify this behaviour.
When user installs application, default db server is chosen by following rules:

• If subscription is synced with Service Plan, Service Plan "Default DB Server" settings is used;

• If subscription is locked or customized, subscription "Default DB Server" settings is used;

• If Service Plan or subscription settings isn't set, server-wide setting is used.

 

[burnley]

Thanks Igor for clarifying this. Since manually modifying each and every plan & add-on on each Plesk server isn't an option for us to transition from local to remote MySQL database, I'll look into what options we've got to automate the process and will report back.

 

[UFHH01]

... modifying each and every plan & add-on on each Plesk server isn't an option for us ...

I'm pretty sure, that you can set the remote database as default for each reseller, subscription, hosting - plan and domain, with a single one-line - combination - command of "plesk db "SELECT * ..." ( just like the one, that is shown in your signature. ) and additional PLESK - CLI - commands. If you smile to @IgorG , he might even provide an example for you.

 

[burnley]

I'm pretty sure, that you can set the remote database as default for each reseller, subscription, hosting - plan and domain, with a single one-line - combination - command of "plesk db "SELECT * ..." ( just like the one, that is shown in your signature. ) and additional PLESK - CLI - commands. If you smile to @IgorG , he might even provide an example for you.

That's cheeky
Of course we can do some more psa db surgery to get this fixed, we're pretty good at stitching together sql queries to get the job done. As we use to say in my country of birth, "there's nothing in this whole world you can't fix using a little bit of metal wire" But I'm interested in a more "professional" solution.

 

[IgorG]

Hint:
You can find id of remote database server in DatabaseServers table. Then update this id as value for element 'default_server_mysql' for corresponding id of Service Plan in TmplData table.

 

[burnley]

Thanks Igor