Performance

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.
Could you share with me if you have like this article ?Hi
You don't say how you are connecting to the server! For instance ADO has a
close method for disconnecting a connection object
http://msdn.microsoft.com/library/d...r />
lose.asp.
It is not always a good idea to close the connection if you expect to
re-connect again soon after as the time taken to connect can slow down your
application, and creating/destroying the connection takes resources on the
server. This is why things like we applications use connection pooling, so
that a client can re-use an already open connection. This make more effectiv
e
use of the connections that are open and does will help limit the total
number of connections. [url]http://msdn2.microsoft.com/en-us/library/8xx3tyca.aspx[/url
]
HTH
John
"Erencan SADIRODLU" wrote:

> 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 f
or
> this subject on the internet.
> Could you share with me if you have like this article ?
>
>