Sybase iAnywhere SQL AAnywhere Mobile and Embedded Database

Rows and Columns


SQL Anywhere perspective on technology

header image

Licensing SQL Anywhere in Virtualized Environments

November 6th, 2008 · No Comments

One of SQL Anywhere’s strengths is its support for a wide variety of platforms. With the increasing use of virtualization to maximize hardware utilization, many existing and potential customers have asked what exactly is supported in terms of virtualization.
Our basic position on support for virtualization is that we will support our customers running SQL Anywhere on any OS in a virtual environment providing that OS is listed as supported (see link above). To ease tracking and diagnosis for technical support issues, our support team will sometimes ask customers to reproduce issues outside of the VM environment, in order to remove as many possible contributing factors when diagnosing a problem.
If we do run into issues that are directly caused by running in a virtual environment, we are willing to work with our customers and the virtualization vendor to diagnose and resolve these issues.
Once assured that we do indeed support virtualization, the next logical question surrounds licensing. How is SQL Anywhere licensed in a virtual environment. The answer to that question is simple. From a licensing perspective, we treat each running VM as an independant piece of hardware, so users must be licensed for each virtual machine on which SQL Anywhere is running. Here are a couple of examples that will hopefully clarify things.
In reading the examples, note that SQL Anywhere has 2 basic licensing options: per CPU on the server, or per-client seat. For details on licensing options related to SQL Anywhere, e-mail us at or call us at 1-866-924-0521. If you are outside North America, find the office nearest you here

Example 1

This configuration shows a server machine with 1 CPU with 1 core. Two virtual environments (VEs) have been created. Two instances of SQL Anywhere are running on one VE and one instances is running on the other.
VMLicensingExample1Core
Licensing
CPU based – Each VE accessing a physical processor requires a license. There are 2 VEs. Each licensed VE can permit an unlimited number of instances. Therefore, 2 CPU licenses are required.
Server & Seat – Each VE running a database server needs a database server license. There are 2 VEs. Each licensed VE can permit an unlimited number of instances. Therefore, 2 database server licenses are required.

Example 2

This configuration shows a box with 2 dual core CPUs. Two VEs have been created. Two instances of SQL Anywhere are running on one VE and one instance is running on the other.
SAVMExample2CPU2Core
Licensing
CPU based – Each VE accessing a physical processor requires a license. There are 2 VEs each accessing 2 processors. Therefore, 4 CPU licenses are required.
Server & Seat – Each VE running a database server needs a database server license. There are 2 VEs. Therefore, 2 database server licenses are required.

Example 3

This configuration shows a box with 4 CPUs. Five VEs have been created. Four VEs are running SQL Anywhere accessing a single CPU. The Fifth VE is running SQL Anywhere accessing two CPUs.
SAVMExample4CPU1Core
Licensing
CPU based – Each VE accessing a physical processor requires a license. There are 4 VEs accessing 1 processor and 1 VE accessing 2 processors. Therefore, 6 CPU licenses are required.
Server & Seat – Each VE running a database server needs a database server license. There are 5 VEs. Therefore, 5 database server licenses are required.

Be Sociable, Share!

Tags: SQL Anywhere