Oracle Database vs. Oracle Exadata

We migrated from NoSQL to an Oracle database. One of the reasons was robust backup and recovery options available in the Oracle database, which provide zero data loss. A transactional database like Oracle is a better fit for our use case than NoSQL. On a large scale, deployment was evaluated as a cheaper option than the NoSQL engine. This conclusion came even after considering Oracle license is expensive.

Incentivized

• First, get the database on Oracle. If you are in an Oracle stack, it would be much better to use the Oracle products. If you are driving a Ferrari, you wouldn’t put a Mercedes engine in it. If you are writing a query, you cannot rely on other brands. Since I'm an architect, when I look for a product, I look for performance.
• The installation is easy because it comes out-of-the-box and you just start using it.
• Previous to Oracle Exadata, we were using a normal Oracle RAC service. We were just waiting for this product to come out.
• I'm currently writing a data warehouse on Exadata. Before this solution, we were aiming for this to be completed by 8 a.m., when our ETLs would finish. With the help of Exadata's special features, this was reduced to 3 a.m. This solution allows us to bring more data within the same time period. It provides us with more subject areas that provide more reports to our users. Our ETL times reduced to 65%, then to 50%.

Incentivized

• Best thing about it is that it supports PL/SQL which is helpful in writing complex quarries easily.
• Its storage capacity , backup and recovery features make it the best database storage tool available.
• Other thing I like about this software is its interface is so good.

Incentivized

• Customize-able for specific functionality optimized for combination of online transaction or analytical processing.
• Ability to serve mix workloads with resource management feature enables prioritizing allocation for certain workload.
• Scale-able on-premise with compatibility for cloud deployment offers flexible solution for organization considering to transition from on-premise solution.

Incentivized

• The memory demand and management makes it impossible to run it in a container.
• It is hard to perform local unit testing with Oracle even using the personal edition (aggressive all the available memory grab for itself).
• Lack of built in database migrations (e.g. as Flyway).
• The need to install the Oracle client in addition to its drivers.
• The cost of running it, especially in the Cloud.
• Comes with very spartan community grade client/management tools whereas the commercial offerings tend to demand a premium price.

Incentivized

• Patching can often become quite involved and convoluted. It should be more transparent and straightforward.
• Storage metrics can be difficult and time consuming to obtain.
• Basic administrative functions can be hard to repair when discovered.
• Vendor support can take a while to obtain. Generally several attempts are necessary to reach the right area of vendor expertise.

Incentivized

It is very likely to use this 12c (or next version) of Oracle Database. Nothing close to it in the marketplace in terms of performance, reliability and overall database management efficiency. If Oracle did one thing really good - it is it's OLTP Database I must say.

Many of the powerful options can be auto-configured but there are still many things to take into account at the moment of installing and configuring an Oracle Database, compared with SQL Server or other databases. At the same time, that extra complexity allows for detailed configuration and guarantees performance, scalability, availability and security.

Incentivized

I am comparing Exadata with the Oracle RAC database experience. In addition to Oracle RAC features, Exadata provides automatic performance optimization through Smart Scan and storage indexes. Deep integration with the Oracle ecosystem and tight coupling with Oracle Enterprise Manager
for monitoring and management. Some downsides of Exadata are: a steep learning curve, concepts like cell offloading, IORM, and flash cache behavior aren’t intuitive initially. Operating
Exadata requires specialized DBA skills.

Incentivized

1. I have very good experience with Oracle Database support team. Oracle support team has pool of talented Oracle Analyst resources in different regions. To name a few regions - EMEA, Asia, USA(EST, MST, PST), Australia. Their support staffs are very supportive, well trained, and customer focused. Whenever I open Oracle Sev1 SR(service request), I always get prompt update on my case timely. 2. Oracle has zoom call and chat session option linked to Oracle SR. Whenever you are in Oracle portal - you can chat with the Oracle Analyst who is working on your case. You can request for Oracle zoom call thru which you can share the your problem server screen in no time. This is very nice as it saves lot of time and energy in case you have to follow up with oracle support for your case. 3.Oracle has excellent knowledge base in which all the customer databases critical problems and their solutions are well documented. It is very easy to follow without consulting to support team at first.

Incentivized

Overall the implementation went very well and after that everything came out as expected - in terms of performance and scalability. People should always install and upgrade a stable version for production with the latest patch set updates, test properly as much as possible, and should have a backup plan if anything unexpected happens

Because of a rich user base and support for any critical issue, this is one of the best options to choose. In case the project has a TCO issue, it can compromise and choose Postgres as the best alternative. SQL server is also good and easy to code and maintain but performance is not as good as the Oracle

Incentivized

I couldn’t find all the options listed here, so I’m
summarizing the ones we considered during our evaluation before selecting
Oracle Exadata Service on AWS:


Continuing
to use the Oracle RAC on‑premise database
Running
Oracle Database on AWS EC2
Using
Oracle Database through the AWS RDS service


Since we wanted to retain Oracle RAC capabilities while
achieving high performance and maintaining our presence in the AWS public
cloud, we selected the Oracle Database @AWS Exadata service.

Incentivized

• Our product's ability to monitor the Oracle database has generated significant revenue from only a few customers, totaling $1mn.
• An Oracle account helps analyze the patches and changes going into it, enabling the team to enhance the product and update it more quickly. It reduced the effort by more than 50%.
• Being a closed-source code DBMS, it is difficult to ascertain the exact exploits of the vulnerability to provide patches to customers and requires reverse engineering.

Incentivized

• One of the central critical systems was migrated from a large 4-node Oracle RAC running on legacy hardware. This application was experiencing severe performance issues literally causing loss of service for numerous customers. Once it was migrated to a 2-node Exadata server, its average performance improved almost by a level of magnitude, therefore eliminating any signs of application slowness.
• Numerous application databases were migrated to Exadata servers which reduced the overall cost of hardware due to Exadata's price structure.

Incentivized