Oracle Autonomous Data Warehouse vs. Oracle MySQL Cloud Service vs. Amazon Redshift

II would recommend Oracle Autonomous Data Warehouse to someone looking to fully automate the transferring of data especially in a warehouse scenario though I can see the elasticity of the suite that is offered and can see it is applicable in other scenarios not just warehouses.

Incentivized

It is very scalable and it gives us backup for everything. Because of this feature, we (as a developer) can do any R&D if required. It is very stable so we can get any type of help. It has a recovery feature also which we used recently for my project. It is very easy to recover.

If the number of connections is expected to be low, but the amounts of data are large or projected to grow it is a good solutions especially if there is previous exposure to PostgreSQL. Speaking of Postgres, Redshift is based on several versions old releases of PostgreSQL so the developers would not be able to take advantage of some of the newer SQL language features. The queries need some fine-tuning still, indexing is not provided, but playing with sorting keys becomes necessary. Lastly, there is no notion of the Primary Key in Redshift so the business must be prepared to explain why duplication occurred (must be vigilant for)

Incentivized

• Very easy and fast to load data into the Oracle Autonomous Data Warehouse
• Exceptionally fast retrieval of data joining 100 million row table with a billion row table plus the size of the database was reduced by a factor of 10 due to how Oracle store[s] and organise[s] data and indexes.
• Flexibility with scaling up and down CPU on the fly when needed, and just stop it when not needed so you don't get charged when it is not running.
• It is always patched and always available and you can add storage dynamically as you need it.

• Oracle database has ability to store large scale of data.
• It can support any kind of scenario with any label of system.
• Encryption and security is the key features of Oracle database 12c.

• Redshift is fully managed. Small teams do not have the resources to maintain a cluster. CloudWatch metrics are provided out-of-the-box, and it is easy to configure alarms.
• Redshift's console allows you to easily inspect and manage queries, and manage the performance of the cluster.
• Redshift is ubiquitous; many products (e.g., ETL services) integrate with it out-of-the-box.
• Writing .csvs to S3 and querying them through Redshift Spectrum is convenient.

Incentivized

• Level of integration or compatibility to connect it to different applications can be improved
• The support service is slow
• The issue is with the record number limitation of not being able to bring back more than one million records or not being able to export larger datasets to Excel

Incentivized

• It has some issues [when] performing local unit testing in personal edition.
• It is costly if we will go for cloud.
• Need license for some features.

• It could benefit from adding data integrity and programming tools common to other database management systems.
• Amazon Redshift is based on PostgreSQL 8.0.2. That version of PostgreSQL was released in December 2006. While PostgreSQL was much improved since then, the new features were not implemented in Redshift. Many basic features are missing from it.
• Primary keys can be declared but not enforced. Referential integrity (foreign keys) can be declared but not enforced. UNIQUE and CHECK constraints are not supported and cannot be declared.
• IDENTITY can be declared on a column, and Redshift will put unique values into it. However: IDENTITY values in the newly inserted rows won’t be incremental or sequential. To implement a sequential number, you need to write your own custom code.
• There are no stored procedures in Redshift. We are writing SQL script files, and then parsing and running them one statement at a time from a Python program. This also enabled us to implement execution-time error logging.
• In SQL scripts, to check for the row count of affected rows, a complicated join query against some system tables or views has to be executed.
• Data Control Language (DCL) does not exist. No statements like IF, WHILE, DO, RAISERROR, etc.
• On performance of views… Views do not “pass-through” a query parameter which is a potential problem for performance.
• When selecting against a view with the WHERE clause outside of the view, the inner query of the view will be executed first without consideration for the WHERE clause, and only then the WHERE clause will be applied.
• Certain clauses of SQL work many times faster than other clauses. So be careful and test your statements for performance earlier rather than later, especially if working with a large data set.
• There was a situation when DELETE FROM JOIN was unacceptably slow. Replacing JOIN with the USING clause made DELETE instantaneous.

Incentivized

Because

• It is really simple to provision and configure.
• Does not require continous attention from the DBA, autonomous features allows the database to perform most of the regular admin tasks without need for human intervention.
• Allows to integrate multiple data sources on a central data warehouse, and explode the information stored with different analytic and reporting tools.

Incentivized

Overall it serves all our aspects of data management like data cleaning, data manipulation, and data reporting on the cloud platform. We can create stored procedures and triggers in it very easily as all the options are self suggested in it. We can easily attach the results of ARS to the other tools as well for drawing the statistical results.

Incentivized

The support was great and helped us in a timely fashion. We did use a lot of online forums as well, but the official documentation was an ongoing one, and it did take more time for us to look through it. We would have probably chosen a competitor product had it not been for the great support

Incentivized

Understanding Oracle Cloud Infrastructure is really simple, and Autonomous databases are even more. Using shared or dedicated infrastructure is one of the few things you need to consider at the moment of starting provisioning your Oracle Autonomous Data Warehouse.

Incentivized

Our organization adopted Oracle almost 20 years ago and there were a few options at that time. Oracle was the leading database tech company at that time and it was a safe choice to us. And they have been evolved and always ahead of new technologies, high performance, and professional business support. We didn't find a good reason to replace Oracle with any other competitors.

Incentivized

It has the most stable database. It smoothly supports [a] huge [amount of] data. Security-wise it is best among them. It is a very large community and has well-defined documentation, which can support [during the] implementation of the Oracle database. We can easily scale up servers whenever [we] change our requirements. Oracle12c is best for large-scale projects like banking and retails.

We evaluated [Amazon] Redshift vs BigQuery vs Amazon EMR, back in 2014. Back then BigQuery cost was slightly higher than that of [Amazon] Redshift price structure. Amazon EMR, needs lots more management (Admin tasks) and EMR is designed to be ephemeral and not designed to be a data store. [Amazon] Redshift was ideal with the price structure, performance and ROI[.]

Incentivized

• Overall the business objective of all of our clients have been met positively with Oracle Data Warehouse. All of the required analysis the users were able to successfully carry out using the warehouse data.
• Using a 3-tier architecture with the Oracle Data Warehouse at the back end the mid-tier has been integrated well. This is big plus in providing the necessary tools for end users of the data warehouse to carry out their analysis.
• All of the various BI products (OBIEE, Cognos, etc.) are able to use and exploit the various analytic built-in functionalities of the Oracle Data Warehouse.

Incentivized

• It has ability to handle [a] huge [amount of] data and give [the] best performance
• Easy to write PL/SQA queries
• Secure and encryption option

• It allows for an almost seamless integration of our data which can then be used by other departments for analytical purposes.
• No in house resources are needed for keeping the data alive and performing backup/migration tasks of the data in its end state.

Incentivized