B
Brian Wotherspoon
Hi All,
I'm running an online transaction processing system using an SQL Server
2000 SP3 database server and an online application server.
I seem to be hitting some performace issues I believe be related to
connections. Certainly I've tracked it to a single point in the
processing.
Running a profiler trace indicates that the stored procedure and SQL
statements within have no performance issues, indexes are all fine
according to the execution plan.
However the Audit Logout line that appears after each call to the
procedure has a duration of several hundred ms, even though the
procedure executes in a max of 16ms.
Does this indicate that performance is being hit by the overhead of
creating and destroying connections? I understood that connection
pooling, which is enabled as far as I can tell, was supposed to prevent
these kind of problems.
Any help is very much appreciated.
Brian.
I'm running an online transaction processing system using an SQL Server
2000 SP3 database server and an online application server.
I seem to be hitting some performace issues I believe be related to
connections. Certainly I've tracked it to a single point in the
processing.
Running a profiler trace indicates that the stored procedure and SQL
statements within have no performance issues, indexes are all fine
according to the execution plan.
However the Audit Logout line that appears after each call to the
procedure has a duration of several hundred ms, even though the
procedure executes in a max of 16ms.
Does this indicate that performance is being hit by the overhead of
creating and destroying connections? I understood that connection
pooling, which is enabled as far as I can tell, was supposed to prevent
these kind of problems.
Any help is very much appreciated.
Brian.