Help with connection timeout?

[dogboydelta]

I need help I'm running an SQL query that sometimes works in about 30-45 seconds but usually times out in about 30 seconds.

Here's my connection string, I set the timeout to 180 (3 minutes), and the server is set to 600, but the web page fails and an exception is thrown 'SQL server timeout', within about 30 seconds.

Is there another setting thats not allowing it to try for the full 180 seconds?

"Server=x.x.x.x;Database=mydb;Uid=MyUser;Pwd=MyPass;Connect Timeout=180;" />

[si_the_geek]

There issue may be due to your other code etc, as several database connection technologies have their own time-outs in addition to those provided by the database system.

[dogboydelta]

I'm using .NET 2.0, SQLConnection function.

When I do SqlCn.ConnectionTimeout it displays correctly (180).

Where else might there be a bottleneck that is shortening my timeout?

[MaximilianMayrhofer]

Two possibilities:

1. If the data returned from this connection is part of the basic html of your webpage, i.e. the page isn't finished loading until it has this data, then it could very well be that the browser is timing out because if a page hasn't finished loading within a certain amount of time, most browsers will assume that something must be wrong. If this is the case, then you need to load your page first and then run this connection and update a frame on the page perhaps. You could put a little loading gif.

2. Your ISP is forcibly cutting the connection because it's been open too long.

[wild_bill]

Are you sure it isn't your command object timing out?

[dogboydelta]

Thanks, it was the command object that was timing out (before the actual connection ). Setting the command object itself to the same timeout as the connection object fixed the problem.

[dogboydelta]

This is resolved

(sorry my edit's not working)