May 24, 2016 Leave a comment
by Phillip Downey, WW program Director, IBM Analytics Platform Hybrid Cloud Strategy
In DB2 11.1, we introduced two new and easy to consume DB2 Direct editions: DB2 Direct Advanced and DB2 Direct Standard. Both editions bring a new dimension to the database offerings for the small and larger enterprise clients that are looking for the flexibility and scalability of the hybrid cloud. They can be acquired directly online via passport advantage and offer a simplified licensing metric and monthly subscription pricing model that are ideal for private, public and hybrid cloud deployments.
· DB2 Direct Advanced Edition
The DB2 Direct Advanced Edition has all DB2 Server and Client features from DB2 Advanced Server Edition including encryption, multitenant deployments, adaptive compression, BLU Acceleration, SQL compatibility with PL/SQL, Data Server Manager, pureScale and database partitioning feature options. It also includes federation capabilities providing access to non-DB2 database sources like Oracle, MS SQL, Teradata, Hadoop, Netezza, Spark and other solutions.
Advanced Federation Capabilities
It also includes access to 10 User licenses of Infosphere Data Architect per installation for designing and deploying database implementations.
· DB2 Direct Standard Edition
DB2 Direct Standard Edition is modelled on DB2 Workgroup Edition, which provides encryption, pureScale for Continuously available HA deployments, Multitenant Deployments, SQL compatibility with PL/SQL, Data Server Manager Base Edition, Table partitioning, multi-dimensional clustering, parallel query and concurrent Connection pooling. It is limited to 16 cores and 128GB of RAM and is ideal for small to mid-sized database applications providing enterprise level availability, Query performance and Security as well as unlimited database size
You can take advantage of the new subscription model to lower costs and enjoy licensing flexibility for on-premises and cloud deployments:
Virtual ProcessorCore (VPC) Charge metric
- Virtual processor core licensing gives you flexibility and simplified sub capacity licensing options that enables you to optimize your licensing to meet your business requirements.
- There are two Licensing Scenarios you can apply
- Simply license the sum of all available Virtual Processor Cores on all Virtual Servers the Direct edition is installed on
- OR when you can identify a Server and it is more cost effective to do so simply license all available Processor Cores on the Physical Server regardless of the number of virtual machines on the system.
- Benefits: This makes it simple for private and public Cloud deployments alike and enables you to optimise your licensing
Subscription based pricing
- DB2 Direct Advanced $354 USD per month per VPC
- DB2 Standard Edition $135 USD per month per VPC
(Prices as of May 10th, 2016 in the United States.)
Each Deployment requires a minimum of 2 VPCs except in the case of Warm standby, which requires only one VPC.
These editions are ideal for customers who want to move to a subscription based model on their private cloud or a 3rd party vendors (hosts) and pay as their applications grow in size. It is also ideal for ISV’s who charge their applications to customers on a subscription model and want an easy to order database at competitive subscription pricing.
Understanding the Virtual Process Core Metric
Virtual Processor Cores are defined to simplify licensing in the private or public cloud deployment environment. You can deploy DB2 licenses with confidence even though you may or may not be aware of the underlying infrastructure. It enables customers to easily analyze their Licensing requirements including in sub-capacity situations.
A Virtual Processor Core is a Processor Core in an unpartitioned Physical Server, or a virtual core assigned to a Virtual Server. The Licensee must obtain entitlement for each Virtual Processor Core made available to the Program.
For each Physical Server, the Licensee must have sufficient entitlements for the lesser of
- the sum of all available Virtual Processor Cores on all Virtual Servers made available to the Program or
- all available Processor Cores on the Physical Server.
Other key Virtual Processor Core considerations for you to understand
- If the number of VPCs is greater than the physical cores, then you only need to license the number of physical cores on the machine
- Minimum of 2 VPCs per deployment (1 VPC for idle/warm standby)
You can determine the VPC requirement through DB2 Itself by executing the following on each Physical or logical server DB2 is installed on and take the Online CPU Count and divided it by the HMTdegree result (threading degree) to get the count of Virtual CPU’s present.
An example of this In a Cloud deployment
- A customer buys a Virtual Cloud Server as a Service on a internal private cloud or MSP like Softlayer/Azure/ Amazon/rackspace ….
- They purchase an 8 core Virtual CPU Environment
- The customer runs “ Db2pd –osinfo” is run on the machine and shows HMTDegree of 1 and OnlineCPU of 8
The customer must license 8 VPC for this environment
An Example of a Private Cloud deployment using VM-Ware
- A customer deploys Multiple VMWare Hosts are created on a server to run DB2. The server is a 2 Socket server, 8 cores per processor, with hyper-threading turned on to a degree of 2 (16 physical cores) Each of the 11 virtual VMs deployed Reports 6 Virtual Processors.
- The Customer runs “db2pd –osinfo” across all VMWare Hosts reporting a total of Online CPU of 64 across 11 Virtual Machines (HMTDegree of 1 for all VMs)
As the Hardware can be physically Identified as a 16 core server the customer only has to pay for 16 VPC’s not 64 as some competitor programs would as it is the lesser of the two numbers.