Oracle Database In-Memory Reviews

We stream and exchange data with multiple partners and vendors using the product.

Oracle Database In-Memory has a valuable transaction feature. It efficiently handles low-code data and supports read-and-write operations for clustering.

The product could be more economical. It is much on the higher side than other databases. Additionally, they should include OLTP functionality.

We have been using Oracle Database In-Memory for ten years.

It is a stable platform. I rate its stability a ten out of ten.

There were 5000 Oracle Database In-Memory users in my previous company. I rate the product's scalability a ten out of ten.

The technical support services are good.

Positive

The initial setup is easier for the cloud version. I rate the process a ten out of ten.

The product is expensive. However, it provides quality features. There is room for improvement, considering other options. I rate the pricing a ten out of ten.

We evaluated different providers. We went to Oracle Database In-Memory for better transaction size and volume.

I rate Oracle Database In-Memory a ten out of ten.

We use the solution for improving database reporting that previously took long hours.

The solution's most valuable feature is its ability to manage database memory using various methods.

They should improve the solution's scalability for large databases. Also, they should frequently update the on-premises version.

We have been using the solution for two years.

The solution is highly stable. I rate its stability as a nine.

It is a scalable solution. We have 2,000 customers and 35,000 end users of the solution. Also, we plan to increase the number of users.

The solution's technical support team is responsive. But it could respond faster to complex issues.

The solution's initial setup process is fast and easy. It takes less than an hour to complete. However, implementing and testing it in a different environment takes more time.

The solution requires four executives for deployment and maintenance. We test the solution's new version in a lower environment for deployment. Later, we release it in our production environment.

The solution's ROI is excellent.

I recommend the solution to others and rate it as a nine.

We work as consultants, so we provide the solution to customers. It's deployed on-premises.

We write the queries using SQL Developer, and we do the synchronization.

We're using Oracle 10g and 11g.

The query optimization and backup features should be added.

I've been using this solution for more than eight years.

The on-premise version is stable. We have different teams and resources for the server side, for admin, and for development. We can easily take care of all the services and applications.

We do maintenance frequently. Every weekend, the admin team has to do some patches and some upgrade activity on the servers. So, maintenance is needed to stay up-to-date.

Since we aren't using this as a SaaS, if we move to cloud, we can go for scalability easily. The on-premise solution is scalable. It's also good for cost reduction. If the client is looking for some cost reduction, it is not possible with the on-premise version, so it's better to go for SaaS or cloud.

There are no costs in addition to the standard licensing fees.

I would rate this solution 8 out of 10.

For someone with small architecture and a small volume of data, they can go for the cloud services. If they have a huge volume or some security perspective like BFSI data and a banking system, they should definitely go for the on-premise solution.

If we go for any BFSI or some banking or card solution, we can easily see that most of the companies are working with the on-premise solution only. They aren't considering the cloud solution to be secure. In terms of security, they are going for the on-premise version because everything is in their hands only.

We use the tool for real-time data transfer for risk management purposes. In a trading system, conversions happen fast. We use the product to handle fast transactions with low latency. 

I would like Oracle Database In-Memory to include a data replication feature. 

I have been working with the solution since 2005. 

Oracle Database In-Memory is very stable. 

I would rate the product's scalability a nine out of ten. 

Oracle Database In-Memory's setup takes six months to complete. You need 10-15 resources to handle the deployment of the whole system. 

Oracle Database In-Memory is expensive. 

I would rate the solution a ten out of ten. If you do not have high-frequency transactions, then Oracle Database In-Memory is not for you. You would require Oracle Database In-Memory for mission critical high-frequency transactions. 

I mainly use this solution for business analytics and intelligence.

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. Another valuable feature is that we can zero data loss with this solution because there is no data loss when there is a loss of power or the RAM crashes, as with traditional databases.

In the next release, Oracle should include column store or advanced query optimization so a database can be optimized by enabling analytic queries to run faster.

I've been using Database In-Memory for two to three years.

Database In-Memory is reliable, performs very well, and requires very little maintenance.

This solution is easy to scale.

Oracle's technical support is very good.

Positive

The initial setup was simple.

We used an in-house team along with some documentation and help from Oracle's website.

Database In-Memory is priced a bit higher than its competitors like Microsoft. The Enterprise edition has no additional costs, the in-memory features come included.

I would rate Database In-Memory nine out of ten.

We primarily use the solution as an email database.

Overall, it's a very good solution.

The application development is very user-friendly. 

The SQL is great in Oracle. If you use other databases, you often have to find another syntax and develop in other languages.

The user interface is great.

The pricing could be improved. It would ideal if it was more reasonable.

The design isn't that great. It's kind-of buggy and doesn't seem to cater to the Korean market.

There seems to be issues relating to migration. It's difficult to migrate off of it if you need to.

I've probably been using the solution for about a decade. It's been about ten years now.

The stability has caused us some issues. We've dealt with bugs in the past. It's not flawless.

The scalability is pretty decent. We've had clients that have scaled in the past, however, they didn't use Oracle to do so. That said, I believe it scales.

We don't have contract-level technical support. In the past, we've used MOS support at oracle.com. It was just for a service request. They utilize more of an open-source system and it relies on open-source technical knowledge. It would be more helpful if Oracle could directly answer our queries. However, that's just not the case.

We've found another similar solution called Ignite that we are looking at implementing.

The initial setup is pretty straightforward. It's nearly always a cloud environment, which makes things fairly easy. Everything is already set up for the most part. Companies that want to utilize In-Memory just need to work with the existing cloud infrastructure.

The product is quite expensive. Organizations should be prepared for a rather high price tag. Our clients may end up moving to an open-source option to lower costs.

We're Oracle partners. We've been partners with Oracle for a long time.

Our IT department first changed from on-premises to cloud. Our clients seem to like a hybrid deployment model. Now they are considering looking for other solutions that may not be as expensive or may even be open-source.

I'm not really a database expert. My understanding is that some customers want to make a product from the portal website using the In-Memory DB. Others tend to want to migrate from an Oracle In-Memory database to another email database. It's difficult when users want to migrate off of Oracle or simply to another Oracle solution. They tend to run into a lot of issues. Personally, this solution wouldn't be my top choice, as it makes things difficult.

There are a lot of alternative email database solutions. I'd just advise other companies to take a look at the options to see which would work best for their use case.

That said, while we migrated to another solution, it's still a pretty good tool, and issues just seem to arise if you are migrating. 

Overall, I'd rate the solution seven out of ten. If the pricing was more reasonable, and the migration was easier, I'd rate it higher. 

My solution has a big database with terabytes of data and we use Database In-Memory for a lot of our data. Normally, we partition it and create big tables, but we can use In-Memory for data that we use every day or every hour. We put some partitions in In-Memory from some tables and we use that. It normally has good performance.

Normally, every database server uses hard disks. In-Memory has a feature, apart from its 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 tablespace from that spot to share. It's a really good feature. We use it a lot.

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 the last partitions on the table. We always need to create a script and make a schedule that can load the last partition 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.

I have been using this version for about four months.

We have used this feature for four months and it's stable. I used to load one terabyte of data in my memory servers each time. I think it worked okay. I don't have any problem for now.

I live in Iran. Iran is sanctioned by the US government so Oracle can't provide any services to us. I study on my own. I use Oracle documentation and watch YouTube videos. I don't have any company to support us.

It is very easy to deploy. I always work in Linux, Oracle Linux. If you want to work from the GNOME GUI, it's really simple. You must state a parameter in Linux and then use their installer. Click next, next, next, then finish. It's simple. In Oracle 80 and 90, we have an installation system in a common UI. It's very simple. You must have the prerequisites and after that, install RPM in just one comment. Check your configuration and set up the database. It's simple.

Deployment in the GUI version, if you want to use that, is I think 14 to 20 minutes. In the command line, it would take 10 to 15 minutes. I can't remember exactly, but something close to that.

Oracle is the best database, but I love open-source software. Oracle always has the first original features for three or four years and we use them because they are stable and we can buy in a large scale and use it for our office. It has no problems. I think Oracle is ten out of ten.

About Oracle Database In-Memory, in particular, I would rate it as eight out of ten. It's a new feature. I think it's improved from the last version three years ago.

Oracle's new features and data are very useful for us for storing data, loading it, etc. Oracle features based on processes are good. In Oracle, we just have four functions based on data types, but in post-production, we have more than ten functions. That is very useful for us. We'll add more functions and features like index and categorization based on data type, output, and large data. That would be very useful.

We use Oracle Database In-Memory for reporting and analytics.

The platform's most valuable features are query response time, columnar storage, and data cube setup.

The platform’s pricing needs improvement.

The platform is stable. I rate the stability a nine out of ten.

We have more than 50 Oracle Database In-Memory users in our organization. While occasional usage may increase, the technical infrastructure effectively manages these fluctuations. It demonstrates negligible impact on performance, even with incremental user growth. I rate the scalability a nine out of ten.

We have received technical support for reported bugs, and the team promptly releases patches.

Earlier, we utilized the Oracle Database Appliance for data warehousing purposes. Additionally, we relied on SQL databases, particularly older versions managed by Oracle as well as the old SAP DB. However, we transitioned to Oracle Database In-Memory to address the specific needs of our environment, particularly in scenarios where we needed to report data across distributed sites efficiently.

The initial setup process is simple.

The platform provides the best performance in terms of database analytics. It efficiently serves as a data lake. We can integrate it with any data sources as well.

I recommend it to others and rate it a ten out of ten.