TimeOut Expired

[MSR]

Hi,
I have a query that takes 1 min 50 secs to execute in Query analyser
(SQL Server 2000).
When i execute this query from vb using ADO i get the 'Timeout
Expired' error.
I have tried setting the Connection.Timeout property to the ADO
connection object but it doesn't work.
Can anybody tell me how can i set the Connection.Timeout property in
both vb and SQL Server.

Thanks in advance

[Steve Thorpe]

Use the CommandTimeout property

e.g.
cnn.CommandTimeout = 300

set it after you open a connection.

Also any command objects you create will not inherit this property so add
objADOCmd.CommandTimeout = 300 on each command object

Steve

"MSR" <ms*****@hotmail.com> wrote in message
news:9c**************************@posting.google.c om...

Hi,
I have a query that takes 1 min 50 secs to execute in Query analyser
(SQL Server 2000).
When i execute this query from vb using ADO i get the 'Timeout
Expired' error.
I have tried setting the Connection.Timeout property to the ADO
connection object but it doesn't work.
Can anybody tell me how can i set the Connection.Timeout property in
both vb and SQL Server.

Thanks in advance

[Dave Pylatuk]

My two cents.

We are have had the same problem many times in SQL Server2000.

In our case setting the timeout property made absolutely no difference.
We found two things that caused this error.

1. Flakey or slow network connection.
2. Rebuild and Reindex all indexes on large/heavily used tables.

For us it has always been one of these two things.

"MSR" <ms*****@hotmail.com> wrote in message
news:9c**************************@posting.google.c om...

Hi,
I have a query that takes 1 min 50 secs to execute in Query analyser
(SQL Server 2000).
When i execute this query from vb using ADO i get the 'Timeout
Expired' error.
I have tried setting the Connection.Timeout property to the ADO
connection object but it doesn't work.
Can anybody tell me how can i set the Connection.Timeout property in
both vb and SQL Server.

Thanks in advance

[Ellen K.]

The Timeout property of the Connection object is not the problem, that
only controls how long you get to make the connection. Check the
Timeout property of the Command object. Watch out, there are two of
these, the CommandTimeout property of the Connection object, and the
CommanTimeout property of the Command object. The second one is the
one to check.

On Tue, 9 Sep 2003 13:31:51 -0400, "Dave Pylatuk"
<da***@centurysystems.net> wrote:

My two cents.

We are have had the same problem many times in SQL Server2000.

In our case setting the timeout property made absolutely no difference.
We found two things that caused this error.

1. Flakey or slow network connection.
2. Rebuild and Reindex all indexes on large/heavily used tables.

For us it has always been one of these two things.

"MSR" <ms*****@hotmail.com> wrote in message
news:9c**************************@posting.google. com...

Hi,
I have a query that takes 1 min 50 secs to execute in Query analyser
(SQL Server 2000).
When i execute this query from vb using ADO i get the 'Timeout
Expired' error.
I have tried setting the Connection.Timeout property to the ADO
connection object but it doesn't work.
Can anybody tell me how can i set the Connection.Timeout property in
both vb and SQL Server.

Thanks in advance