Oracle Multitenant Reviews

We are still working with Oracle, specifically Oracle Database and Oracle Analytics. We have many customers, and we use the multitenant model. We use the on-premises deployment and not the local cloud, however, it is actually the same. 

We are integrators, mainly using VPD, the virtual private database, in terms of security of data between customers. We do not handle the installation side; that needs to be addressed by DBAs.

Our primary use of Oracle includes writing queries for retrieving data for customers without worrying about the customer ID, user ID, as it is automatically connected to each query. This ensures the right data is retrieved for each customer without involving wrong data. 

We use the VPD, which aligns with our data security needs across customers, though it is not easy to maintain. Despite the challenges, Oracle works well for us.

We are currently migrating to Oracle's multitenant architecture and are in the process of moving databases over from the old architecture to use this as a multitenant database. We are customers of Oracle and integrators of this solution.

This is a cost-effective solution because we're using the free version and we receive three databases for the price of one. The DBAs now benefit from having more databases and nobody is negatively impacted. It's a good investment. 

I use the solution in my company since queries and everything can be easily manipulated. All the data can be easily drawn out if we write simple queries. It is quite easy to access the database.

Everything is going well with the tool. From the scope of improvement, I would say that people are adopting new query options. Certain databases like MongoDB adopt new query options so that they can just pull the data. Using new query options, we can generate the data, which will be pretty helpful for those users who don't have any knowledge about databases. They also can face the data without learning to do some queries.

We have multiple customers on Oracle Multitenant, and each one needs to see their own data. 

Oracle Multitenant has a filter for private databases. 

I use Oracle Multitenant for database operations, particularly in the banking system.

The modernization aspect of Oracle Multitenant is significant. It wasn't available previously in database technology, but now it is, enhancing database consolidation. The pluggable databases feature makes management and migration easier. These databases are easier to administer compared to traditional non-container databases.

We [my company] are in the consulting field. Use cases are based on customer needs. We do projects and implementations based on customer requirements and situations. 

Once you start using it and want to keep in touch with the latest version of Oracle, the latest versions are plugged into the database. There's no other choice.

For me, the best features are the level of separation and independence, the support of development processes, and the optimization of hardware resources.

Moreover, Oracle definitely works with AI, like other vendors. You can do AI projects in Oracle Cloud and all the databases. The most important thing about AI and Oracle is Oracle Cloud, where you can do AI projects or proof of concepts.

I primarily tested on the cloud but I tried the on-premises version once.

It's about consolidation. They are trying to solve all the issues. Oracle has many solutions for managing resources. For example, if you have many applications to maintain, some applications share the same database. They need to restart, which will impact the other applications. You will have to stop all the services and that adds to downtime.

To solve this issue, Oracle Multitenant provides one container database. It is set up with many databases within each other as in a schema database. You will make each application connected to the pluggable database.

The database becomes pluggable. Inside this container is called a pluggable database and each application contains this pluggable database inside multitenant. We can then share resources like control files, memory, etc. This lets you stop and start each application without impacting the others. This resource sharing is the most valuable feature

If you would like to do this with the older version or another system, you would have to install many databases and each database will get a resource. Then you have to buy resources for the license, CPU, server, etc.

This is the main feature they use this solution for. Of course, if you get a cloud database service, they may not give you a dedicated database. If so, they will provide a pluggable one for part of the container like virtualization or clone. You can use this solution in that way also.

According to my point of view, this is the main feature with 12c compared to 11. It is called 12c for the cloud since they are preparing to move more to the cloud.

In the cloud, you're sharing resources. Not every database has a high load, so they distribute resources from one controller to this pluggable database.

They are sharing resources because there are usually wasted resources otherwise. There are companies that check the vitalization of your server, memory, hardware, and infrastructure. You will find that 70% or 80% of your resources are wasted.