Running ODBC application against SQL server 2000, ODBC connection is
established
successfully. If we then have an idle period of, say, 30 min, when app
is not accessing ODBC connection, and then an ODBC request is made - we
see an exception thrown, indicating disconnect.

I can't seem to find anything about this. Is there indeed something
like idle timeout? Where is it triggered - client, server, TCP layer?
Anyway to change this timeout? What's the best way to keep connection
"warm"? (except executing bogus select requests)..

Appreciate help.

M.