IIS ASP.NET 2.0 Not creating a connection pool nor re-usingconnections

[j.l.robinson]

I need some help!

I have a webapp in ASP.NET 2 running on 2003 R2 that doesn't seem to
want to bring up a connection pool.

When I run a trace on the DB server I can see Audit Logoff and Audit
Logon between query batches, which leads me to believe that this is
occurring.

This is a replacement platform for our current live systems, so I have
just tried to build everything as similarly as possible throughout.

The main difference is that the DB server is now SQL2005 SP2 whereas
before it was SQL2000. I haven't read anything indicating that this
would be the cause, but I am very open to ideas.

The connection string I am using is:

Application Name='Live';pooling=true;Min Pool Size=1;Max Pool
Size=1000;database=DB1;User ID=USER ;Password=PASSWORD;Server=live-
db1;


I cannot find any way to verify information on connection pooling
working, other than by using SP_WHO - which does appear to show an
idle connection or two from the webapp, but like I say, I can see the
connections being torn down and back up every batch from the profiler
trace.

The reason I'm investigating this is that the application is serving
pages incredibly slowly when they have to hit the database, but I've
tried running the query batches directly through MSMS on both the DB
server and App servers, and they are very fast - much faster than when
run via .NET. This connection latancy is the only thing I can put it
down to at the moment.

I'd welcome any insight.


Jon

 

[j.l.robinson]

I need some help!

<snip>

Further to this, it looks like it is creating the connections, as if I
boost the Min Pool Size, I can see the connections sleeping with
sp_who, and can see them established with netstat on the application
server.

However, I still see connections being physically torn down and
brought up with the Audit Logout and Audit Login entries in the
profiler trace - I have been told that's what this indicates, can
anyone confirm?

Jon

 

[j.l.robinson]

On Feb 26, 2:23 pm, (e-mail address removed) wrote:> I need some help!

<snip>

Further to this, it looks like it is creating the connections, as if I
boost the Min Pool Size, I can see the connections sleeping with
sp_who, and can see them established with netstat on the application
server.

However, I still see connections being physically torn down and
brought up with the Audit Logout and Audit Login entries in the
profiler trace - I have been told that's what this indicates, can
anyone confirm?

Jon

SO I was wrong, it was using them, as this article explains:

http://blogs.msdn.com/psssql/archiv...ace-event-change-connection-based-events.aspx

Our performance problem appears to be purely .NET web services being
terribly slow, so it's back to the drawing board to work that out.

Jon