Who needs a license for kdb+?¶
Everyone. All use of kdb+ is governed by a license.
Commercial versions of kdb+ also need a license key file (
kc.lic for kdb+ on demand) to run.
Free, non-commercial, 32-bit kdb+¶
Use of the free, non-commercial, 32-bit kdb+ distribution, is licenced by the terms and conditions on the download page.
When you start kdb+ you will see on the banner that your license has no expiry date.
KDB+ 3.5 2017.06.15 Copyright (C) 1993-2017 Kx Systems m32/ 4()core 8192MB sjt mint.local 192.168.0.39 NONEXPIRE Welcome to kdb+ 32bit edition
If you have a commercial distribution of kdb+, it will abort without a suitable license key file
kc.lic. For example, with no license key file:
KDB+ 3.5 2017.06.15 Copyright (C) 1993-2017 Kx Systems m64/ 2()core 8192MB tom mb13.local 192.168.1.44 'k4.lic
Kdb+ signals the error
'k4.lic and aborts.
Obtaining a license key file¶
Each Kx customer designates to email@example.com one technical person as the Designated Contact for issues with kdb+, managing licenses and downloading software.
The banner at the top of the aborted q session above contains machine-configuration information but no license information.
The Designated Contact sends a copy of the banner to firstname.lastname@example.org to receive a license file in return.
Save a copy of the license file in the
QHOME folder. Restart kdb+ and note the change in the banner.
KDB+ 3.5 2017.06.15 Copyright (C) 1993-2017 Kx Systems m64/ 2()core 8192MB tom mb13.local 192.168.1.44 EXPIRE 2018.05.15 email@example.com #400 q)til 6 0 1 2 3 4 5 q)
Note the license number (
#400 in the example) and quote it in any correspondence about the license.
Keeping the license key file elsewhere¶
The default location for the license key file is the
QHOME folder. You do not have to keep the license there. You can use the environment variable
QLIC to specify a different filepath.
Folder not file
QLIC points to a folder, not a file. For example,
If the license is for fewer cores than the total number on the machine, the number of cores available to kdb+ must be restricted with OS programs, or kdb+ will signal
'cores and abort.
Designated Contacts should send license questions to firstname.lastname@example.org.
Emergency failover licenses
In case of an emergency, such as a hardware or infrastructure failure that renders your license key file unusable, the Designated Contact can email email@example.com to request a temporary failover license to allow use of a different machine or IP address.