Timeout expired

[JefB]

I am using FrontPage 2k to display online database results from SQL 7 queries.
The queries are fed criteria from fields set up by the database wizard (ie Protocol = xxx)
Somedays everything works fine but there are days like today when the queries will work for all but one protocol and I'll get:

"Database Results Error
Description: [Microsoft][ODBC SQL Server Driver]Timeout expired
Number: -2147217871 (0x80040E31)
Source: Microsoft OLE DB Provider for ODBC Drivers"

More frustrating is that tomorrow, a different protocol will timeout.

Any suggestions on what to look for would be greatly apreciated.

Jef

 

[JohnYingling]

There is a parameter on the server for script timeout. Depending on the results (number, type?) of your query, the process is taking too long. Can you increase the timeout?

http://WWW.VBCompare.Com

 

[JefB]

John,
Thanks for responding.
All parameters are at the max (as far as I can tell).
I ended up rewriting the queries and eliminating a link to one of the tables. That seems to have helped alot.
My bigger concern is the inconsistancy of the time-out errors; some days it worked fine and other days only a single results set would be affected.
We also had a situation where, if I changed the url-passed argument "?Protocol=AAA988" to "?Protocol-aaa988" it would work!
All in all, very frustrating!
Any insights on how to avoid this situation would be most appreciated.

Jef

 

[JohnYingling]

Add indexes, reorganize existing indexes, compact it, unload/reload it, split the queries... ad nauseum. You have a timeout property (I believe) on the objConn or the DSN etc AND is there not one on the SQL server?

http://WWW.VBCompare.Com