Senior Executive at a computer software company with 11-50 employees
Real User
2021-02-09T14:52:50Z
Feb 9, 2021
This is a fairly stable language, and it's been in the market for several years. In fact, it's been around since about 1995, when the concept of object orientation started. People should use it because it's clever. On a scale from one to ten, I would give Oracle Java DB a nine.
Team Lead at a tech services company with 501-1,000 employees
Real User
2020-04-16T08:44:00Z
Apr 16, 2020
I would rate it an eight out of ten. Not a ten because it's difficult to learn. It's easier for developers but as QA it's difficult to train and deliver. I'd prefer an automation tool that doesn't have as much coding.
IT Manager at a transportation company with 1,001-5,000 employees
Real User
2019-11-13T05:29:00Z
Nov 13, 2019
We use the on-premises deployment model. I'd rate the solution ten out of ten. When we're interacting with the solution, it's usually other third-party software solutions that interact with Oracle DB. As far as our interaction, it's quite limited. We don't do much unless it's real queries. We use SQL, we use Oracle. There isn't much that we would need from the solution. We're getting the job done at the end of the day.
What is a relational database? A database is an organized collection of structured data that is electronically stored in a computer system.
A relational database is an intuitive database that stores and supplies access to various related data points. A relational database is based on the relational model where data is stored in tables in an intuitive and straightforward way, similar to an Excel spreadsheet. In this management system, tables are used to store complex data, which can be...
I rate this solution a six out of ten. The solution is good, but it can be improved by making it user-friendly and improving its scalability.
I would always suggest going with this product if the add-ons available through Oracle are required. I would rate this solution as nine out of ten.
I rate Oracle Java DB a ten out of ten.
This is a fairly stable language, and it's been in the market for several years. In fact, it's been around since about 1995, when the concept of object orientation started. People should use it because it's clever. On a scale from one to ten, I would give Oracle Java DB a nine.
I would rate this solution a six out of ten.
I would rate it an eight out of ten. Not a ten because it's difficult to learn. It's easier for developers but as QA it's difficult to train and deliver. I'd prefer an automation tool that doesn't have as much coding.
We use the on-premises deployment model. I'd rate the solution ten out of ten. When we're interacting with the solution, it's usually other third-party software solutions that interact with Oracle DB. As far as our interaction, it's quite limited. We don't do much unless it's real queries. We use SQL, we use Oracle. There isn't much that we would need from the solution. We're getting the job done at the end of the day.