Giving Database Connections A Name

[DRDuquette]

I know that the CF Administrator manages the connections to the database (in my
case SQLserver) and maintains a limited number of connections to the database
that all users use.

My question is: Is there a way to uniquely identify each connection that is,
user workstation through CF to the database? I want to better manage the users
on the database when I run sp_who. Right now I have one ODBC connection for
all users and the CF Administrator opens several connections to the database
depending on traffic however, they all have the same user name. In addition, I
do not want to setup a separate ODBC connection for each user.

Any help with this will be appreciated.

Don

[philh]

You've pretty much boxed yourself into a corner. Connection pooling is the
defacto method. CF doesn't handle Windows authentication from the user because
of the hop/impersonation issue. The only thing you can do is write some
session start code that discovers the connection SPID and inserts it into a
table with the user name.

Good luck.

[DRDuquette]

Thanks, Phil. I think it would be easier to simply create an ODBC connection
for each user in my case since the number of users is less than 30. Do you
know how most applications handle this situation?

Thanks,
Don

[philh]

I suppose with a small number of users you can get away with the ODBC
connections.

I wonder what your real need is. Most Web application talk to the DB through
a pooled connection (excepting your unique connections as above). Judicious
application of connection and session timeouts should minimize any performance
impacts, which, with 30 users, is practically negligible. You can handle
identity management through cookies and/or, in the case of an Intranet,
domain-authenticated users. If you're after who did what when, that's best
done in an Intranet scenario using triggers and the auth_user info.

My $.02