It's extremely stable, and I'm optimistic that it will remain open and adaptable in the future. I would rate it nine out of ten.

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

The product is stable. I rate the solution's stability a nine out of ten.

Stability-wise, I rate the solution a nine out of ten.

I rate Database In-Memory's stability an eight out of ten.

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.

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

Very stable.

Oracle Database In-Memory is very stable. 

In-Memory stability is really very good.

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

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

The stability of the solutions are one of the more impressive things. Having come from Oracle 8i as my first Oracle DBA job, when a new release would come out, there were always tremendous numbers of bugs. That's not the case with these 12.1 releases. They're extremely well-tested. I'm not going to say there aren't any bugs but they're fewer and farther between than they were in earlier releases. There's a significant advantage to getting on the 12.1 juggernaut, if you will, because these releases have been very well shaken out.

The solution is stable.

It is pretty stable.

Stability has been pretty OK. There have been some issues. Support was able to help us out with some configuration.

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.

The product is stable. Of course, at this level of software, there are always some bugs. But, each time I have had to implement it, the bugs weren’t very problematic and I've always found a patch or a workaround.

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

This is a very stable solution. You always have kinks with any solution, but they have awesome support, depending upon how much money you pay them. You need to have platinum service to get good support. Otherwise, you'll have to struggle a bit.

The solution is stable. 

The database is very stable.

We have not had any problems with stability.

It requires a lot of resources, man power, and DB power, to make it stable.

Stability is very good.

The numbers show that it's very stable and very promising for high-transaction, low-latency systems.