• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 15312
  • Last Modified:

How to set a recordset.open timeout???

I have an application that generates queries dinamicaly and some of them are huge. I'd like to set a time limit for the queries.

I'm using ADO recordsets to run the queries in SQL 7. I've tried to set the CommandTimeout property for the connection i use in the Recordset.Open Method, but it didn't work.

Here is my test:

    Set con = CreateObject("ADODB.Connection")
    Set rs = CreateObject("ADODB.Recordset")
   
    con.CommandTimeout = 5
    con.CursorLocation = adUseClient
    con.Open "Provider=SQLOLEDB.1;Password=*****;Persist Security Info=True;User ID=USR;Initial Catalog=DB;Data Source=Server"

    rs.Open "select * from table", con, adOpenStatic, adLockReadOnly

The query runs for several seconds, even if i have set the CommandTimeout to 5 seconds.
0
RobertoTY
Asked:
RobertoTY
1 Solution
 
aranaCommented:
i think the commandtimeout property is for settin a timeout before command STARTS executing (due to network traffic or slow connection)
but if the query already began to run, then the commandtimeout does not apply.
0
 
Anthony PerkinsCommented:
The Connection CommandTimeout property only affects the Connection Execute method.  So that probably explains the reason it has no effect.

One solution would be to use a Stored Prodecure and set the CommandTimeout property for the Command object.

Hope this helps,

Anthony
0
 
RobertoTYAuthor Commented:
I think that even using the connection.execute method, I face the same problem. I've made the following test and the query remains running even after the time estipulated for timeout.

    Dim con As ADODB.Connection
    Dim rs As ADODB.Recordset

    Set con = CreateObject("ADODB.Connection")
    con.CursorLocation = adUseClient
    con.Open "Provider=SQLOLEDB.1;Password=****;Persist Security Info=True;User ID=USR;Initial Catalog=DB;Data Source=SRV"
    con.CommandTimeout = 3

    Set rs = con.Execute("select * from TABLE")


I think there must be another way to set a timeout for these queries, since this property should be for something like an Idle timeout.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
Anthony PerkinsCommented:
Roberto,

I could be wrong about this, but I believe the Connection CommandTimeout property needs to be specified prior to the Open.

Have you tried this and if so does it have any effect?

Suerte,
Anthony
0
 
RobertoTYAuthor Commented:
Extracted from msdn:

On a Connection object, the CommandTimeout property remains read/write after the Connection is opened.

It doesn't work either.

I discovered that recordset has a dinamic property:
Command Time Out
But it didn't work as well.

0
 
RobertoTYAuthor Commented:
Extracted from msdn:

On a Connection object, the CommandTimeout property remains read/write after the Connection is opened.

It doesn't work either.

I discovered that recordset has a dinamic property:
Command Time Out
But it didn't work as well.

0
 
Anthony PerkinsCommented:
Roberto,

Yes, I know I spoke too soon:  I checked the CommandTimeout and in my case it works as advertised, placed prior to the Connection open or after.  Basically it triggers a Timeout expired (-2147217871).

I am not sure why it is not working in your case.  The only other thing I can suggest is that you try out the CommandTimeout property of the Command object.  Perhaps you will have better luck.

Anthony
0
 
RobertoTYAuthor Commented:
acperkins,

I am very curious to see the code you said that works for you. Can you send me the code sample you used? Maybe i'm doing something wrong.
0
 
Anthony PerkinsCommented:
I very much doubt my code is any different to yours.  By the way I am using ADO 2.5.

Dim cn As ADODB.Connection
Dim rs As ADODB.Recordset
Dim SQL As String

SQL = "SELECT ... " 'SQL statement that is guaranteed to take longer than 1 second

'Next line was originally Set cn = New ADODB.Connection
'but changed it to match your code
Set cn = CreateObject("ADODB.Connection")
With cn
   '.CommandTimeout = 1
   .ConnectionString = "Provider=SQLOLEDB.1;Password=*****;Persist Security Info=True;User ID=USR;Initial Catalog=DB;Data Source=SQLServer"
   .Open
   .CommandTimeout = 1
   Set rs = .Execute(SQL, , adCmdText)
   rs.Close
   .Close
End With

Set rs = Nothing
Set cn = Nothing
0
 
DanRollinsCommented:
Hi RobertoTY,
It appears that you have forgotten this question. I will ask Community Support to close it unless you finalize it within 7 days. I will suggest to:

    Accept acperkins@devx's comment(s) as an answer.

RobertoTY, if you think your question was not answered at all or if you need help, you can simply post a new comment here.  Community Support moderators will follow up.

EXPERTS: If you disagree with that recommendation, please post an explanatory comment.
==========
DanRollins -- EE database cleanup volunteer
0
 
Computer101Commented:
Comment from expert accepted as expert

Computer101
E-E Moderator
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now