0% found this document useful (0 votes)
118 views24 pages

Silo - Tips - Enterprisedb Licensing Management Guide

The document provides an overview of EnterpriseDB's licensing policies and compliance procedures. It discusses the different types of licenses that apply to EnterpriseDB software, including PostgreSQL and Postgres Plus Advanced Server. It also covers how to measure usage for compliance purposes, such as by sockets, vCores, UniCores, servers, and cluster nodes.

Uploaded by

elpatron nacho
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
118 views24 pages

Silo - Tips - Enterprisedb Licensing Management Guide

The document provides an overview of EnterpriseDB's licensing policies and compliance procedures. It discusses the different types of licenses that apply to EnterpriseDB software, including PostgreSQL and Postgres Plus Advanced Server. It also covers how to measure usage for compliance purposes, such as by sockets, vCores, UniCores, servers, and cluster nodes.

Uploaded by

elpatron nacho
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 24

EnterpriseDB

Licensing Management Guide

October 07, 2014


EnterpriseDB Licensing Management Guide

Table of Contents
Overview.............................................................................................................................3
EnterpriseDB Compliance Policy.......................................................................................4
Product Subscriptions and Entitlements............................................................................5
Subscription Entitlements to EnterpriseDB Software ...................................................6
Software Licenses ............................................................................................................7
PostgreSQL....................................................................................................................7
The PostgreSQL License and Obligations................................................................7
Postgres Plus Advanced Server and other EDB Software............................................8
EnterpriseDB Limited Use License and Obligations.................................................9
EnterpriseDB License, Support and Services Agreement and Obligations............10
Subscription Compliance.................................................................................................11
What to Measure .........................................................................................................12
How to Measure...........................................................................................................13
Sockets for Bare Metal Environments.....................................................................13
vCores for Virtualized Environments.......................................................................14
UniCores..................................................................................................................16
Servers.....................................................................................................................18
Cluster Nodes..........................................................................................................19
Collecting Usage Information.......................................................................................19
Reporting Usage Information to EDB..........................................................................20
Postgres Enterprise Manager (PEM)...............................................................................21
Additional EnterpriseDB Tools and Software...................................................................21
Third Party Add-on Components......................................................................................22
Appendices.......................................................................................................................22
[1] The PostgreSQL License........................................................................................22
[2] EDB Business Agreements.....................................................................................23

© 2014 EnterpriseDB Corporation. All rights reserved. EnterpriseDB and Page: 2


Postgres Plus are trademarks of EnterpriseDB Corporation.
Version 1.2
EnterpriseDB Licensing Management Guide

Overview

EnterpriseDB (EDB) publishes and/or distributes multiple software programs


to address the database needs of enterprises at the lowest possible total cost
of ownership compared to traditional database vendors. Some of these
programs are distributed under commercial licenses and some are distributed
under open source licenses.

The bundling of commercial and open source software has multiple beneficial
effects for customers:

• EDB's own engineering team is augmented by a large number of


developers who are part of the PostgreSQL community, providing
added programming power at a lower cost than closed source vendors.
Our lower development expenses are then passed on to our
customers as lower software costs, providing up to 80% savings
compared to traditional database vendors costs.
• The large cast of community developers/contributors combined with
EDB's enterprise focus means that database features that customers
want are more likely to be available than in software from many closed
source vendors with a more singular development focus.
• Basing our software on open source code makes our products more
flexible and customizable than closed source vendors' products.
• A single subscription-based fee simplifies cost management by
including licensing, maintenance, and support in one renewable fee
without penalties as an Operating Expense.
• No upfront perpetual license fees lowers a customer's initial purchase
of a database solution.
• Your Total Cost of Ownership is dramatically lower than that of a
database from a traditional database vendor.

EDB is committed to helping our customers succeed in their use of open


source based software along-side their commercial software programs. This
guide is designed to help organizations understand the licensing policies
associated with EDB software with a focus on maximizing their software
investments, simplifying compliance efforts, and minimizing their costs as
much as possible.

Paramount to achieving these goals is understanding:

• how software programs are bundled into products

© 2014 EnterpriseDB Corporation. All rights reserved. EnterpriseDB and Page: 3


Postgres Plus are trademarks of EnterpriseDB Corporation.
Version 1.2
EnterpriseDB Licensing Management Guide

• what a customer pays for when purchasing a product


• which license a program is distributed under
• what user obligations exist under that license
• what Unit of Measure (UOM) is associated with a product
• how many UOM your purchase authorizes you to use
• how to determine your consumption of that UOM, and
• if your consumption is compliant with your authorization.

NOTE: This guide does not constitute a formal business agreement with EDB,
nor can it be used as a substitute for any existing business agreement with
EDB. This guide may not be included as part of any existing business
agreements customers and EDB may have entered into when transacting
business. Any pricing information in this guide may not be assumed to be any
part of an official price quote. The sole purpose of this document is to help
readers understand the key concepts and usage characteristics behind those
agreements with respect to licensing and consumption and how best to use
and comply with them.

