I've a very complex table-value function in MS-SQL (ADO protocol) which takes a long time to complete/send the first resultset row.
For example: SELECT * FROM MY_FUNC(param1, param2, ...);
Sometimes it takes more than 60 seconds (using SQL Management Studio) until the server returns the first row.
If I run the query with zeos, the execution stops after 60 seconds with the exception "timeout expired".
It seems that this timeout comes from ADO. There are several options to set the ADO timeout, for example:
- set the QueryTimout registry value for JET to 0
set CommandTimeout=0 and/or set QueryTimeout=0 in the connection string
Is there a way to set the timeout explicitly via zeos?