The most valuable feature we have found is the multi-tenancy. You can set up background processes and memory at the container level, not at the pluggable level. he second thing is, I can set up a disaster recovery solution for the container database, not at the pluggable level, so that if I have more pluggable databases, I do not need to worry about disaster recovery setup at the pluggable database level. I only have to set it up one time at the containment level. I can reduce my time, effort, cost, everything. I feel this is one of the best features in 12c, multi-tenancy.
Another valuable feature Oracle has released is the Flex ASM in RAC. In 10g and 11c, if something goes wrong for you with A, some instance, your database will go down. But in 12c, if something goes wrong for you with A, some instance, your database will not go down. You automatically use the next two machines, A, some instance. These are two wonderful features that we have used in database 12c.
One more very cool feature is called Information Lifecycle Management, ILM. It is one of the best features right now.
Instead of maintaining multiple servers, multiple databases, multiple disaster recovery solution setups for several levels, if you implement the 12c multi-tenancy, I only have to set it up for one container, not for all of the pluggable databases. I can reduce my support, my time, my effort, my cost, my server cost.
We have been using 12c for 10 months.
We have been using it for the past 10 months. We have not had any stability issues, at all. We updated the PSU patches, just the CPU patches; it's up and running for months.
We haven’t exactly scaled it right now. Once we upgrade the remaining databases, we can go ahead with scaling it.
We raised a couple of SR requests with the Oracle team, and they responded quickly. We have successfully upgraded one database to 12c.
We are really pretty happy. In the coming months, we are going to upgrade three to four databases to 12c. I attended an Oracle OpenWorld conference to get some information about how I can upgrade with nearly zero down time. I was looking for that.
Upgrading it is not easy, because application to application could be different architecture. Before upgrading to 12c, we have to go into QA and development, from us to QA and development. Once that is successful, you can go ahead with production. Until now, out of six databases, we have upgraded to 12c on one platform; it was smooth.
When you upgrade from 11g to 12c, consider your execution plans. Before upgrading, check it out in the QA and development environments. The third thing is, when you go about upgrading from 11g to 12c, plan how many databases you are going to make as pluggable, and how much memory it requires, and what flat file from exactly you are moving to upgrade. These are the three things you have to keep it mind when it comes to upgrading from 11g to 12c.
Although it is smooth coming into production, you have to be careful. Until now, it has been very smooth. We didn't raise any issues, but we have raised a couple of SR requests. Oracle has provided a smooth solution.
:-)
To say the truth, I was not thinking straight on MS SQL, although truly I put it behind Oracle in rank. In my mind I had two main topics that can impact Buggy Maintenance:
1. Instability of the system - crashes, bugs.... Oracle has many, but others have more. This is translated in more maintenace time.
2. Lack of features. I recall one time, I was programming in one free RDBMS and it had only few (very few) built-in average functions. Can you imagine your developers spending time to create libraries on such common things ? What about the rest ?