What do I have to query to find out which users are logged on?

Roy Lambert

Hi Roy,

> What do I have to query to find out which users are logged on?

Didn't test it, but it should be something like this on the Configuration
database:

SELECT User FROM ServerSessions

No need to put in a WHERE clausule, cause this table only lists logged on
users.

Best regards,
Fons

PS. Look into ServerSessions Table topic for more info.

Fons


Good suggestion but I should have added in fileserver mode.

Roy Lambert

Roy,

<< Good suggestion but I should have added in fileserver mode. >>

You can't do so with a local session, only with remote sessions attached to
an ElevateDB Server.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

>You can't do so with a local session, only with remote sessions attached to
>an ElevateDB Server.

What, in this case makes c/s different from f/s? Since we have to logon to the database (no option) why can't the logon be recorded? I appreciate that not logging off correctly can leave "dangling" logons (lovely image that generates) which will need a utility to clean them up but the same is true of c/s.

Roy Lambert

Roy,

<< What, in this case makes c/s different from f/s? Since we have to logon
to the database (no option) why can't the logon be recorded? I appreciate
that not logging off correctly can leave "dangling" logons (lovely image
that generates) which will need a utility to clean them up but the same is
true of c/s. >>

It's a little more difficult than that.   With the EDB Server, it controls
the logon process, so it knows when logons need to be cleaned-up, removed,
etc.  With file server access, which user knows that the other user's logon,
or their user logon, is invalid ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


>It's a little more difficult than that. With the EDB Server, it controls
>the logon process, so it knows when logons need to be cleaned-up, removed,
>etc.

So you have tools in the server to do this. To my simple mind that means that the engine already has the capability and it's simply the application (the EDBServer) which is managing it.

>With file server access, which user knows that the other user's logon,
>or their user logon, is invalid ?

Isn't that our problem when writing the app? I'm not expecting the engine to do the management. It just makes sense to me that if the capability is there I shouldn't be generating my own tables to do the same thing. Much as I'm moving to ElevateDB's user id & password system.

Roy Lambert

Roy,

<< So you have tools in the server to do this. To my simple mind that means
that the engine already has the capability and it's simply the application
(the EDBServer) which is managing it. >>

Not quite.  It's a state issue, meaning that if you don't have a single
process that can track the state of all sessions, then it isn't possible to
do.  On the server we have that single process.  With file-sharing, local
access we do not.

<< Isn't that our problem when writing the app? >>

It depends upon who you ask.  Once we add such tracking, then most customers
would assume that the tracking in EDB will handle improper disconnections,
which it cannot.

--
Tim Young
Elevate Software
www.elevatesoft.com