Oracle Database Reviews

Oracle Database is suited for for scenarios where the database is large and there is a need for reliability, security and availability at scale. The pricing reflects this. It won't be well suited and will be expensive for mostly dev and test environments or where reliability is not a factor or issue.

Oracle Database should be a good fit for any applications who need a database, especially eCommerce use cases. There might be better choices for lightweight applications or applications with very large data sets.

It is highly performant and guarantees data consistency based on ACID compliance. Oracle Active Data Guard allows us to open the standby database for read operations. With Oracle 19c , Oracle also allows to do DML redirection on standby DB which can help with some reports that need temporary tables.
Using XML/non-structured data is not easy and I have noticed performance issues when the XML becomes deeply nested.

I believe that Oracle Database can be used almost on any scenario, starting with small department solutions to actually any enterprise level system. It includes many features that allow a single database to work as an OLTP and Data Warehouse at the same time, reducing hardware requirements and the need to implement ETL or integration solutions between OLTP and DW.

Although this database is massive, it's the best selection for quite a lot of things. From the automatic query optimization to the physical table lookup, every single aspect is a product of years of innovation. Most of the tools/techniques used today in other DBs were first was implemented in this. Oracle Database can fulfill nearly every database requirement a small, a typical, or a giga-company needs. With the right professionals, this tool can run countries!

We primarily use Oracle in our organization, except for a few applications which use other databases like SQL Server, Redis and MongoDB. Primarily, Oracle Database 12c is used to manage data for various applications all across the organization by multiple applications like Ticket Car, DataMart, ERP for invoicing and master catalog, and for Watts processor by Edenred Brasil.

While Oracle is more or less a bulletproof database server, if you don't have an Oracle DBA on staff you are in for a lot of trouble. We use Oracle, Sybase, SQL Server, and SAP IQ. Of the 4, Oracle is the most painful to troubleshoot when things get weird. Now, if you do have Oracle DBA's on staff, Oracle is a perfectly good database solution, but I can't say that it is in any way better than Sybase and I would say it is a touch less reliable that SQL Server.

One of the features that benefits me is that it is able to set up an audit on specific tables to specific users, via setup Audit policy.

Most of the functionality needed by the application was already supported by 12c, so I did not explore any other features needed. I believe 12c may not be suitable for applications with a small footprint due to larger infrastructure requirements. That is why many developers have chosen databases such as PostgresSQL or MongoDB.

Well suited as the base backend structure for any ERP system or for EDW structure in the cloud. Less appropriate for a small business start-up.

For compliance activities, it is very useful. It also works very well for managing all of our different case types. From an audit perspective, I wouldn't recommend it based on all the needed customization. Over customization has also led to performance issues. This may be, in part, a product of our agency as well as some limitations of the database.

It is well suited for large enterprise applications, but not for smaller applications.

It is the most resilient database that I've used.

12c is appropriate for anyone using an Oracle database already and needs to upgrade. Similar database models can also lateral. The pluggable databases are great for use in both provisioning and portability. For those who need self-service provisioning, 12c is very useful.

For data warehouse environments, it is a great option. We used to run it using a non-EXA appliance and batches used to take like 3 to 4 hours but it was reduced to 30 min which helped our customers. I think Oracle has an option for any need that any customer has.

Oracle Database is well suited for practically any data store. The hardest portion though is using large objects, such as images, and being able to query those objects.

Oracle database is a perfect choice when customers have Oracle hardware and they're looking for relaible OS like Linux and Solaris. Customers who have Oracle applications will find appropriate to have Oracle Database due to single point of support and fewer resource requirements to maintain the data.
Oracle Database will be less appropriate for customers who have a smaller budget and hardware with slower performance.

Oracle has been the top choice and the best relational database solution in the market for years..for companies that can afford to pay for it. Every Oracle component is very expensive, so it is not as well suited for a small company which cannot afford to have a large budget for it.

Standard edition for small organizations that don't need partitioning or multi-tenant capabilities. Runs best on Oracle engineered systems and has much more licensing flexibility

I would recommend it for telecommunication companies due to the volume of information managed by these companies.

Higher education is well suited for Oracle Database 12c. We also recommend 12c to the HR and Financial Aid departments within our college.

Well suited for large data and for complex applications. It is great, secure, and support, in general, is good.

Not well suited for small companies (cost) and for home projects. There is not a smaller version of Oracle available for home use like SQL Server. You can find many free options for your home or small business without having to pay thousands of dollars compared to Oracle.

The Oracle Database is well suited in any environment that needs to store large amounts of data or support multiple applications across different platforms.

Oracle is mostly good for OLTP based transactions. I see it is limited for the micros service, but I am still exploring that area. Invisible column and identity columns are well used in my applications.

A little more effort on making SQL Developer a better tool could drive the usage a lot more.