Re: connection in connection pool with pooling=false
From: Kevin Yu [MSFT] (v-kevy_at_online.microsoft.com)
Date: 06/22/04
- Next message: William Ryan eMVP: "Re: Sqlcommand object gives command timeout"
- Previous message: Wells Caughey: "Re: Time out expired"
- In reply to: Jason Collins: "Re: connection in connection pool with pooling=false"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 22 Jun 2004 12:21:55 GMT
Hi Jason,
Thanks for your additional information!
Based on my research, SqlXmlCommand uses connection pooling by default as
ADO does. That might be the cause that there is always a connection remain
to the server.
Since SqlXml uses OleDb provider for SQL Server to connection, we cannot
use pooling=false to disable pooling. Instead, we can add "OLE DB
Services=-4;" in the connection string to disable connection pooling.
Please try it in your application to see if it works. HTH.
Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
- Next message: William Ryan eMVP: "Re: Sqlcommand object gives command timeout"
- Previous message: Wells Caughey: "Re: Time out expired"
- In reply to: Jason Collins: "Re: connection in connection pool with pooling=false"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|