We were getting [Microsoft][ODBC SQL Server Driver]Timeout expired error messages via ado and IIS on a website yet when running the query via Query Analyser it took a long time, but nevertheless worked.
Using Profiler we would see the Start and End times, but still have a web page error.
Many many people out there with the same problem judging by the number of forum entries.
Quite often the commandtimeout parameter would be suggested, so we tried adding to the connection string.
e.g. DRIVER=SQL Server;POOLING=FALSE;commandTimeout=0;SERVER=etc.etc...
But this is not the only CommandTimeout Parameter available... There is one in ADO itself.
This site told us how to do it, and so we hope to add a bit of 'Google Power' to it so it appears first in the Google list, rather than further down.
It probably applies to any web scripting language too:
© 2004 - 2013 1 Oak Hill Grove Surbiton Surrey KT6 6DS Phone: +44(020)33845936