"Erencan SAÐIROÐLU" <erenc***@hotmail.com> wrote in message
news:uaeY1jc%23GHA.5092@TK2MSFTNGP04.phx.gbl...
> Hi to all,
> I know that we should close sql connection when it's complete its job for
> performance and sql server's resources. But i can't find article or text
> for
> this subject on the internet. Or i know not true?
> Could you share with me if you have like this article ?
>

"Brian Pursley" <b*@cinlogic.com> wrote in message
news:eS5EPNj%23GHA.4800@TK2MSFTNGP05.phx.gbl...
> For internet applications you should use connection pooling, and close
> your connection as soon as you are finished.  The provider (or driver)
> will automatically keep the connection open for you and re-use it if you
> open another connection using the same connection string within the
> connection pool timeout period.  Just search for "SQL Server connection
> pooling" and I'm sure you will find more information
>
> "Erencan SAÐIROÐLU" <erenc***@hotmail.com> wrote in message
> news:uaeY1jc%23GHA.5092@TK2MSFTNGP04.phx.gbl...
>> Hi to all,
>> I know that we should close sql connection when it's complete its job for
>> performance and sql server's resources. But i can't find article or text
>> for
>> this subject on the internet. Or i know not true?
>> Could you share with me if you have like this article ?
>>
>
>