Multiple databases per application
. but i does not apply here.. so sad :((
Ranil Jaramillo
shared this idea
26 comments
-
Anonymous
commented
One of the dumbest things I've ever seen for a webhost. And people have been complaining for 7 years straight, and still no fix in sight
-
Jeff S.
commented
This is also a deal-breaker for me. Creating a new application for just a DB is absurd in 2020.
-
Justin Mayfield
commented
Yes, please address this more adequately. Even shared Bluehost plans have built-in phpmyadmin with full management ability for every DB on the account and ability to create new DB's.
Creating a whole new application for a mere DB is a pretty low-quality solution. It makes a slow workflow and it clutters the application list. Without more ability to tag and search applications, this is a fairly low-quality user experience.
The only thing I can think of is creating a DO or Vultr droplet/server directly on their service (so it's cheap) and setting up phpmyadmin there with root access. I may have to do that for adding extra DB's but that doesn't help me to have a central place to manage all of my DB's.
Also, setting up SQL Workbench is a fairly complicated solution for DB management--especially given how generally user-friendly the rest of Cloudways' service is.
-
Anonymous
commented
I was nearly ready to start migrating my sites to Cloudways from Webfaction but I think this shortcoming might be a dealbreaker.
-
Anonymous
commented
Almost seems possible, the function is there, but 'access denied'.
-
Anonymous
commented
This is really sad
-
Scott Whitlow
commented
This is causing us major issues and the workaround provided is *not* sufficient. We need to have a solution that easily allows you to create a new DB in the same instance. It is crazy that you have to create an entire new application just to add a new DB.
-
Tom Greenwell
commented
This would be particularly useful for a staging version of a website at a subdomain. The tool I use to sync site versions (Wordmove) currently does not allow for differing table prefixes.
-
Anonymous
commented
This is absurd. It is 2017 - what a joke.
-
Qarib
commented
So basically for every new database I have to create another application
which is not ideal in real world scenerio
as I will have to maintain so many apps
please let me know if you have plans to improve this
as this is really a huge drawback -
Dovydas
commented
It would be awesome to have it!
-
Cran
commented
Yes getting the denied access and no privileges sucks. Please implement this feature.
-
Stan
commented
Yeah, lets get this sorted please.
-
Mat
commented
According to Support they team are working hard to implement a solution to this .. since this was raised as an issue in 2014 first and it is now 2017 I'm not holding my breath.
Very disappointing.
-
Mike
commented
Can the Cloudways team provide an explanation for this limitation? (apart from the perhaps obvious reason to want users to create multiple instances just for the database and therefore increase costs)
-
Stephen Barker commented
I have sites I'd love to bring to Cloudways but I guess I need to keep giving my money to another host.
-
The proposed workaround from Cloudways does not allow a single user to access both databases (the main app db and the empty stack db). It's 2017. Seriously. Your tool has a "Create new database" option but you deny access. Why? Nobody has yet answered that question. It can access the "Information Schema" database as well as the app database. Why not a third or more? There's no way here to share tables or cross reference due to the user partitioning.
Please, let's get this moving. This functionality has been possible with PHPMyAdmin for years and years. CloudWays can do better here.
-
George Tourtsinakis
commented
I'm confused with your guide for second DB.
-
The proposed solution doesn't work for a single application that only has a single set of credentials but needs to connect with multiple databases or share tables.
-
Rob
commented
Agree with all the comments so far. This is ridiculous. Honestly, I am considering cancelling my hosting plan with Cloudways because of "permissions" being capped. I had to do so much workaround (especially setting up DNS records) to bypass this limitations that it's not funny. It's easier for me to move all of my sites to a new host than to bypass limitations on Cloudways. Unacceptable.