Previously, we wrote on the Basics of Virtualization and Major Disadvantages of Virtualization. This time, we will discuss a topic on Database Virtualization, that is strongly associated with the rapid progress of Database Virtualization Technology : a major change of licensing models.
The introduction of new licensing models in Database Virtualization Technology
Introduction of new licensing model in Database Virtualization field was done by Oracle, in 2010 (based on memory, a reference from readers will be helpful).
Customers demand of flexible licensing models for Database Virtualization has increased. A plus cap or metering method was much needed and thankfully introduced by the market leaders.
As a result, there may be a significant reduction of the expected savings on Database Virtualization, or to subsequent restrictions on the technical implementation of Database Virtualization projects.
Different type of licensing models for Database Virtualization
Soft Partitioning : In the soft partitioning” model, a soft-partitioned server with several installed CPUs installed are mapped. This was introduced by Oracle in Database Virtualization.
Hard Partitioning : Function is quite obvious from its name : unlike soft, it is actually partitioned.
Other Proprietary Licensing models : Microsoft SQL Server Enterprise Edition is an example where the customers are licensed regardless of the number of cores or processors.
Impact and Conclusion of Database Virtualization
When less computing power from Database Virtualization technoloy is needed by the End users : basically it is still difficult to find a suitable and profitable plan from any company.
We can hope that introduction of newer companies dealing with Database Virtualization will lead to a competition and increased customers’ demand for different type of licensing models for virtualization projects will reduce the cost.
So, it is very important, particular for a new end user company to judge and learn about a specific Database Virtualization plan from a specific company before actually deploying it.
