The initial setup of Oracle Autonomous Data Warehouse is easy and basic, especially if one doesn't use the tricks to get Oracle Exadata for use. One doesn't need to know or be involved in technical stuff to do the setup since, at the least, knowledge might be required when working with some external connections, but it is easy because everything can be done within a couple of clicks.

The solution is deployed on the cloud.

For deployment, you don't need any technical guidance since you can sit, find it on the web, and prepare an Oracle Autonomous Data Warehouse platform by yourself for free for a limited time.

The people needed for the deployment and maintenance depend on the implementation one wants. If you do a simple implementation, you don't need anybody for maintenance since everything is on the cloud. You only have to schedule your backup or see if Oracle can schedule a backup, and you don't take care of the backup. For some more sophisticated or technical implementations, you will need staff for some data warehouse except for some parts of the maintenance like backup, patches, or upgrades since these are a few things you take care of in the background, and you only seek help with the maintenance part, if needed.

The initial setup is complex. It is not a simple product, so it is complex.

The number of people required to maintain the solution depends on the database size. Also, it depends on the number. There is no formula stating that if I have two databases, then two people are needed. In short, it is very much dependent upon where it is being used.

The initial setup for this solution is straightforward, with almost nothing to do. The setup is very, very fast.

The initial setup is fine if compared to RedShift; this is easy. 

On AWS or Azure, spinning up a data warehouse involves things like Glue jobs, schedules, file transfers from S3, crawler configurations, and processing shifts. It's a whole orchestration! 

With Oracle Autonomous Data Warehouse, things are much simpler. Creating a structure, initializing the servers, extending the servers, those are all things that are very, very easy. That's the main reason we use it. 

Postgres is the first reason, and the second one is it's easy.  That's one of the main reasons we haven't migrated away yet. It frees us from the complexities of server and configuration management, allowing us to focus on what truly matters: reporting and queries.

No setup is required as the service is fully automated, and runs on Oracle Cloud. Only an account registration is needed. 

The solution's initial setup is straightforward. But, the implementation gets too complicated when we load the data from different systems into our data warehouse.

The initial setup is extremely simple. If you know in advance what you intend to set up, it takes less than five minutes before you're actually running or creating tables and placing data. It's very quick. We do the setup ourselves, specify capacity, username, password and then it should be up and running in a matter of minutes. 

It doesn't require any maintenance on our part, that's all controlled by Oracle. The patching is done automatically, typically with zero outage and there's no performance tuning really, because it does the majority of it itself. Internally, we'd have a couple of hundred people dealing with the product at any one time. 

The product is easy to set up, but it can be very difficult once you get beyond the autonomy. The solution could be deployed on public, private, and hybrid cloud environments. The time taken for deployment depends on the client.

The configuration in our company took a few weeks and we implemented it in-house. We deployed the solution with the help of Oracle Autonomous Database. I would suggest that any company still relying on an on-premises environment should migrate towards a cloud service provider, whether it's Microsoft, Oracle, or Azure. We have around eight to 10 users. 

Its setup is somewhat simpler than Hadoop because it does not have so many components. We have had two—in some cases, three—people in the past for the deployment.

In terms of maintenance, after some time, you probably don't need permanent staff for maintenance. Once it is in a steady state, our observation is that the clients can survive with on-call support. The IT department of the bank is able to manage without external consultants. They do the operational stuff, and if there is a problem, we help them, but after some time, support is not required 24/7. Previously, it was also available on-premises, and then they re-architected it to be on the cloud. Now, they're on the cloud, which is another reason it does not require on-premises support.

There is no installation for this cloud-based system.

The initial setup was now straightforward or easy. It was rather complex. A company needs to be prepared for that when they implement it.

With pre-DBA knowledge, it is simple, straightforward procedure.

The initial setup was handled by our partner. We didn't handle it. I wouldn't be able to speak about if it was complex or straightforward as I wasn't personally involved.

If you are familiar with Oracle products, the initial setup is easy and straightforward. The deployment took only a few hours because it is on the cloud.