Percona Server for MySQL vs. Valentina

Percona Server for MySQL covers 100% of our requirements in terms of our OLTP traffic and provides the High Availability levels required through a typical primary and 2 replica's using semi-synchronous replication. We're able to scale our writes using sharding, but a true distributed database would be a great option on top of this. In terms of OLAP traffic, we leverage columns stores available, but Percona Server fairs well

If you have to manage a lot of different databases from different vendors, you could do well by standardizing on this product. It checks all the boxes for a proper database management studio. You would only have to learn one product to manage them all. However, if you are looking to find a good product for a single database vendor, you might be better off finding a tool that was designed specifically for that vendor product.

Incentivized

• Faster than other server solutions
• Installation and configuration process is easy from the user's standpoint
• Easy to learn and good support

Incentivized

• Foreign Key Constraint data viewer! This was a tremendously helpful feature that not many other products have. Just pick a constraint and see the data in the child tables! No setup required!
• Supports any and every database imaginable.

Incentivized

• Better documentation
• A better UI

• Somewhat laggy performance. Boot up speed was on the slow side and connecting to our database servers was also a little slower than other products.
• User interface can be a little clunky. Instead of the usual tree view of servers, databases, and schemas, you are presented with lists that you click on and get new windows to pick the new list of data from. Not organized efficiently.

Incentivized

It is easy to install and use. Using it along with Percona Monitoring and Management makes it even easier to use.

Incentivized

We are using opensource so we have not used customer support.

Performance and stability sets Percona Server for MySQL apart from the rest. Percona embraces the upstream version and contributes towards the upstream version making MySQL stronger on two fronts and thus having a much larger community. Many quality contributions have been made by Percona into the base code. Percona provides great tools to support Percona Server for MySQL and this makes the monitoring and management easier

Compared to Microsoft's SQL Management Studio, Valentina studio was comparable, just harder to get used to in the UI department. It ran slightly slower than other products but did save some time with neat features they baked into the product. However, in using DBeaver Community and DBForge Studio for PostgreSQL from Devart, we found different products that the team ultimately decided to use. DBeaver has all of the features we needed most (minus the constraint data viewer) and a more intuitive UI that we were used to. DBForge Studio for PostgreSQL has a very standard Windows look and feel and lacks some features, like database/table designers, but makes up for those shortcomings in the much easier filtering and sorting options right in the data grids. You can even write a query and edit the data returned, which is something we don't see in many of these tools. Our team ultimately settled on the developers using DBeaver and the support team that needs data viewing/editing capabilities using DBForge Studio.

Incentivized

• At the performance level, it maintains and even improves other open-source databases such as MariaDB or some commercial ones such as Oracle.
• If we compare it with MySQL, we could have up to 50% improvement in performance.
• For some small companies or startups, the price of the complete solution and the support can be a bit high.

Incentivized

• It saved time in some areas of finding child data by not having to write queries to find it.
• The user interface caused some extra training for some users and ultimately caused them to not like using it.

Incentivized