>>Are you confusing DbConnection.ConnectTimeout and DbCommand.CommandTimeot ?
>>Regards,
>>Viv
>
>I guess I'm. I recall the discussion a while back and I remember I tried to adjust our connection string. At the end we all just switched to local SQL Server for development that solved our timeout problems.

It might solve ConnectTimeOut problems but long running queries might still require the tweaking of the CommandTimeout setting......

Best,
Viv