Anyone have experience using Azure SQL Data Sync? Any "If they only put
this on the back of the brochure" moments that left you with buyers remorse?
---
Regards,
Scott Barnes
http://www.riagenic.com
Yep, no connection timeout != command timeout.
You need to have a command timeout set on each command that’s created. Sucks if
the devs didn’t do that up front but I see this often. Works great until
queries take more than 30 seconds.
Regards,
Greg
Dr Greg Low
1300SQLSQL (1300 775 775) offic
I don't recall such an ability. You'll probably have to go the helper
method and config value route - fun fun!
On Monday, 10 July 2017, Greg Keogh wrote:
> Folks, I have some old code that uses a mixture of Enterprise Library 5
> and traditional ADO.NET classes. On some machines I'm getting comm
;Connection Timeout=XX in the connection string
where XX is in seconds is the way to do it in a single connection string.
I don't know about EL
regards,
Preet, in Auckland NZ
On 10 July 2017 at 14:27, Greg Keogh wrote:
> Folks, I have some old code that uses a mixture of Enterprise Library
Folks, I have some old code that uses a mixture of Enterprise Library 5 and
traditional ADO.NET classes. On some machines I'm getting command timeouts
at 30 seconds. Is there a way of globally changing the timeout for all
commands on the connection, perhaps by changing the connection string?
I cou
