Skip to Content

what is Sybase license server

Feb 05 at 11:53 AM


avatar image
Former Member

Do we require acceptance/development servers for Sybase licensing. Can we also use Sybase licensing server for hosting Sybase DB’s as well?

Why do we have Sybase licensing server separately for Sybase while we don’t maintain licensing server separately for SQL server or Oracle?

Does it also require a DR?

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Mark A Parsons Feb 05 at 02:36 PM

ASE needs a license to run ... whether it's a developer license, evaluation license, 'production' license (of which there are many variations), etc.

There are 2 ways to manage licenses:

1 - 'unserved' license: generate (and install) a separate license for each ASE host machine (multiple ASE instances running on a single host can share a license file); in this case each license is hard-coded to work on a single host machine (ie, the host's hostid is embedded within the license) and with the number of cpus on said machine; this license cannot be moved to another host; this license has to be checked-in and regenerated if you change the licensing model, number of cpus, etcif you have a 1,000 machines running ASE then you need to generate (and install) 1,000 separate licenses

2 - 'served' license: generate (and install) a single license file on a 'license server'; while this license file is also hard-coded the host machine, the licenses can be checked out by any ASE that has network access to the license server; in the case of 1,000 machines running ASE, you could have just one license installed on the license server, the license has credentials for the 1,000's of cpus, and the license server checks out/in a virtual license file for each ASE in the network; net result is that you only have to generate/install/manage a single license file

NOTE: There's a bit more to using a license server, eg, setting up redundant license servers (in case one license server is down for some reason), configuring ASE's to access a set of license servers, etc.


Whether you choose to use 'unserved' (aka standalone) or 'served' (requires a license server) licensing is up to you.

If you have a (relatively) small number of ASE hosts then 'unserved' licensing is likely easiest to setup.

If you have a large number of ASE hosts, or you envision needing to regenerate licenses on a regular basis, you may find that 'served' licensing is easier to manage.

10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Feb 06 at 10:05 AM

Hi Mark,

thanks for such an helpful reply. few specific questions below if you clarify.

Do we require acceptance/development servers for Sybase licensing server?
Can we also use Sybase licensing server for hosting Sybase DB’s as well?

Does it also require a DR configuration?

thank you so much

Show 2 Share
10 |10000 characters needed characters left characters exceeded


- licensing server can cover all environments (DEV, QA, ACCEPTANCE, PROD)

- you have almost answered your question. DR (or some altenate host) will be needed, because license server needs to be reachable when you start/shutdown any ASE servers to check in and check out of licenses.

- license server can host any number of data servers, provided there is enough horsepower of CPU, MEM, DISKs etc.

(conceptually treat them as separate applications !)

Just curious what is the actual issue you are trying to tackle ?




As Avinash has stated, a single license server (or pair of license servers if you want some sort of DR/backup solution) can serve your entire network (dev, test, prod); just keep in mind that if someone were to spin up a lot of dev/test ASE instances such that they used up all of your licenses, then your production ASE instances could, at some point, fail to check out a license, net result is that if you don't have a lot of control over the creation of new ASE instances in dev/test then you may want a separate license server(s) for production, ymmv.

You can run your license server on its own host, or co-locate it with other products (ASE, SRS, Oracle, etc). The license server software has a very small footprint operational wise (ie, very little cpu/memory usage). I typically recommend setting up the license server under it's own $SYBASE ... where you could install just the SySAM server and its utilities. ASE, SRS, IQ, etc would then be installed under their own $SYBASE directories, but still be able to check out licenses from the license server.

The license server does not require any sort of DR solution, but if your license server is down for any period of time then some ASE/SRS/IQ/DA instances may not be able to startup without a license (and in many cases the ASE/SRS/IQ/DA instance could actually shutdown if unable to locate a license and the grace period expires). So ... whether you setup a secondary/tertiary license server is up to you to decide. And if you do decide to setup multiple license servers ... make sure they are on different hosts (and preferably different physical hardware/frames if you happen to be running everything on VMs).