Server Side Process Not Killed by Application | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Server Side Process Not Killed by Application

Hi,<br /><br />My server is SQL SERVER 2000 and it is in different place and for client I developed one application using C#. What this application is does just connect database do some query, do some call procedure and some other stub.<br /><br />Now, problem is when I start my application and in that application I create 9 connection to different database and after that I close this connection using this code<br /><br />m_SCnn = new SqlConnection("Data Source=test;UID=test<img src=’/community/emoticons/emotion-4.gif’ alt=’;P’ />WD=test;Initial Catalog=MyDB");<br /><br />m_SCnn.Open();<br /><br />after doing this I will close this connection using<br /><br />m_SCnn.Close();<br />m_SCnn.Dispose();<br /><br />but after doing this still all process is on the server and what happend If I close my C# application and immediatly it kill all process on the server.<br /><br />So my question<br />==============<br /><br />Is there any way to close OR kill all process in the server after doing m_SCnn.Close() command. What I have to use.<br /><br />Thanks<br />Chandresh<br /><br /><br /><br />Thanks<br />Chandresh
I think the process will not be killed immediately after closing the connection. SQL Server will keep it alive (but idle) for a little while so that it can be reused if another connection needs it.
Thank you
Are you using Connection pooling? Satya SKJ
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.