Contents IndexClient application settings and deployment Chapter 27.  Introduction to SQL Remote Replication

User's Guide
   Part III. Using SQL Anywhere
     Chapter 26. Client Application Deployment
      Licensing

Compliance with the SQL Anywhere licensing agreement can raise questions when deploying an application that uses only selected components of the SQL Anywhere database management system. The following illustrates two licensing model options for deploying a client application.

Caution
Licensing is governed by the legal terms of the SQL Anywhere license. Information provided in this section is designed solely as a guide to the range of licensing options. All information provided here is superseded by the terms of your license agreement.

Top of page


Concurrent versus per seat licensing

There are primarily two options for deploying SQL Anywhere in a manner that is compliant with the terms of the SQL Anywhere license: Licensing on a concurrent basis and licensing on a per seat basis.

Concurrent licensing allows for distribution of SQL Anywhere network client files throughout an organization, but restricts the number of users able to simultaneously use those network client files to connect to a SQL Anywhere network server. The number of users allowed to connect to the network server at the same time is determined by the terms of the concurrent license.

For example, if a license allows for four users to connect concurrently, only four users can access the SQL Anywhere network server that is the subject of the concurrent license agreement. This is not effected by the number of connections each user generates (i.e. the number of times a user's application connects to the network server or the number of applications a user is running and connecting to a network server), or the number of user systems that have the network client software installed.

As well, the concurrent license is unaffected by the number of databases running on the network server. (Of note, it is not possible to run more than one SQL Anywhere network server on a file or application server.)

Don't count connections, count users
There are various methods for connecting to a SQL Anywhere network server, not all of them using SQL Anywhere network client files. Examples of this would include: an Open Server Gateway connecting multiple Open Client application users to a network server; or, a web server using Dynamo to allow users with Internet browser to send and retrieve data from a network server. In both cases the number of users may far exceed the number of connections to the network server. In the concurrent licensing model, what counts is the number of users simultaneously connecting and using the network server, regardless of what method is used to make that connection.

When a second network server is added to the environment, the licensing agreement for the first network server does not extend to the second server. For example, the first server could have an unlimited concurrent user license and the second server have a license for only four concurrent users.

The per seat licensing model (or "named user licensing" as it is sometimes known), requires that each and every user and server that have SQL Anywhere files installed must be licensed. There is a flat fee for each user and another, separate, flat fee for each installed network server.

The definition of what constitutes a user includes any unique accesser of the network server. A user is not necessarily a person or PC but could also be a device, such as a production line sensor that gathers information.

SQL Anywhere installation CD

The installation CD contains all the files required to install using either licensing models. The CD makes no attempt to restrict what files are removed, or how or where they are distributed.

Top of page


Contents IndexClient application settings and deployment Chapter 27.  Introduction to SQL Remote Replication