Re: ADO executing stored procedures for all calls, bad performance
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Tue, 17 Apr 2007 21:52:06 +0000 (UTC)
Randy Stroede (RandyStroede@xxxxxxxxxxxxxxxxxxxxxxxxx) writes:
Thanks for your response. The connection string is:
Provider=SQLOLEDB.1;Password=ups_test;Persist Security Info=True;User
ID=xyz;Initial Catalog=upsproduction;Data Source=BARKLEY2;Use Procedure
for Prepare=0
OK, you are not turning off connection pooling in the connect string,
that's good. Still you are seeing Audit Login/Logout. I would rather
expect to see an sp_reset_connection, which would indicate that a
connection was reused from the pool.
Unfortunately, since I don't see the code, I don't have much more to add.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- Follow-Ups:
- Re: ADO executing stored procedures for all calls, bad performance
- From: Erland Sommarskog
- Re: ADO executing stored procedures for all calls, bad performance
- References:
- Re: ADO executing stored procedures for all calls, bad performance
- From: Erland Sommarskog
- Re: ADO executing stored procedures for all calls, bad performance
- Prev by Date: Re: ADO executing stored procedures for all calls, bad performance
- Next by Date: Re: ADO executing stored procedures for all calls, bad performance
- Previous by thread: Re: ADO executing stored procedures for all calls, bad performance
- Next by thread: Re: ADO executing stored procedures for all calls, bad performance
- Index(es):
Relevant Pages
|
Loading
