> > > Do what SQL Server does, raise a 'Timed Out.' exception
> >
> > Isn't a "timeout" a client side thingy with MS SQL?
>
> I didn't think so but could be wrong, see
>

(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/a

> d_config_6soe.asp) I did a google but too many results to look through :-)

A "remote query" - as far as I know - is a query ran against a "linked
server",
albeit any ADO or ODBC source as well as other servers.

Because a "remote query" doesn't allow you to set database engine specific
options (like Firebird related options) because it uses a generic interface,
I
think SQL Server has options for that and will break the execution process
after the given timeout.

" For heterogeneous queries, remote query timeout specifies the number of
seconds (initialized in the command object using the DBPROP_COMMANDTIMEOUT
rowset property) that a remote provider should wait for result sets before
the query times out. This value is also used to set DBPROP_GENERALTIMEOUT if
supported by the remote provider. This will cause any other operations to
time out after the specified number of seconds. "

DBPROP_COMMANDTIMEOUT is an OLEDB command. I'm unsure if
this is passed on to the server (for those that support it), or a driver
issue. It
might as well be passed on to the server and that OLEDB only interfaces this
to the server on a per-command or per-connection basis. Either way, you
can also set ADO to a command timeout of 0 (= no timeout) and as far as I
know, there's no pre-configured timeout for all queries send to SQL Server.

With regards,

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com