EnterpriseDB Compliance Policy

Unauthorized or unlicensed use of EDB's software may constitute a breach of


contract and/or a violation of intellectual property rights laws. Non-compliance
may be deliberate, but may also occur unintentionally due to a lack of
knowledge of the applicable license terms, lack of license management, or
lack of controls over the distribution of the software within an organization.

EDB is committed to protecting its contractual and intellectual property rights


and will assist our customers and partners in obtaining and maintaining
adequate subscriptions or licenses for their right to use EDB developed
programs and/or obtaining software maintenance and support.

If a subscription or license violation is identified, EDB will provide written


notification of the violation to the non-compliant organization and generally will
allow thirty days to obtain the appropriate subscriptions or licenses or to
otherwise correct the violation. EDB will assist the customer or partner in
obtaining the appropriate subscriptions or licenses in the proper quantities for
the desired use of the EDB software programs.

A customer may correct a compliance shortfall in one of the following ways:

• by purchasing sufficient subscriptions or licenses to cover the

© 2014 EnterpriseDB Corporation. All rights reserved. EnterpriseDB and Page: 4


Postgres Plus are trademarks of EnterpriseDB Corporation.
Version 1.2
EnterpriseDB Licensing Management Guide

compliance shortfall,
• by uninstalling enough EDB software to return to compliance, and
• by reconfiguring the operating environment to return to compliance
(e.g. virtualization).

NOTE: As a general practice EDB does not require retroactive payment for
correcting compliance shortfalls provided the customer is current and timely in
submitting their annual usage reports and any non-compliance reports are not
overly excessive or egregious in nature.

Product Subscriptions and Entitlements

Unlike traditional software vendors, EDB does not sell its software programs
under a perpetual software license where the customer essentially buys the
software for a one-time, up-front fee (a Capital Expense) and then separately
purchases software maintenance and support (an Operating Expense) at
regular intervals.

Instead, EDB sells a simpler all-in-one subscription to its software that


includes a right-to-use license, software maintenance, and support services
for the term of the subscription (all as an Operating Expense). Subscription
terms usually last from one (1) to three (3) years but may also be of longer
durations. At the end of a subscription term, unless the subscription is
renewed for a new term, a customer loses the right to continue using the EDB
commercially licensed software as well as receive software maintenance or
support services.

An EDB subscription product may consist of one or more software programs,


software maintenance services, software support, as well as other ancillary
goods and services. Some of the software is developed, maintained, and
supported by EDB and may be distributed under a commercial license. Other
software may not be developed or maintained by EDB and may be distributed
under one of a number of open source licenses.

When you purchase a subscription product from EDB, compliance for any
included EDB developed software applies to its installation, use, maintenance
and support, while compliance for any included open source software applies
to EDB supplied maintenance and support only.

A customer's entitlements to EDB subscription products are contained in


Schedule A Subscription Entitlements to EnterpriseDB Software of the

© 2014 EnterpriseDB Corporation. All rights reserved. EnterpriseDB and Page: 5


Postgres Plus are trademarks of EnterpriseDB Corporation.
Version 1.2
EnterpriseDB Licensing Management Guide

EnterpriseDB License, Support and Services Agreement, and is summarized


in the section immediately below.

Subscription Entitlements to EnterpriseDB Software

1. Postgres Plus® Enterprise Edition (EE) subscription. In addition to support


for the applicable number of UOM indicated on the Order Form, purchase of
an EE subscription entitles the Customer to use of the following EDB
software:
a. Postgres Plus Advanced Server.
b. Postgres Enterprise Manager (PEM). PEM includes use of the SQL
Profiler.
c. EDB SQL/Protect.
d. EDB Update Monitor.
e. EDB Migration Toolkit.
f. EDB xDB Replication Server in single-master or multi-master
configurations.
g. EDB Failover Manager.
h. EDB Backup and Recovery Tool.

2. Postgres Plus Standard Edition (SE) subscription. In addition to support


for the applicable number of UOM of PostgreSQL indicated on the Order
Form, purchase of a SE subscription entitles the Customer to use of the
following software:
a. Postgres Enterprise Manager (PEM). PEM includes use of the SQL
Profiler.
b. EDB SQL/Protect.
c. EDB Update Monitor.
d. EDB Migration Toolkit.
e. EDB xDB Replication Server in single-master configurations only.
f. EDB xDB Replication Server Multi-master configurations use is only
permitted provided Customer has: (a) purchased the EDB xDB Replication
Server Multi-master Option, and (b) has a valid Postgres Plus Standard
Edition subscription(s) for a total number of UOM not less than the number
of UOM in use on the cluster nodes for which EDB xDB Replication Server
in Multi-master configurations is being purchased.
g. EDB Failover Manager use is only permitted provided Customer has: (a)
purchased the EDB Failover Manager Option and (b) has a valid Postgres
Plus Standard Edition subscription(s) for a total number of UOM not less
than the number of UOM in use on the cluster nodes for which EDB
Failover Manager is being purchased (excluding the Witness Node).

