As a test, do you still get timeouts when both are set to 0? That is supposed to be infinite. Also, I read online that for ADO.NET, there is a CommandTimeout property of the command object that defaults to 30 seconds. And of course 0 means infinite. You can also set this value at application level: System.Data.IDbCommand.CommandTimeout = 50 or whatever. I'm assuming you tried that already though...
>>Silly question, but I like to rule everything out. What does this setting show? The same?
>>
>>1. Open SQL Server Enterprise Manager and find the server that contains your database.
>>2. Right click on the server name.
>>3. Select properties.
>>4. Choose the Connections tab.
>>5. Increase the query timeout value. (The value is in seconds. Set it to 0 for unlimited time)
>>6. Click OK.
>
>The Connection section shows:
>
>Connection Timeout 15
>Execution Timeout 0
.·*´¨)
.·`TCH
(..·*
010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"
