Silo - Tips - Enterprisedb Licensing Management Guide
Silo - Tips - 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
Overview
The bundling of commercial and open source software has multiple beneficial
effects for customers:
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.
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.
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.
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.
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.
Software Licenses
PostgreSQL
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.
Anyone may download Postgres Plus Advanced Server from the EDB website
by completing a simple web registration form.
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.
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.
The following sections outline how to comply with subscription obligations for
either database server.
Subscription Compliance
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
Your business agreement(s) with EDB consists of one or more Sales Order
Forms and the EnterpriseDB License, Support and Services Agreement.
which software programs your subscription type entitles you to install, use and
receive support.
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.
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”.
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.
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.
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.
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
Windows Platforms:
====================
INSTALL_DIR\bin\edb_audit.bat
edb_audit.vbs
The script should be run in each VM where the software is installed or running
and will return output similar to:
Then record the total number of vCores for each VM in the spreadsheet
“EDB_Product_Usage_companyname.xls”.
If you cannot locate these scripts, contact your Account Manager who can
obtain a Usage Reporting Kit for you.
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.
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
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”.
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.
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
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
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.
To count cluster nodes simply tally the number of physical or virtual machines
where Failover Manager or xDB Replication Server are installed and running.
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.
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.
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].
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
=======================================
PostgreSQL Database Management System
(formerly known as Postgres, then as Postgres95)
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose, without fee, and without a written agreement
is hereby granted, provided that the above copyright notice and this
paragraph and the following two paragraphs appear in all copies.
In general the business agreements most customers have with EDB consists
of the following artifacts:
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.
About EnterpriseDB
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)