© 2014 EnterpriseDB Corporation. All rights reserved. EnterpriseDB and Page: 6


Postgres Plus are trademarks of EnterpriseDB Corporation.
Version 1.2
EnterpriseDB Licensing Management Guide

h. EDB Backup and Recovery Tool.

3. Postgres Developer Edition subscription. Customer is entitled to install


Postgres Plus Advanced Server and/or PostgreSQL and receive application
development feedback and advice for non-production systems only for the
applicable number of persons specified on the Order Form. Customer's use of
Postgres Plus Advanced Server is governed by the terms of the EnterpriseDB
Limited Use License for the duration of the Developer subscription term.

4. SQL Profiler. For Customers who have paid the applicable subscription fees
for the right to use PEM, EDB also grants a non-exclusive, non-transferable,
limited right to use the source code of the SQL Profiler Plugin.

A customer's full obligations to subscription compliance and other details are


governed by the EnterpriseDB License, Support and Services Agreement.
The remainder of this document is intended to help customers understand
and maintain compliance with respect to Section 1. Scope of License and
Section 9. Verification in the agreement.

Software Licenses

Before explaining how to comply with your EDB subscription entitlements it


important to understand more about the commercial EDB and open source
PostgreSQL software licenses relevant to EDB subscriptions. The licenses
determine what customers will pay for and will not pay for as well as their
obligations when using the software.

PostgreSQL

EDB distributes the community version of the PostgreSQL database server


program under the open source PostgreSQL License.

The PostgreSQL License and Obligations

PostgreSQL is distributed under the PostgreSQL License (see Appendix 1),


which guarantees the free distribution and use of PostgreSQL without fees or
written agreements.

© 2014 EnterpriseDB Corporation. All rights reserved. EnterpriseDB and Page: 7


Postgres Plus are trademarks of EnterpriseDB Corporation.
Version 1.2
EnterpriseDB Licensing Management Guide

EDB is known as a 'packager' of PostgreSQL (both graphical installers and


RPMs) and hosts downloads for the graphical installer and RPM packages on
its website in a freely accessible manner.

Anyone may download the PostgreSQL installers from the EDB website,
install and use the software without paying any fees or engaging in any written
agreements - and use as many installations of the program as desired for as
long as they want.

However, it is important to note that the PostgreSQL license does not prevent
businesses or individuals from charging fees or using written agreements for
PostgreSQL related services such as maintenance and support. These fees
may be based on some measure of a PostgreSQL installation such as
number of installed PostgreSQL program instances, number of physical
servers with PostgreSQL installations, number of hardware sockets used by a
program instance, the number of CPU cores used by or assigned to a
program instance, or some other means.

Source code for PostgreSQL is freely available at the community website:


http://www.postgresql.org/download/. However, under the PostgreSQL
License, there are no obligations for a packager to make source code
available.

In summary, EDB may not charge an up-front fee or require a written


agreement (including website registration) for users to download, install and
use PostgreSQL, but we may levy fees for other products and services we
provide related to PostgreSQL.

Another of EDB's obligations under the PostgreSQL license is to include the


Copyright notice and other text in any derivative works of the software we may
publish or distribute. And in fact we do that with Postgres Plus Advanced
Server.

Postgres Plus Advanced Server and other EDB Software

EDB creates Postgres Plus Advanced Server as a continuously synchronized


derivative work of PostgreSQL and distributes the database program under
commercial licenses as allowed by the PostgreSQL License – or more
accurately as not prevented by the PostgreSQL License. This practice means
that Advanced Server is owned by and is the intellectual property of EDB.

© 2014 EnterpriseDB Corporation. All rights reserved. EnterpriseDB and Page: 8


Postgres Plus are trademarks of EnterpriseDB Corporation.
Version 1.2
EnterpriseDB Licensing Management Guide

EDB distributes Advanced Server as well as other EDB developed software


(e.g. EDB xDB Replication Server and EDB Failover Manager) under a
Limited Use License that allows short term non-production use for evaluation
purposes only. Production use beyond the trial period requires the purchase
of a subscription and execution of a written agreement that includes the
EnterpriseDB License, Support and Services Agreement.

The EDB licenses are summarized below.

EnterpriseDB Limited Use License and Obligations

Anyone may download Postgres Plus Advanced Server from the EDB website
by completing a simple web registration form.

However, Advanced Server is distributed under the EnterpriseDB Limited Use


