on 2013 Dec 31 5:14 PM
Testing seems to indicated that a unique connection number is assigned to each connection established on each instance of any database started on one instance of a SQL Anywhere server.
In other words, connections on two different databases started on the same server instance will get different connection numbers. If one of the databases is stopped and started, new connections to that database will get different connection numbers.
Is that true?
Request clarification before answering.
Correct. Connection numbers are monotonically increasing numbers and are guaranteed to be unique across the entire server instance (and are independent of the database). Note that once the max connection number is reached (which is some number less than 2^32) the 'base number' (of the sequence) wraps back to 1 but the server will still guarantee that the number is unique when it assigns a number to a new connection (i.e. it verifies that a connection with the number does not already exist).
HTH
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, that is correct.
FWIW, the uniqueness is documented in the docs:
When a user connects to a database, the database server assigns the user's connection a unique connection ID. For each new connection to the database server, the server increments the connection ID value by one.
AFAIK, that particular numbering scheme has been introduced in 8.0.3/9.0.1 - before that, the IDs did not start with 1 after a database server start.
User | Count |
---|---|
33 | |
22 | |
17 | |
8 | |
5 | |
5 | |
4 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.