The forum will experience an outage sometime between February 10 at 7:00pm EST and February 12 at 11:59 EST for installation of security updates. The actual time and duration of the outage are unknown but attempts will be made to minimize the downtime. We apologize for any inconvenience.

Hi

We have licenses for the SQL Anywhere 17 workgroup edition. As I read here: link:http://scn.sap.com/docs/DOC-54533 the workgroup edition is now renamed Edge and I see in the table that it's supporting 8 cores. The workgroup edition had only 2 cores with the license. SELECT PROPERTY ('NumPhysicalProcessorsUsed') shows still only 2 for the SQL Anywhere version 17.0.4. As there are more than 2 processors available on the server, how and can I get the current database to support the 8 cores?

Regards, Robert

asked 27 Jul '16, 08:04

robert's gravatar image

robert
543253345
accept rate: 0%

edited 27 Jul '16, 08:06

The workgroup edition had only 2 cores with the license.

AFAIK, up to v16, the counting is related to chips/sockets/processors, not cores, so the v12 / v16 Workgroup Editions allow for two processors, and as many cores/threads as available on those two cores.

(I share your impression that the switch to core-based licensing in v17 seems to ingore the fact that the allowed 8 cores for an Edge Edition may be supplied by more than 2 processors, when using a per-seat license....)

(28 Jul '16, 10:16) Volker Barth

It just might be as easy as [cough] telling the Workgroup edition that it is now the Edge edition...

[WHISPER] That seems to work for the Developer Edition. [/WHISPER]

"%SQLANY17%\bin64\dblic.exe" -o dblic17_log.txt^
  -l Core^
  -u 8^
  "%SQLANY17%\bin64\dbsrv17.lic"

SQL Anywhere Server Licensing Utility Version 17.0.4.2053
License applied successfully.
Developer Edition
Add-on: High Availability
Add-on: In-Memory mode
Add-on: Scale-out Nodes
Licensed cores: 8
User: Developer Edition
Company: Restricted Use
Install key: 
permanent link

answered 27 Jul '16, 08:38

Breck%20Carter's gravatar image

Breck Carter
26.6k418575824
accept rate: 21%

edited 27 Jul '16, 08:44

HI Breck

Unfortunately, your whisper is not loud enough for me ;-) I don't get which one the essential dblic option is, as I have a per-seat license and -l is the license type and -u number of users. I seem to miss the good part ...

(27 Jul '16, 08:50) robert
Replies hidden

Did you try it?

The -l changes the license type from Perseat to Core, and the -u specifies the number of cores :)

At least it did for the Developers Edition, which originally looked like this...

SQL Anywhere Server Licensing Utility Version 17.0.4.2053
License read successfully.
Developer Edition
Add-on: High Availability
Add-on: In-Memory mode
Add-on: Scale-out Nodes
Licensed nodes: 3
User: Developer Edition
Company: Restricted Use
Install key: 
(27 Jul '16, 10:24) Breck Carter
1

I tried it and it works like in your example. But I think I have now also changed the license type from per-seat to core. As I have per-seat licenses, I think it's commercially spoken not correct to run the database serve now per cores, correct? Is there a way to keep the license type and change the maximum number of cores used by the database server? I think thats what the SQL Anywhere Editions sheet says.

Regards, Robert

(28 Jul '16, 08:48) robert
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×8

question asked: 27 Jul '16, 08:04

question was seen: 208 times

last updated: 28 Jul '16, 10:24