License, which entitles users to a trial of the software for 60 days. A
subscription is required to continue use beyond the trial period and requires
paying a fee and signing a business agreement.

Advanced Server may not and cannot be installed unless the user accepts the
Limited Use License Agreement in the graphical installer (i.e. click-through
license) or installs the software via an RPM which installs the Limited Use
License along with the program. The graphical installer also installs a copy of
the Limited Use License with the program.

Upon acceptance of the Limited Use license, users acknowledge two key
conditions for use: 1) the user agrees that the program is the property of EDB,
and 2) the user agrees to completely remove the software from their
machines and cease all use of it after a 60 day trial period that begins on the
date of installation.

Even though Advanced Server regularly merges with community PostgreSQL


source code, EDB owns the combined source code and resulting binaries.
EDB is not obligated to share the source, and may restrict and even charge a
fee for its use in binary form.

If your organization needs more than 60 days to complete a trial of Advanced


Server you can inquire about an extension by contacting your local EDB
Account Manager or partner organization.

© 2014 EnterpriseDB Corporation. All rights reserved. EnterpriseDB and Page: 9


Postgres Plus are trademarks of EnterpriseDB Corporation.
Version 1.2
EnterpriseDB Licensing Management Guide

EnterpriseDB License, Support and Services Agreement and


Obligations

Users may use Advanced Server and other EDB software beyond the 60 day
trial period and/or in a production environment, with the purchase of an
appropriate subscription obtainable only by executing a Sales Order with EDB
or qualified business partner that includes and references the EnterpriseDB
License, Support, and Services Agreement.

Under this agreement customers' basic obligations include but are not limited
to:
• Installing EDB software on no more UOM (e.g. sockets, vCores,
Cluster Nodes or Persons) than they are authorized to on the Sales
Order Form based on the EE or SE subscription purchased. If you
have more than one Sales Order executed over time, then you are
entitled to use the qualifying UOM under the applicable durations for
which each was purchased.
• Verifying the quantity of use of EDB software to assure compliance and
reporting the results back to EDB on an annual basis.
• Reporting non-compliance whenever it occurs so that appropriate
actions can be taken to return to compliance (e.g. additional
subscription purchases, uninstall non-compliant instances, etc.).

The table below compares the licensing and pricing characteristics for
PostgreSQL and EDB owned software.

© 2014 EnterpriseDB Corporation. All rights reserved. EnterpriseDB and Page: 10


Postgres Plus are trademarks of EnterpriseDB Corporation.
Version 1.2
EnterpriseDB Licensing Management Guide

Characteristic Open Source EDB Commercial


Postgres Plus Advanced Server
EDB Postgres Enterprise Manager
EDB xDB Replication Server

Covered EDB Failover Manager


PostgreSQL
Software EDB Backup and Recovery Tool
EDB SQL/Protect
EDB Migration Toolkit
EDB Update Monitor
EnterpriseDB Limited Use License
License(s)
and
used for PostgreSQL License
distribution EnterpriseDB License, Support and
Services Agreement
Downloads Free Registration Required
Source Code
Yes No
Available
Include License in any EnterpriseDB ownership,

Key License derivative works, 60 day Trial Use,


Constraints No fees, Purchase required for use beyond Trial,
No agreements Must cease use when subscription ends
Up Front
No No
License Fee
EDB
Maintenance / Optional Included in subscription purchase
Support Fee

Table 1: Database Server Licensing Comparison

The following sections outline how to comply with subscription obligations for
either database server.

Subscription Compliance

In general, to comply with EDB subscription entitlements and licensing or their


organization's internal compliance policies, a customer needs to:

• Understand their business agreement(s) with EDB that describe what


you need to measure and how much you are authorized to use (See

© 2014 EnterpriseDB Corporation. All rights reserved. EnterpriseDB and Page: 11


Postgres Plus are trademarks of EnterpriseDB Corporation.
Version 1.2
EnterpriseDB Licensing Management Guide

Appendix 2).
• Create or maintain processes and artifacts to track your usage of all
software downloaded from the EDB website and communicate their
use to employees, contractors, consultants, and other user populations
in your organization. 1
• Perform annual audits of all your EDB software usage to meet and
confirm your internal compliance efforts, and report the results to EDB
on each anniversary date of your subscription.
• Do not install/use more copies of EDB software than you are
authorized for on all Sales Orders with EDB. If you have more than one
Sales Order executed over time, then you are entitled to install/use the
software under the applicable durations for which each was purchased.
• Do not request support for software installations not covered or
authorized on all Sales Orders with EDB.
• Notify EDB when additional EDB software is installed or used above
the authorized subscription UOM quantities specified on all Sales
Orders.
• Purchase sufficient subscriptions or licenses to cover compliance
shortfalls when they occur or uninstall EDB software that is non-
compliant and notify EDB of the un-installations and/or cease
requesting support for out of compliant software installations.
• Uninstall all copies of EDB software and cease all use of EDB software
and support services at the end of the subscription term if a renewal
has not been purchased.

