> I am using closed system, which can execute store procedure via jdbc
> interface.
> The problem is that, after every execution of store procedure exist
> process in sleeping state with "awaiting command" command.
> Is exist any option to manually, in code of my store procedure, say,
> that process should be closed.
> May be exist parametr with timeout for closing sleeping processes?

On Jun 5, 1:30 am, Erland Sommarskog <esq...@sommarskog.se> wrote:
> (is_vl...@hotmail.com) writes:
> > I am using closed system, which can execute store procedure via jdbc
> > interface.
> > The problem is that, after every execution of store procedure exist
> > process in sleeping state with "awaiting command" command.
> > Is exist any option to manually, in code of my store procedure, say,
> > that process should be closed.
> > May be exist parametr with timeout for closing sleeping processes?
>
> I don't know about JDBC, but most modern client API has this features
> known as connection pooling. This means that when the application
> closes a connection, the API lingers to the physical connection for
> some time, typically 60 seconds, and if there is a requestion for a new
> connection in this time frame for a connection with the same properties,
> the connection is reused.
>
> The reason for this design is efficiency. By avoiding actual connection
> sequences, the load on SQL Server is reduced.
>
> --
> Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se
>
> Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
> Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

> the problem is that every call to sp create a new process and not use
> connection from a pool.

> so as temporary solution I want to manual close connection from store
> procedure.
> is exist any solution?