There is a need for more storage to be allocated, but over a period of time, it becomes impossible to reduce it after using it. If you use more storage and don't need it in the future, then you have to remove some data and use less storage. You cannot dynamically add and reduce processors in the product. If you choose a larger storage capacity, later on, it is not easy to reduce the storage allocated. The aforementioned details contain areas that can be improved in the product.

Nothing comes to my mind that needs improvement in the tool. It pretty much has a whole great set of features.

The installation process is complex. Oracle can make the installation process better.

An improvement for us would be the inclusion of support for an internal IP, so we could use it directly with the VCN in Oracle Cloud. Basically, the autonomous data warehouse can only be reached using the public network which is not ideal for some companies. We usually use private network and need private IP to include it into our subnet.

We do not need more for now, it's working perfectly. I know Oracle is working on a solution.

My main suggestion for Oracle is the configuration and key values that come for JSON files. When we create a table, especially if you see in our RedShift or some other stuff, if I create a table on top of a JSON file with multiple array columns or superset columns, those column values create some difficulty in Oracle. 

In terms of architecture and pricing structure, I feel it is a little bit costly compared to Azure. It's fine compared to RedShift, but compared to Azure, it's a bit pricey when you calculate for one TB storage plus around five hours of reporting with the frequency of 1TB data. The cost adds up, making Oracle a bit expensive.

There are two clusters I'm expecting to improve. The super set datasets need a bit of enhancement, especially the column values that come with the super in these. There's a separate column called super. Those kinds of elements have to be improved in Oracle. 

Another aspect is the pricing strategy, which should come with different options. Cloud users prefer keeping their applications in OCI cloud. Many are moving to Postgres for savings. That's a great deal for us.

We recently moved our Oracle database to Postgres, saving a significant amount. Oracle Autonomous Data Warehouse should consider more flexible pricing strategies based on usage to accommodate the diverse needs of users.

In future releases, I would like to see better support for various file systems when creating tables. Plus, a bit more focus from the Oracle community on improving things. And lastly, the pricing strategy could be tweaked to leverage the power of Oracle Autonomous Data Warehouse further.

The service could be improved by:

• Providing Access to SYS schema
• Allowing access to SYSTEM schema
• Provisioning to apply user patches, and not just automated patches
• Having provisions to administer the database by a DBA as an add-on to autonomous management
• Getting provisions for fine-grained configuration
• Allowing for migration tools from other cloud services, including migration from Amazon Redshift, RDS, and Aurora
• Data Pump integration
• Simplified Integration with other Oracle cloud services such as the Autonomous Container Database
• Simplified migration from a local database 

Existing Oracle customers interested in the Autonomous Data Warehouse should know that this is a different experience than the classic Oracle DB Enterprise Edition. Yes, this is a database capable of running an entire enterprise, with unparalleled performance, available disaster recovery, and cutting-edge analytics. But the analytics come with new Notebook technology to code collaboratively with the rest of your team, not the classic data miner GUI interface. Don't expect to tune your queries with various indexes and fancy partitioning strategies. The system is designed to run on autopilot, not be carefully controlled and highly tuned. And, due to security limitations, neither the powerful GUI development environment Application Express (yet?) nor Oracle R Enterprise are not available. Hopefully these features can be added in a future release and the system can be accessed more easily without compromising the database's security.

They should add features to make the solution more user-friendly. They should work on making its integration with GoldenGate easier. It would increase work efficiency while loading the data into the data warehouse.

Ease of interconnectivity could be improved by which I mean setting up the VPN access and the like from on-premises to cloud. If that was a little easier, it would certainly make my life easier.

The tool is not as autonomous as it's led to believe. A lot of the tools that were previously there have now been taken away. If we write our queries in the same way, then it doesn't trigger the autonomy in the way that it should.

Oracle should increase visibility options because what's available now is limited. Experienced users are easily able to understand everything, but from a layman's perspective, it's confusing and can be difficult to understand the steps required. In that sense, the solution requires an upgrade. I recently worked with the machine learning model offered by Oracle and could only find the visualization, without other options. There should be additional 3D, and 4D representations as well as other options that competitors such as Azure are offering for machine learning models. Azure offers its own machine learning studio, so Oracle should do the same, not only for machine learning but for all the database services.

It is good as data warehouses go, but it is not that good for really big data.

It doesn't work well when you have unstructured data or you need online analytics. It is not as nice as Hadoop in these aspects.

It is very important the integration with other platforms be made to be as easy as it is with an on-premises deployment. On-premises,  you can integrate with different vendors such as Microsoft. There should be flexibility in terms of how you can accomplish things and not just with a single vendor, but with all vendors.

We are thinking of changing to a data warehouse on the cloud. I don't know if Oracle is in the cloud as well or if we will turn to another solution such as Google Cloud. 

The initial setup was pretty complex. It was not easy.

It would be ideal if the company could manage semi-structured data such as JSON. Some other data warehouses can handle that. However, Oracle doesn't seem to be able to.

An ADB serverless service provides no control over storage, host, and facilities. One of the major problem is creating custom tablespace. The ADB serverless option doesn't support custom tablespace creation, which could cause issues during on-premise database migration that requires specifically named tablespace. There should be an option to create customized tablespace. 

There are many data types and parameters which are not supported. That should be improved a bit so many customers can adopt.

The solution needs to offer support for the R language. It doesn't exist and it really is something they should have. 

Sometimes the solution works differently between the cloud and on-premises. It needs to be more consistent and predictable.

There isn't support for data migrations. It would be helpful to have more documentation or information about this process. It's not easy for us to find online or on their website.