What to Measure

A pre-requisite to compliance is to know which subscription product you


purchased, how it is measured and what quantities of EDB software the
subscription entitles you to install, use and/or get support for. This information
is available in your EDB business agreements.

Your business agreement(s) with EDB consists of one or more Sales Order
Forms and the EnterpriseDB License, Support and Services Agreement.

The Sales Order specifies which subscription product you purchased, EE or


SE, its UOM, and the quantity of your purchase.

Schedule A of the License, Support and Services Agreement specifies for


1 Creating and maintaining appropriate processes and artifacts for compliance is the responsibility of the
customer and not a topic of discussion in this guide.

© 2014 EnterpriseDB Corporation. All rights reserved. EnterpriseDB and Page: 12


Postgres Plus are trademarks of EnterpriseDB Corporation.
Version 1.2
EnterpriseDB Licensing Management Guide

which software programs your subscription type entitles you to install, use and
receive support.

Before discussing how to report your software usage, a further explanation of


how to measure each UOM is necessary as some software programs are
measured differently.

How to Measure

This section describes the UOM used for EDB software and techniques that
may be used to determine if your organization currently exceeds the number
of subscriptions previously purchased. For convenience, EDB supplies a
spreadsheet to record and report your usage but you may use compliance
reports already in use if desired and send those to EDB.

Sockets for Bare Metal Environments

A socket means an integrated circuit with one or more central processing


units where the software is installed or running. An integrated circuit with more
than one central processing unit core will be considered a single CPU socket.

For EE subscriptions, sockets are used to determine what quantity of


Postgres Plus Advanced Server and other EDB software may be installed,
used, and supported.

For an SE subscription, sockets are used to determine what quantity of


PostgreSQL may be supported and what quantity of EDB software may be
installed, used, and supported.

To calculate sockets, users must determine how many sockets exist on each
machine that has the software installed. The total of all sockets for all
machines with the software installed will be used to determine a purchase
price or usage count.

For example, if 4 machines will have the software installed and 2 of those
machines have 2 CPU sockets each and the other 2 machines have 4 CPU
sockets each, then a total of 12 sockets apply ( 2x2 plus 2x4 = 12).

Then record the total number of cores for each VM in the spreadsheet
“EDB_Product_Usage_companyname.xls”.

© 2014 EnterpriseDB Corporation. All rights reserved. EnterpriseDB and Page: 13


Postgres Plus are trademarks of EnterpriseDB Corporation.
Version 1.2
EnterpriseDB Licensing Management Guide

Depending on the hardware and operating system in use, the methods for
counting sockets may vary. It is the customer's responsibility to understand
their hardware and operating environment and accurately report on the
number of sockets being used including determining the best methods to use
in discovering this type of information.

The guidelines below apply to determining your socket usage.

1. Partial socket counts for a machine may not be used for determining the
total sockets. All sockets for the machine where the software is installed
or running must be counted. Note that you may install multiple instances
of the database (PostgreSQL or Advanced Server) on a machine, however
the sockets for the machine should only be counted once for all the
instances as a group.

2. Sockets must be counted and reported for ALL application usage


categories. This includes but is not limited to any kind of backup server
used for Disaster Recovery or high availability (Cold, Warm, or Hot
standby or Failover server), servers used for testing and servers used for
development.

EDB is ready to help you in reporting your socket usage and encourages you
to contact your Account Manager for assistance. Our team will work with your
staff to determine the most effective way to accurately determine your usage
of sockets for your internal compliance efforts as well as fulfilling your
reporting requirements to EDB.

vCores for Virtualized Environments

vCores means the number of virtual cores or processors assigned to the


virtual operating system environment or virtual machine (VM) where the
software is installed or running.

For EE subscriptions, vCores are used to determine what quantity of Postgres


Plus Advanced Server and other EDB software may be installed, used, and
supported.

For an SE subscription, vCores are used to determine what quantity of


PostgreSQL may be supported and what quantity of EDB software may be
installed, used, and supported.

© 2014 EnterpriseDB Corporation. All rights reserved. EnterpriseDB and Page: 14


Postgres Plus are trademarks of EnterpriseDB Corporation.
Version 1.2
EnterpriseDB Licensing Management Guide

Virtualization systems have utilities to determine this information but they may
be different depending on the vendor, the operating system in use and
whether done via a GUI program or command-line program.

EDB has a core counting script available for you to use in either a Linux or
Windows virtualized environment. For counting vCores for any version of
PostgreSQL or Postgres Plus Advanced Server versions 9.2 and earlier,
contact your Account Manager or Technical Support. For Postgres Plus
Advanced Server versions 9.3 and later, the script is installed with Postgres
Plus Advanced Server in the following locations:

