Licensing costs are typically arranged by Oracle CPU. You pay for the access and then you can scale. If you have a fairly intensive database activity, you'd scale up by CPU, and you're paying by the CPU and the uptime. So there's a marginal uptime cost. If your operations are only running 12 hours a day, you can put your database offline after that and reduce costs. If you had multiple databases supporting the same environment, let's say a development, a test, and a production, you could just turn off the development and the test when you're not fixing anything or developing, and that would reduce your costs. There is also a free version of ADW that can be accessed if you create a cloud account. I think it allows for 20MB of space that is free.
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.
CTO at a tech services company with 51-200 employees
May 15, 2020
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.