Oracle Database

Oracle is the best DB for mission-critical OLTP applications. For read-only, reporting, light-loaded systems, people would want to consider MySQL to save license costs.

For our OLTP and DWH systems, it has been fulfilling all our requirements so far, this is in terms of availability, recoverability, performance and development. Of course, our Oracle databases have been so good for big databases but I think it shouldn't be used for small databases where the license and high hardware requirements can't be fulfilled.

Well suited: Application and User management granularity. Less appropriate: Complaints from user community, inability to sync password across PDBs.

When you need a reliable environment for production, it is great. Because of its popularity it is easy to find talent or consultants. It is expensive and it is not a fit for all use cases.

Good for enterprise, overkill for Mom/Pop shops.

Well suited for critical applications that need high availability and robust security options.

We upgraded to Oracle 12c to stay in support. This is especially critical for our SAP applications that run on the Oracle database. The upgrade process is pretty straight forward using DBUA (database upgrade assistant). Also, Oracle 12c Multi-tenant will allow us to run more databases on less hardware. We didn't have any scenarios where Oracle 12c was not suited. We have upgraded all our Oracle 11 databases to Oracle 12c.

We use it to transform data temporarily before we ETL them. We ETL millions of records from old CRM to Salesforce CRM. We use Oracle as a temporary storage to transform and clean data. It is really fast and helpful for this middle step of E-T-L. We also use AQs on Oracle.

Database patching is the most scary of operations due to service interruptions and availability metrics. The autonomous patching feature is highly appreciated and used for critical financial applications and gives us flexibility for our business plans.

It is well suited to corporate level products. If there is a price competition it can make your product more expensive.

We depend on the Oracle DB for large scale enterprise apps. May be not for micro services.

I love the quick and easy SQL. I know its not 100% standard, but outer joins with (+) are so much easier to read than "left join ... on ...". It is also easy to optimize and there are loads of parameters for all types of circumstances. I also like that I can set up DBLinks to for example SQL Server and write Oracle SQL that works against SQL Server. And I like the PL/SQL. One can write detailed and complex programs inside the Oracle database and its amazing how quickly they run. Oracle has got very big and it is difficult to keep up to date with all the different developments. I focus on the Oracle PL/SQL programming and I use Delphi for the front end. At the moment I am learning how to do REST inside the Oracle Database, and the documentation and set up is rather complex and it is time consuming to set up something that shouldn't be so complex. Oracle SQL Developer, the free DML and DDL tool that comes with Oracle is good, but slightly buggy and I much prefer Toad.

Oracle Database 12c is usually best suited to work with other Oracle products. No matter what Oracle product it may be, but it works quite well, as it can be integrated quite easily. There are lots of how-tos available for integrating with Oracle products, but outside of it, it isn't that easy, nor is there enough documentation. It is less appropriate in that case, as all products have a "preferred or suggested" database to use with it, and Oracle isn't the one for all products.

For DBAs with moderate skill sets and query, tuning is a challenge. It also helpful for maintaining multiple small databases, in a CDB.

It is a jack of all trades

When we have our disaster recovery tests each year the switchover to the standby databases is so smooth and efficient. We do this process with EOM13C and after the initial setup and configuration, it is almost automated.

Very good RDBMS for financial applications, OLTP and DSS. Many high availability options.
The 12c version has many improvements on capability and memory managed objects, etc. Offers common and shared storage of containers/auto manage of Table spaces. Global Allocation and System managed table spaces all are new features that help to administer day to day.

Well suited with legacy systems and big data. Also with images and non rational files.

It is will suited for online transaction processing. It performs really well. It is one of the best and industry standard database systems.

It is useful for highly confidential data managing projects. RMAN table restore is very useful for online recovery and online data file renaming.

So far I have not come across any areas where 12c wouldn’t work. Oracle 12c is very robust and easy for our older legacy systems to interact with.

For large scale healthcare reporting, Oracle 12c has been an excellent enterprise wide database, and reporting is faster than with previous database vendors.

For OLTP apps it is the best, for XML/JSON payloads it doesn't perform quite as well.

Oracle Database 12c is well suited to companies involved with service delivery, especially those in banking, insurance, finance, human resource, e-commerce, and any others that collect crucial and confidential information from their clients and manage it in a database for later analysis and use in enhancing service delivery. On scenarios where it's less appropriate, I cannot fathom any as almost every business handles some data along its operations and will require to back it up or manage it in some way or another.

Oracle Database 12c is well suited to companies involved with service delivery, especially those in banking, insurance, finance, human resource, e-commerce, and any others that collect crucial and confidential information from their clients and manage it in a database for later analysis and use in enhancing service delivery. On scenarios where its less appropriate, I cannot fathom any as almost every business handles some data along its operations and will require to back it up or manage it in some way or another.