SQL Anywhere Chip License Implementation

[Former Member]

I am trying to help a customer make a purchase decision related to SQL Anywhere for their application.

They are considering purchasing a 2 CPU (12 core) Dell server with Win2012R2 and wish to run an application which will need around 20 user - with 5-8 simultaneously being the usual use.

We are considering a 1 Chip License for this system (SA 12 or 16) and want to know how the Chip License is implemented.

Does it occupy and lock all the threads and cores on that chip, (CPU) rendering the application processes only the use of the other CPU, or does it behave well, utilizing only threads on that chip on an as needed basis leaving it available for other thread activity.

For occasional and low volume activity for one or two databases should the 1 Chip License be sufficient?  How would we know that the Chip limitation is seriously impacting the system's performance.

Also, if down the road we notice that Database throughput is limited, can you upgrade from a 1 chip to a 2 chip License.

Thanks

[former_member207653]

http://dcx.sap.com/index.html#sa160/en/dbadmin/dbserver-s-3165478.html

http://dcx.sap.com/index.html#sa160/en/dbadmin/control-threading-cmdline-running.html

You can find more details about SQL Anywhere threading model in the link above.

It is easy to switch to a higher number of CPUs, if needed. You could also do the opposite, and buy a 2 CPUs license, use one to start with and then go up to 2 when needed (have a look at the second link above please).

About performanace, you should test considering that it sounds like you do not want to dedicate that machine to SQL Anywhere.