Connection Pooling with the .NET Provider on IIS
Posted in 2009
Topics: Performance & Tuning, Connectivity: ODBC / JDBC / .NET
I have developed an Intranet IIS web application that is configured to use Windows Authentication against our Active Directory. The sites run with identity impersonation so all connections against the database SHOULD use the the credentials of the original user who requested the web page. Initially this appeared to be working correctly. If you have infrequent visitors or many hits from the same user everything appears fine however if you get visits from multiple identities in quick succession the second and third connections re-use the credentials of the first connection. Adding "Pooling=False" to the Connection string resolves this issue, however I fear we will run into performance issues when we deploy the system to our live servers. Has anyone seen this issue before? Is this a bug in the Provider? I have never seen this with other (SqlClient) .NET Data Providers.
Hi, Can you post your note in this forum. http://www.ibm.com/developerworks/forums/dw_forum.jsp?forum=467&start=0 This is a specific .NET forum and you will definitely get a response there. VG.