We performed a comparison between MySQL and Oracle Database In-Memory based on real PeerSpot user reviews.
Find out in this report how the two Relational Databases Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."MySQL is a popular database platform for businesses because it is extremely easy to use."
"It has a lot of features. The RDBMS, consistency, and multi-user features are valuable."
"The most valuable feature of MySQL is the informative error outputs of command line interface."
"A good traditional database that supports JSON."
"I like the JSON stuff."
"It is easy to use."
"The most valuable feature of MySQL is its reliability and performance."
"It is a very stable solution. I deployed the product six years ago, and it still works fine."
"I like Oracle because it is a backward-compatible solution."
"The solution's ROI is excellent."
"The most valuable feature is that Database-In-Memory is more consistent and faster than traditional databases as it requires fewer CPUs to process instructions."
"The product offers high scalability."
"It accelerates query processing, which in turn speeds up operations and streamlines workflow, and ultimately enhancing productivity."
"Normally, every database server uses hard disks. In-Memory has a feature, apart from their database, which is very good. When we start our server, all your data needs loading memory. We can use that. It's a very good feature. I think they added this feature in 2019. We can mount memory in the partition, create partitions in there, and create table space from that spot to share. It's a really good feature. We use it a lot."
"It efficiently handles low-code data and supports read-and-write operations for clustering."
"The scalability of the solution is very good. It's able to support large amounts of data."
"We require more ease of use, scalability, and high availability. These are some of the critical features that we use and look for in a product. It should be easier to manage clusters. Scalability is very important for us because our projects and concurrency requirements are quite big. We also require high availability of the server, application, and other things. It should also have more performance-based features or enhancements from the performance point of view. When we divide a database, it should be able to handle the queries very fast."
"I am looking for the Temporal SQL feature, which basically means that there is complete history for each table. This feature is currently available in MariaDB. PostgreSQL has something called a foreign-data wrapper, which is another way to access external data from inside. MySQL could have a similar feature."
"Improvements to MySQL depend on the specific use case. For example, in my scenario, I frequently need to maintain and store data, which can then be utilized to generate reports. On the other hand, others may suggest incorporating a feature that allows for easier visualization of the data, such as what is available in Power BI or other similar tools."
"The licensing cost of the solution is expensive, which MySQL needs to consider improving."
"In an upcoming release, there should be something added similar to EPL. For example, when using the flow diagram, we can create a schema. We have two useful features to add or create the table, but there should be some UI features to allow us to drag and drop to create other schemas. This would be very helpful."
"The analytics features are in need of improvement."
"The GUI could improve in MySQL."
"Sometimes, I get lost in the toggles and buttons, and a better visual design would be nice. The layout is not user-friendly or efficient."
"I would like Oracle Database In-Memory to include a data replication feature."
"They should improve the solution's scalability for large databases."
"The query optimization and backup features should be added."
"The product could be more economical."
"The solution is quite expensive."
"We use some partitions in In-Memory. We have a very large table and a low dose. It is very expensive in data to load all of them into In-Memory. It takes up more memory slots in the server, as well as a lot of RAM. We use last partitions on the table. We always need to create a script and make a schedule that can load a last partition in In-Memory. Oracle doesn't have features to do this automatically. I would like them to allow us to load last partitions, as well as other table partitions, in In-Memory. I think a good feature would do that automatically, letting you see a table, load a large partition, and monitor loading memory. It's quite a good feature."
"The pricing could be improved. It would ideal if it was more reasonable."
"The high cost of the product is an area of concern where improvements are required."
MySQL is ranked 4th in Relational Databases Tools with 142 reviews while Oracle Database In-Memory is ranked 8th in Relational Databases Tools with 27 reviews. MySQL is rated 8.2, while Oracle Database In-Memory is rated 8.8. The top reviewer of MySQL writes "Good beginner base but it should have better support for backups". On the other hand, the top reviewer of Oracle Database In-Memory writes "User friendly with great scalability but needs to move toward intelligent AI". MySQL is most compared with Firebird SQL, PostgreSQL, MariaDB, Teradata and SQL Server, whereas Oracle Database In-Memory is most compared with SAP HANA, Progress OpenEdge RDBMS, IBM Db2 Database, SQL Server and Exasol. See our MySQL vs. Oracle Database In-Memory report.
See our list of best Relational Databases Tools vendors.
We monitor all Relational Databases Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
