SqlCommand.CommandTimeout really works?

  • Thread starter Thread starter Cristian Ionita
  • Start date Start date
C

Cristian Ionita

I use SqlCommand to run a query against a SQL Server database in ASP.NET
and I need to abort the query if it takes more than a specified time. I've
tried to
use CommandTimeout property but it doesn't seem to work. Digging in
System.Data.dll
with ILDASM it appears that the property isn't used anywhere.
Is this true or I'm missing something? If it's true, then there is any other
easy way
to acomplish this task?


Cristian IONITA
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

SqlCommand.CommandTimeout seems to have no effect 1
Fill method ignoring CommandTimeout value 3
Possible Workarounds: "General Network Error" using TCP/IP with .CommandTimeout = 0 0
Setting Command Timeout globally in Asp.Net / windows applications... 2
BeginTransaction causes command to ignore timeout 1
Set an SQLCommand timeout default application wide? 7
SQLCommand Timeout expires in code but not in Query Analyzer 4
odbcdataadapter.update "concurrency exception" due to fields number? 2

Back
Top