Specify timeout for .CrossApplySqlServerQuery and .ToSqlCommand

[mickvikt]

Is there a way to specify the SQL command execution timeout for .CrossApplySqlServerQuery and .ToSqlCommand?
I'm trying to run a stored proc using .CrossApplySqlServerQuery and consume the result set that it returns and it fails me with a timeout.

As I found out by googling, default CommandTimeout for SqlConnection and OdbcConnection is 30 seconds which is not enough.

Is there a way to go around this? How do you solve this in your production environments, because I suspect not all queries/stored proc calls can be completed in under 30 seconds.

[paillave]

very soon, a new realease will be done containing improvments for Oledb and Odbc.
In the meantime, can you see if you can set this timeout in the connection string? (I believe it may be possible)

[mickvikt]

Nice to hear about upcoming release. Now regarding the timeout, unfortunately you cannot specify it in the connection string. It is being set on the Command object.

…

On Tue, Jul 4, 2023, 09:44 Stéphane Royer ***@***.***> wrote: very soon, a new realease will be done containing improvments for Oledb and Odbc. In the meantime, can you see if you can set this timeout in the connection string? (I believe it may be possible) — Reply to this email directly, view it on GitHub <#463 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGGQZ2F42L46M3ERJT32QBTXOO3U7ANCNFSM6AAAAAAZ4P3BCM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[paillave]

Indeed, I mixed with the connection timeout.