SQL TimeOut Error - Win32::ODBC

[1DMF]

I have my application all running nicely, with strict & warnings (except for a map command that throws an error I can't rectify!), anyways - everything was great - got new hosting no longer getting CGI timeout errors and then BANG!

I get a SQL server timeout error, I've only got it the once so cannot post the exact error msg but I beleive it is from the Win32::ODBC module I use.

Am I correct in assuming this was from the module or did SQL pass the error back to the module.

Is there anywhere I can change the time out setting to give SQL / PERL more time as i'm connecting to a remote data source attached to the internet with the lowest ADSL available (250 kbps up stream) and for the moment the company won't pay for a wider connection.

Any ideas on what could be done to get round this problem.

Cheers 1DMF

 

[AHinMaine]

What is the error message in the web server log?

--
Andy
"Historically speaking, the presence of wheels in Unix has never precluded their reinvention." -- Larry Wall

 

[1DMF]

How do I find that out?

 

[tchatzi]

The error messages are stored in the [red]error_log[/red] file in a folder named [red]logs[/red] in the [red]ServerRoot[/red] folder.


``The wise man doesn't give the right answers,
he poses the right questions.''
TIMTOWTDI

 

[1DMF]

There is nothing in the error logs supplied by my web host that I can see, but I think I've cracked it with the following lines in my File DSN..

CONNECT TIMEOUT=300
READ TIMEOUT=300

Well let's hope that cracked it, I haven't had a timeout error again, but maybe our remote SQL server hasn't had its bandwidth sucked up like the last time it happened.

It's so hard to fully point your finger at the root of a problem when so many factors are involved...

Load on Server, Load on web server, number of hops to reach destination I.P. , bandwidth usage on SQL server at time of request....etc...

only having a 250kbps upstream I know is a major factor but so far the above changes haven't made things any worse or caused an error so here's hoping.