Linux/Solaris Platforms:
====================
INSTALL_DIR/bin/edb_audit.sh

INSTALL_DIR is the directory where the installer was directed to place


Advanced Server.

Windows Platforms:
====================
INSTALL_DIR\bin\edb_audit.bat
edb_audit.vbs

INSTALL_DIR is the directory where the installer was directed to place


Advanced Server and the bat file internally calls the vbs script.

The script should be run in each VM where the software is installed or running
and will return output similar to:

[03/21/14, 11:54:22 AM] FName LName: $ ./edb_audit.sh


CPU type: Intel(R) Xeon(R) CPU L5520 @ 2.27GHz
CPU cores: 4
Memory: 16316176 kB

Then record the total number of vCores for each VM in the spreadsheet
“EDB_Product_Usage_companyname.xls”.

It is the customer's responsibility to accurately report on the number of vCores


being used including determining what utilities are best to use in discovering
this information.

© 2014 EnterpriseDB Corporation. All rights reserved. EnterpriseDB and Page: 15


Postgres Plus are trademarks of EnterpriseDB Corporation.
Version 1.2
EnterpriseDB Licensing Management Guide

If you cannot locate these scripts, contact your Account Manager who can
obtain a Usage Reporting Kit for you.

The guidelines below apply in determining your vCore usage.

1. There is no upper limit to the number of virtual cores counted toward


use on a single piece of hardware. For example, if the hardware
physical processors have a total of 8 physical cores but the
virtualization software creates and uses 12 vCores, then 12 must be
used for determining the purchase price or usage reported to EDB.

2. If you are using Amazon's EC2 infrastructure then report the number of
vCPUs assigned to the instance type you are using along with the
name of each instance type in use (e.g. m1.large or c3.4xlarge) and
total number of instances in use for each type to EDB.

3. In virtualized environments where it is not clear how many vCores or


vCPUs are assigned to the virtual machine on which the software is
installed or running or the number of vCores or vCPUs assigned
changes over time or due to changes in workload, a separate method
for measuring usage must be created and agreed to by the customer
and EDB.

4. vCores must be counted and reported for ALL application usage


categories. This includes but is not limited to any kind of backup server
used for Disaster Recovery or high availability (Cold, Warm, or Hot
standby or Failover server), as well as servers used for playgrounds,
testing or application development.

EDB is ready to help you in reporting your vCore usage and encourages you
to contact your Account Manager for assistance. Our team will work with your
staff to determine the most effective way to accurately determine your usage
of vCores for your internal compliance efforts as well as fulfilling your
reporting requirements to EDB.

UniCores

uniCores means either a physical core or a vCore. For vCores refer to the
section above. Physical cores means all the individual data processing units
packaged together into a single computer processing chip that plugs into a

© 2014 EnterpriseDB Corporation. All rights reserved. EnterpriseDB and Page: 16


Postgres Plus are trademarks of EnterpriseDB Corporation.
Version 1.2
EnterpriseDB Licensing Management Guide

socket where the software is installed or running.

For EE subscriptions, uniCores are used to determine what quantity of


Postgres Plus Advanced Server and other EDB software may be installed,
used, and supported.

For an SE subscription, uniCores are used to determine what quantity of


PostgreSQL may be supported and what quantity of EDB software may be
installed, used, and supported.

To calculate the number of physical cores, first determine the manufacturer


and model number and / or installed processor(s) of the hardware where the
software is installed or running. This information can then be used in
conjunction with the manufacturers hardware specifications to determine the
total number of physical cores in the machine.

For example, if 4 machines will have the software installed and 2 of those
machines have 2 CPU sockets each where chip contains 4 cores and the
other 2 machines have 4 CPU sockets each with chips containing 8 cores,
then a total of 12 cores apply ( 2x2x4 plus 2x4x8 = 16 + 64 = 80).

Then record the total number of uniCores for all machines in the spreadsheet
“EDB_Product_Usage_companyname.xls”.

It is the customer's responsibility to accurately report on the number of


physical cores being used including determining what utilities are best to use
in discovering this information or the hardware and specifications in use.

The guidelines below apply in determining your physical core usage.

1. Partial core counts for a machine may not be used for determining the
total physcial cores. All cores for the machine where the software is
installed or running must be counted. Note that you may install multiple
instances of the database (PostgreSQL or Advanced Server) on a
machine, however the physical cores for the machine should only be
counted once for all the instances as a group.

2. Physical cores must be counted and reported for ALL application


usage categories. This includes but is not limited to any kind of backup
server used for Disaster Recovery or high availability (Cold, Warm, or
Hot standby or Failover server), as well as servers used for
playgrounds, testing or application development.

