Oracle Database Reviews

Oracle Database helps you store and root through data as fast as possible, which is really valuable to our organization. In addition, while I can do everything I would like to with the product, if there is something that is not possible in the current version, you can build your own features.

The expansiveness of the Oracle Database has been beneficial. You can find more than you could ever think of in the product, which increases business efficiencies by returning information to you quickly and allowing you to do work in the database that you would otherwise have to do in a different application.

The product could have more persistent data types, like Boolean and the simple features in MySQL and most databases.

It is so stable that I have this mantra: “If you have not crushed the server you have not been trying hard enough.” I have not crushed it in a long while. It is really stable.

It scales very well.

It is pretty good. They always ask the same questions about log files, so since we already know what they are going to be asking, it’s pretty fast. Most of the time they come up with solutions really quickly.

Do as much as you can in the database. It is the fastest product you can have, when working with data. The product is an eight out of ten.

The most valuable feature is the high concurrency in terms of transactions. The second most valuable feature is that from a diagnostic performance standpoint, I can tell exactly what is going on. It is really good at helping to solve problems.

The organizational improvements go back to the high concurrency. There are a lot of database products out there, but it is difficult to have a lot of simultaneous actions from a business perspective in the database. They have to happen very fast, and Oracle just shines at that.

I would like Oracle to instrument the CPU consumption of Oracle sessions. Right now I can tell how much CPU Oracle consumes, but I have no idea what it's doing when it's consuming the CPU. I can infer that, but I don't have the authority that I would like to when I speak about it.

We have been using the product since 1989.

It’s a software product, so there are some bugs. When I have issues, they tend to be from an unusual or intense workload that is stressing the system.

It rocks. You can tweak Oracle so it will use up all available computing resources. That's powerful. That way, you can use your investment and your capacity.

You always have to be careful about stability when applying patches. A patch could fix one thing but hurt something else, so you really have to be conscientious and do your homework first.

You need to get a good overall understanding before you drill down. There is too much to learn, so get a basic fundamental understanding and then let the problems guide you in learning more.

Usability is the biggest value of Oracle Database.

Compared to the previous version, this version has really improved in terms of the speed.

We want Oracle to specify the differences between the two versions, the former version and the newer version and how it is linked. 

Not only with one version differences but older versions as well since there are people who are using much older versions. If they are able to clarify what the difference is between the latest one and those older versions, and if they are able to offer us the easier method for the migration, then we would appreciate it.

Even if we encounter any problems, then there's a strong definition of how we are able to improve the situation and resolve the situation. We are able to do the backup beforehand by referring to those defined resolutions from the Oracle, and if we are able to have the two systems, then even if one fails, we are able to use the other one, so we are able to prevent problems.

In comparison to other more simple structure databases, I consider the Oracle Database to be more scalable, as well as easiness to export from an external system.

For people who are thinking about introducing Oracle Databases - they need to have knowledge beforehand about how to operate the databases in terms of security, and how to respond to the failures.

There are many use cases for the Oracle Database and if I encounter any problems, there's information available which I can reference.

We are the ones who are developing the system and delivering it to our customers, so it does indirectly benefit our organization from this perspective. The fact that we are able to leverage the available information that I mentioned earlier, means we are able to make sure that development is successful.

The response speed of the support as well as lowering the price.

In comparison with other commercial databases, it's more stable but there are many challenges that we feel should be corrected.

For us, there are not so many cases that require scalability.

I think it takes longer because we're in Japan and if we have a problem then we need to pass the information to the US and it takes them time to respond.

Relatively speaking it's easy.

Oracle is the number one product I recommend as long as the customer has sufficient budget.

I'm not using a lot of different Oracle Database functions, but for us, the fact that they have a documentation in Japanese is quite important. It's quite easy for us to find what we want to do. We wish that the community in the Japanese language would become more activate in the future.

The benefit that we get from using the Oracle Database is the sense of security or the stability.

Others would be better fit to answer this, but I hope that the product will improve in terms of usability (user-friendliness).

After the release we need to do a performance tuning, so we need to figure out what we can do for the visualization for the performance tuning. We wish that Oracle could offer this as a product so that we are able to easily start using it. 

No, but I was involved partially when we developed the environment of the Oracle Database. At that time I had the impression that it was not so difficult, it was rather smooth.

We compared it to other competitors. In the end, the end-user is the one to select which product they want to use. What we can offer is that in terms of the security or in terms of the share, how many companies are using it, which big names are using the Oracle product?

In the past when we wanted to merge data, we needed to consider the series of the data, but with Oracle Database there is no need to index the data. That's the important feature.

