To answer your original question ;-), to use connection pooling effectively with a large number of users, you'll need to change your auditing strategy, to audit in the "application server" layer, rather than at the database layer. Some application servers (eg CICS) could restrict and audit access at this layer.
Cheers, Bob Beauchemin [EMAIL PROTECTED] -----Original Message----- From: ChongQing Xiao [mailto:[EMAIL PROTECTED]] Sent: Friday, May 10, 2002 10:24 AM To: [EMAIL PROTECTED] Subject: [DOTNET] question about connection pool Hi, In ADO.NET, the connection pool will be used if the connection string is the same. This works fine if I can map many different user to the same userID in the Database. But how it will work if I want to distinguish different user in the database (say for audit purpose)? If I map one end user to one database user, can the connection still be reused? Thanks chong You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