© 2014 EnterpriseDB Corporation. All rights reserved. EnterpriseDB and Page: 17


Postgres Plus are trademarks of EnterpriseDB Corporation.
Version 1.2
EnterpriseDB Licensing Management Guide

EDB is ready to help you in reporting your uniCore usage and encourages
you to contact your Account Manager for assistance. Our team will work with
your staff to determine the most effective way to accurately determine your
usage of uniCores for your internal compliance efforts as well as fulfilling your
reporting requirements to EDB.

Servers

Server means the computer on which the Software is installed or running.

For EE subscriptions, servers are used to determine what quantity of Postgres


Plus Advanced Server and other EDB software may be installed, used, and
supported.

For an SE subscription, servers are used to determine what quantity of


PostgreSQL may be supported and what quantity of EDB software may be
installed, used, and supported.

To calculate the number of servers, simply count the number of computers


where the software is installed or running.

Then record the total number of servers in the spreadsheet


“EDB_Product_Usage_companyname.xls”.

It is the customer's responsibility to accurately report on the number of servers


being used including determining how best to discover this information.

The guidelines below apply in determining your server usage.

1. Servers must be counted and reported for ALL application usage


categories. This includes but is not limited to any kind of backup server
used for Disaster Recovery or high availability (Cold, Warm, or Hot
standby or Failover server), as well as servers used for playgrounds,
testing or application development.

EDB is ready to help you in reporting your Server usage and encourages you
to contact your Account Manager for assistance. Our team will work with your
staff to determine the most effective way to accurately determine your usage
of uniCores for your internal compliance efforts as well as fulfilling your

© 2014 EnterpriseDB Corporation. All rights reserved. EnterpriseDB and Page: 18


Postgres Plus are trademarks of EnterpriseDB Corporation.
Version 1.2
EnterpriseDB Licensing Management Guide

reporting requirements to EDB.

Cluster Nodes

Cluster nodes only need to be measured for Standard Edition customers that
make the additional purchase of EDB Failover Manager or EDB xDB
Replication Server for Multi-master configurations. Note: single master
configurations of xDB are included in a Standard Edition subscription.

Cluster node means a self-contained or virtual computer that communicates


with other computers over a virtual or physical network to perform a common
task.

To count cluster nodes simply tally the number of physical or virtual machines
where Failover Manager or xDB Replication Server are installed and running.

The guidelines below apply in determining your cluster node usage.

1. Do not count Witness nodes in Failover Manager configurations. If the


Witness is installed on a machine where Failover Manager is running
(a non-recommended configuration) then that node is counted once.

2. Using Failover Manager or xDB Replication Server with PostgreSQL


without a Standard Edition subscription is a violation of EDB's licensing
policies. The software should either be uninstalled or an SE
subscription purchased.

Collecting Usage Information

Prior to collecting your usage data, you will need obtain the
“EDB_Product_Usage_companyname.xls” worksheet to record you
information. If you deploy any EDB software into a private virtualized
environment you may also want the vCore counting scripts referenced above.

Use the spreadsheet provided by EDB to collect and report your software
usage. This format allows EDB to accurately and consistently record your
data from year to year and do so independently of the persons collecting,
reporting, and recording the information at your organization and at EDB.

© 2014 EnterpriseDB Corporation. All rights reserved. EnterpriseDB and Page: 19


Postgres Plus are trademarks of EnterpriseDB Corporation.
Version 1.2
EnterpriseDB Licensing Management Guide

If your current compliance efforts already collect all the data needed as shown
in the “EDB_Product_Usage_companyname .xls”, then you may forward that
to your EDB Account Manager instead.

The spreadsheet has two tabs: Database Usage for reporting your
organizations' consumption of UOMs and Database Usage SAMPLE to assist
you in understanding what a completed sheet may look like.

For illustrative purposes, below is a sample Database Usage report for a


hypothetical company using EDB database products in multiple IT
environments.

Reporting Usage Information to EDB

© 2014 EnterpriseDB Corporation. All rights reserved. EnterpriseDB and Page: 20


Postgres Plus are trademarks of EnterpriseDB Corporation.
Version 1.2
EnterpriseDB Licensing Management Guide

When your report is complete, save the spreadsheet, then rename the file
replacing the text 'companyname' with your organization name and forward
the file by email to your Account Manager or [email protected].

Postgres Enterprise Manager (PEM)

Similar to Advanced Server, EDB creates PEM as a continuously


synchronized derivative work of pgAdmin. pgAdmin's distribution and use is
governed by the PostgreSQL License. The pgAdmin features in PEM provides
its basic database management features such as viewing and creating
database objects. EDB then adds a variety of additional enterprise grade
tools for managing, monitoring, alerting, and tuning large scale Postgres
deployments.

EDB distributes PEM under commercial licenses as allowed by the