It's been only two years since we introduced the database, so we are unable to identify a clear benefit yet.

Compared to its reputation, it's worse than expected. The system went down two times. It said that when there's a shutdown it's only for one system, and not both systems at the same time, but it actually did occurred.

Maybe it is specific to the way we use the databases, but we introduced Database to different operations in the organization. We didn't actually introduce Database to be shared among all the different departments.

We had improved the version of the operating system. We did a patching of the Database. They helped resolve the problem because we didn't experience similar issues again. We can say that they helped us.

We used to only use IBM Databases, and it really restricted our options. We wanted to broaden our options by introducing another Oracle system.

We contracted with Oracle without the maintenance agreement. We had actually built the organization that way since it was easier for us to develop. We really did not try to fit with the system. We tried to fit with the operations, so it was rather difficult for us to manage. We ended up having less memory.

We really didn't consider any other options because we need to have a major name as a provider. We need to exchange the maintenance agreement through the third party vendors. If it's a small name vendor, and we have difficulty receiving the maintenance support, then we need to provide maintenance on our own. We would like to prevent that situation from happening.

The main features that I take into account when I talk about databases of any kind are high availability, reliability and manageability. Oracle RDBMS has all that.

The high availability and reliability with Oracle RAC, Oracle Dataguard and Oracle Flashback, the manageability with several views and packages like Advanced Workload Repository(AWR), Active Session History(ASR), SQL Tuning Advisor, SQL Plan Control, and many others to monitoring and troubleshooting issues and bottlenecks, are valuable features.

With Oracle RAC, we can reach near to the dreamed 99.999% of availability in a year. Oracle Enterprise manager allows us to see the "big picture" and take proactive actions to maintaining the environment.

Oracle RDBMS has great features, but I believe that Oracle could be more flexible with the offering of some extra options, and include them in the main license. Today, a High Availability or MAA environment with an Oracle database is already expensive, plus with those extra options, it could increase the cost much more.

Oracle RDBMS has a lot of features and is extremely stable, but all this come with a price, and in this case a big one. So, I would advise you to use Oracle RDBMS mainly for medium and large enterprises. For small enterprises, I advise using other RDBMs, like SQLServer or PostgreSQL.

The most valuable feature of Database is the reliability that we get from it. We really depend on it being up and available because we're a manufacturing company. It's got four 9's of uptime, and that's incredibly important.

It goes back to the reliability factor with Database. We've been an Oracle Database customer for years and years, through PeopleSoft, through EBS and other products that we have that use the database. It's pretty straightforward, it's easy to manage, and there's pretty good support for it. All of these things are of vital importance to our business.

We'd like to get some more add-ons, such as Database Vault for security. Other than that, I'd say that support has been harder and harder to get. I can remember 14 years ago, working with Oracle support, talking to the analyst on the phone, and they would sit there and work with you until the problem is resolved. Now, we spent a lot of our time and effort and wheels trying to work with support and get handed off to the next analyst and you start from scratch. We lose a lot of time. A lot of times we just have to escalate it up, without really giving it enough time. I don't know if the level-one folks are just searching through the knowledge base, like we can, online. So the biggest problem has probably been Oracle support.

I came on board at this company in 2003. We've had Oracle Database in place since at least that time. I believe they were on 7.3 when I first started. We don't really use a lot of the features that are available in there as we're just a pretty vanilla type of operation. There are a bunch of features that we would like to use, but we just don't or we're not licensed to use them. The features we'd like to use are the compression and the encryption.

We've had no issues with deployment.

We've had nothing but good stability around Database.

We sized our database well for what our expected transactions were going to be. We never had to scale it up. Of course, you add space to it over time. We have done that with nothing that causes any issues.

I thought that the upgrades were fairly easy. I've done a few and it's fairly spelled out as there is a lot of knowledge base around out there. If you do run into problems, which I found going from 7 to 8 to 9 to 10 to 11, the fixes have been fairly easy. I expect going from 11 to 12 that they will be easy as well.

It's one of the more expensive database products. From a business perspective, we try to leverage our whole entire Oracle footprint to drive down the pricing. Instead of your list price that you see on the web for Database, for example, we can work with ourselves from Oracle and we can make a bigger purchase of more products at a reduced rate. We get the Cadillac for the non-Cadillac price.

You have to have a good plan of what you want to do, what your business is going to need. Are you going to need a Cadillac RDBS software system -- Oracle? Can you do it with one that isn't a standard versus Oracle Enterprise Edition? Stuff like that. Be sure that you know what your requirements are. Be able to look into the future and see what they are going to be in three, four, or five years hence.