on 2012 Mar 09 6:38 AM
Request clarification before answering.
AFAIK unique connection numbers are assigned for all connections to all databases started by one server execution instance, and they can be reused only by a different execution instance. Presumably, they can also be reused if the number wraps.
If you're keeping records: For a given database file, CONNECTION_PROPERTY ( 'Number' ) and CONNECTION_PROPERTY ( 'LoginTime' ) suffice to uniquely idenfify a connection.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
See also: How are connection numbers assigned?
Just to add a quote from the v9.0.1 (and 8.0.3) "What's new" section:
Connection IDs start at 1 and are incremented for each new connection to the database server
When the database server is started, each connection to the server is assigned a connection ID, starting with 1, and the connection number is incremented with each new connection to the server. The connection IDs are logged in the -z server output and the LogFile connection parameter output. They are also used by the CONNECTION_PROPERTY, NEXT_CONNECTION, NEXT_DATABASE, and DROP CONNECTION functions, and by request logging.
(Internal/temporary connections used by events and the like are treated differently, as you'll know.)
For older versions, the behaviour was different, but I don't remember...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
50 | |
9 | |
8 | |
6 | |
5 | |
5 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.