PostgreSQL License – or as stated previously as not prevented by the
PostgreSQL License.

Customers who purchase EE or SE subscriptions are entitled to install and


use PEM on all of the database server installations of Advanced Server and
PostgreSQL authorized by their Sales Orders within the restrictions outlined in
the beginning of this guide in the section titled: Subscription Entitlements to
EnterpriseDB Software. Provided this standard is met, no additional reporting
is necessary.

Additional EnterpriseDB Tools and Software

EDB develops additional software and distributes it under commercial


licenses. This software includes:

• EDB Postgres Enterprise Manager


• EDB xDB Replication Server
• EDB Failover Manager
• EDB Backup and Recovery Tool
• EDB SQL/Protect
• EDB Migration Toolkit
• EDB Update Monitor
• EDB SQL Profiler
• EDB index Advisor

© 2014 EnterpriseDB Corporation. All rights reserved. EnterpriseDB and Page: 21


Postgres Plus are trademarks of EnterpriseDB Corporation.
Version 1.2
EnterpriseDB Licensing Management Guide

Customers who purchase EE or SE subscriptions are entitled to install and


use this software on the number of database server installations of Advanced
Server and PostgreSQL authorized by their Sales Orders within the
restrictions outlined in the beginning of this guide in the section named:
Subscription Entitlements to EnterpriseDB Software. Provided this practice is
met, no additional reporting is necessary.

Third Party Add-on Components

Any EDB product may be distributed with 3rd party open source software
components bundled into the distribution. In addition, EDB may make
available separate 3rd party components that the user can install on a
discretionary basis (either from the EDB website, StackBuilder, StackBuilder
Plus or by RPMs).

Software and 3rd party components are distributed under their respective
licenses and installed by each distribution package including the database
server, dependency components it is compiled with, and add-on components
installed by users after installation of the database server.

Appendices

[1] The PostgreSQL License

PostgreSQL is released under the PostgreSQL License, a liberal Open


Source license, similar to the BSD or MIT licenses.

=======================================
PostgreSQL Database Management System
(formerly known as Postgres, then as Postgres95)

Portions Copyright (c) 1996-2014, The PostgreSQL Global Development


Group

Portions Copyright (c) 1994, The Regents of the University of California

Permission to use, copy, modify, and distribute this software and its
documentation for any purpose, without fee, and without a written agreement

© 2014 EnterpriseDB Corporation. All rights reserved. EnterpriseDB and Page: 22


Postgres Plus are trademarks of EnterpriseDB Corporation.
Version 1.2
EnterpriseDB Licensing Management Guide

is hereby granted, provided that the above copyright notice and this
paragraph and the following two paragraphs appear in all copies.

IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO


ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR
CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT
OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF
THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.

THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY


WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS
ON AN "AS IS" BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO
OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES,
ENHANCEMENTS, OR MODIFICATIONS.

[2] EDB Business Agreements

In general the business agreements most customers have with EDB consists
of the following artifacts:

• An EDB Sales Order Form and


• An EnterpriseDB License, Support and Services Agreement

The subscription products ordered, each product's unit of measure, and the
quantity ordered are listed on the first page of the Sales Order Form.

In addition, the first page contains a Terms and Conditions box that
references the License, Support and Services Agreement. To review and
print the agreement, navigate to the URL in the Terms and Conditions box
using your web browser, select the agreement and then print it.

The agreement is also available by selecting the Licensing link on the


Products menu on the EDB home page.

About EnterpriseDB

© 2014 EnterpriseDB Corporation. All rights reserved. EnterpriseDB and Page: 23


Postgres Plus are trademarks of EnterpriseDB Corporation.
Version 1.2
EnterpriseDB Licensing Management Guide

EnterpriseDB is the leading worldwide provider of Postgres software


and services that enable enterprises to reduce their reliance on costly
proprietary solutions and slash their database spend by 80 percent or
more. With powerful performance and security enhancements for
PostgreSQL, sophisticated management tools for global deployments
and Oracle compatibility, EnterpriseDB software supports both mission
and non-mission critical enterprise applications. More than 2,000
enterprises, governments and other organizations worldwide use
EnterpriseDB software, support, training and professional services to
integrate open source software into their existing data infrastructures.
Based in Bedford, MA, EnterpriseDB is backed by top-tier venture
capitalists and strategic investors like Red Hat and IBM. For more
information, please visit: http://www.enterprisedb.com

Sales Inquiries:

[email protected] (US)
[email protected] (Intl)
+1-781-357-3390
+1-877-377-4352

General Inquiries:

[email protected]
[email protected] (APAC)
[email protected] (EMEA)

© 2014 EnterpriseDB Corporation. All rights reserved. EnterpriseDB and Page: 24


Postgres Plus are trademarks of EnterpriseDB Corporation.
Version 1.2

You might also like