Databases
StackOverflow2013
Postsdbo
PO.net SqlCommandTimeOut and the connection pool
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO.net SqlCommandTimeOut and the connection pool
    primarykey
    data
    text
    <p>Let's say we are executing lots of different sql command, and the <code>SqlCommand.CommandTimeout</code> was leave with default value 30 seconds. </p> <p>And let's just assume some of those sql command are just long query and we might get the timeout exception. </p> <p>Correct me if I'm wrong, this exception was just cause .Net do not want to wait anymore, but if we are using connection pool, this connection might be remain open, so will that sql statement might still running on the SQL server side? Or there are some hidden communication between those system to suddenly stop it no matter we are using connection pool or not? </p> <p>Just want to know what's the mechanism and would it effect the SQL server performance. I mean if the query is really long such as take 10 mins to run if it's still running it might just slow down the server unnecessary as no one can get the result.</p> <p><strong>UPDATE</strong></p> <p>So here I'm asking about the connection pool specifically, it's definitely that the code will close the connection with exception handling, or we can just assume that are using code which is a pattern preferred named by @dash here. The problem is if I call the Close() or Dispose() method on that SqlConnection object, it is returned to the connection pool, it's not physically close it.</p> <p>I'm asking when it's returned to pool, would that long query still running on SQL Server side. And if possible, how to avoid that.</p> <p><strong>UPDATE again</strong></p> <p>Thanks for @dash mentioning that about database transaction, yes a rollback will make it wait and we are not closing the connection and return it to the pool yet. So what if it's just a long select query or an update but just one individual update without any database transaction involved? And specifically I want to know is there a way that we can tell SQL Server that I do not need the result now please stop running it?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USSimon Wang
    1. USSimon Wang
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PO.net SqlCommandTimeOut and the connection pool
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO.net SqlCommandTimeOut and the connection pool
      1. USSimon Wang
      1. VTBountyStart
    3. VO
      singulars
      1. PO.net SqlCommandTimeOut and the connection pool
      1. This table or related slice is empty.
      1. VTUpMod
    1. CONo; there is no way - you can KILL the running process on SQL Server, but you really just need to let SQL Server manage what it's doing. As with everything, if you choose to run a query that degrades the performance of the server, then that's your choice :-)
      singulars
      1. PO.net SqlCommandTimeOut and the connection pool
      1. USdash
    2. COYou can kill the running process on SQL Server by using the SQL KILL command. KILL SPID and to get the SPID you could use SELECT @@SPID or get all of the current processes from one of the sys tables.
      singulars
      1. PO.net SqlCommandTimeOut and the connection pool
      1. USDarren
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload