Before choosing the solution, evaluate the on-premises, public, and private cloud environments. Speak with a representative about what environment best meets your needs.

In the public cloud arena, Azure and AWS also offer good products that compete with the solution.

I rate the solution a seven because there are better public cloud options. 

I would recommend this solution to larger companies that have specific requirements and can benefit from it. It's a highly effective product.

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

Overall, I rate the solution a nine out of ten.

The solution improves the data analytics processes as it helps to meet the requirements of a database. To meet the recommendation of the company to have an Oracle-based product, we use Oracle Database In-Memory. The resources in our organization are mostly Oracle-based products. For bigger environments, I prefer Oracle because it allows me to have access to trained resources in the market. Due to the aforementioned aspects, Oracle works for me.

The tool supports our organization's OLAP and OLTP workloads. My organization is a bank with 900 branches, and all of them are connected simultaneously. Considering the aforementioned scenario, most of the user activities were through the database. Large user bases are supported by Oracle and are much better than DB2.

The columnar data storage format of the product is not used in our company's system. The inbuilt capability of the product was used in our company with regards to the storage part, but for the software part, my company does not use columnar data storage format.

In most cases, a database is required by the application. It is not me who personally but the applications that require a database. In general, database requirements come from the application, and for such scenarios, I recommend others to go with Oracle as other databases may not be good enough, especially if the applications require only databases from Oracle. If the applications require DB2, then users should opt for DB2. My recommendation cannot be considered as a valid one, especially if we consider the requirements that may vary for applications. If there is a need to support terabytes of data, the database from Oracle is useful. The performance capability of Oracle is much better than DB2.

The In-Memory Advisor is helpful, especially after the installation processes are done and the operation part is running. If any performance issues arise, the In-Memory Advisor helps users to find out the information as to what is the root cause of the problem and to explain what should be done.

Whenever there is only a single node, my company faces a lot of password issues since there are many users. The company has to scale up to two nodes. The load balancing aspect is managed with the help of two nodes, so it is easily scalable. Though the steps are a bit complex, the product is very much scalable. The performance had increased by almost 200 percent when my company had added the second node.

I rate the overall tool a nine out of ten.

After accessing the In-Memory database, we usually have some downtime. That's acceptable to me, but if they can eliminate that, it would be good. The downtime is needed now to change the allocated memory in Oracle. If you use a data block, the downtime lasts minutes.

Oracle provides Exadata for customers, and that's very good because usually another cloud is not provided to them.

I rate the solution a ten out of ten.

When I compare solutions like In-Memory to FOSS 3.0, FOSS 3.0 has more features. But if you add all those features to one person, they are incompatible. Compatibility is an important thing, but many people just skip it.

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.

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

It is always worth testing or running a proof of concept to check its value.

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. 

You need to understand the data. You do not want to use In-Memory for all of the data. You need to understand the data, understand the inquiries, understand which data you actually want to put in the In-Memory. You should not put all the data in there.

We do not INMEMORY ADVISOR in oracle, however this is obvious

Which data has to go into In-Memory is something that you only know from experience; how to get the most benefit out of In-Memory. Get access to the Oracle Learning Library School. There are some good videos there for the In-Memory. They're really awesome.

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

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.

I would have to say the In-Memory column store is definitely a 9.5. It's really great right now in 12.1.0.2 and it's going to get gooder in the next release. Multitenant, to be honest, is a little adolescent at this point. There are some things I wish it could do right out of the box but what I'm seeing coming in the next release will probably get it up into the 8.0 or 8.5 range. In terms of security, I'd have to say some of the features we discussed are actually quite good right now. I'd put them towards a 9.0. Oracle Public Cloud needs some more work. As an Ace Director for Oracle, I'm working very closely with the team and my company, OnX Enterprise Solutions, as well, is working very closely with Oracle to make Oracle Public Cloud better, stronger and more easily deployable. For all of these, I'd have to say probably 8.5 to 9 on a scale of 1 to 10.

My recommendation is if you're going to go to 12.1, immediately take a look at the In-Memory column store. It's the biggest bang for your buck. I'm not going to discuss the L word, licensing here, while we're here. It is definitely not a free feature but, in my opinion, if it's implemented properly, it might save the cost of an extra DBA. A good DBA, I'm from Chicago, might cost somewhere between $110,000 to $130,000 a year in salary, not counting benefits. You could save that amount, if you will, OpEx with some CapEx. That's a compelling story. The ability to take a query that you might have dedicated a full DBA to, to make it run faster, and simply by throwing a switch make it run faster, that's a compelling case to me, as a DBA but also as someone who deals with C-level executives and DBA managers all the time.

We use the on-premises deployment model.

I'd advise others to look at the solution, but to be mindful as it is costly. Whether it is right for a company or not depends on the requirements. If they have the budget, they should go for Oracle. If they do not, I'd suggest they look at something open-source like MySQL or Oracle SQL.

I'd rate the solution nine out of ten.

Try it out first. See if it meets your expectations and go from there.

I suggest looking mostly at the interfaces; that is the key. Even if the performance is good, but the interfaces are not right, to the application or to the front end, that could be an issue.

We’re really happy with Oracle Database In-Memory.

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.

Implementing Oracle In-Memory is very easy, but the tuning phase is mandatory to optimize it.

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. 

We are going to be an Oracle shop for a long, long time.

When looking for a vendor, I look for expertise, how quickly they can roll out the product, and the cost of implementation.

The solution provides a good environment and it's a product we trust.

I rate this solution eight out of 10. 

We use the on-premises deployment model in the virtualization environment.

I'd rate the solution eight out of ten. If technical support was better and usability was improved, I'd rate it higher. It's the best solution on the market right now, but it's more for big data. For us, it's the best solution we can get for our specific needs.

My advice it to realize that the cost of the product itself is not the only consideration. Cost for support of the product after purchase must be considered. A decision sometimes seems quite easy to make, but you need to consider many, many aspects. Not to just say, "This is a good one." Good products cost more. They may need more maintenance and more resources for them to work properly.

I would recommend In-Memory because it is a robust and scalable RDBMS. We are able to achieve high availability.

I would rate it a nine out of ten. 

They should improve the licensing cost.

I recommend using this solution, just as we are using it.