Asp Forum - Re: increase the timeout is not the solutionthe query return the result under 1

Naren Kannan

12/7/2010 4:49:00 PM

HI,

Me too facing the similar kind of issue . If you got any solution please let me know.

mail: aachanaren@hotmail.com

> On Friday, January 11, 2008 2:27 PM OLAPFOREVE wrote:

> SQL Server 2005 sp2 64 bits
> cluster
> on a San technologie
> pooling connection is activate
> --------------------------------
>
> error: Timeut Expired. The timeout period elapsed prior to completion of the
> operation or the server is not responding
>
> Hi!
>
> We have a very strange problem.
>
> We write a store procedure who use fulltext search "contains" sentence
>
> When the programer use this store proc from an ".net SQLClient data
> provider" connection, all run well but sometime he receive a timeout expired
> error
>
> In the same time, If I run the same store proc from SQL server managment
> studio (query) the store proc run well and never return a timeout expired...
> never (under 1 sec response time)
>
>
>
> I rewrite the store proc for dont use fulltext search but in place use a
> basic "select ... from ... where" without "contains" sentence:
> Same thing .. with ".net SQLClient data provider" = sometime return a
> timeout.... from SQL server managment studio no timeout (under 1 sec
> response time)
>
>
> When then problem occurs, I monitor the connection in activity monitor I
> See in "Wait type" column:
> -when the store proc use fulltext search "contains" sentence : wait type=
> MSSEARCH
> -when the store proc dont use fulltext search "contains" sentence : wait
> type = LCK_M_RS_S (Key range Shared/Shared)
>
>
>
> Very strange....Could you help us

>> On Friday, January 11, 2008 11:02 PM Tom Dacon wrote:

>> When you run a query from management studio, it sets its own timeout
>> interval, which is different from the default SqlCommand timeout interval in
>> the framework (only 15 seconds). This puzzled me too for a while.
>>
>> The solution is to increase the timeout by setting the SqlCommand's
>> CommandTimeout property to a higher value (in seconds).
>>
>> Tom Dacon
>> Dacon Software Consulting
>>
>> "OLAPFOREVER" <OLAPFOREVER@discussions.microsoft.com> wrote in message
>> news:5A922CA0-705C-4017-B2E5-1446C75C0AA3@microsoft.com...

>>> On Monday, January 14, 2008 9:14 AM OLAPFOREVE wrote:

>>> increase the timeout is not the solution
>>>
>>> the query return the result under 1 second (in ssms) but
>>> in ado.net a timeout occurs
>>>
>>> "Tom Dacon" wrote:

>>> Submitted via EggHeadCafe
>>> Microsoft LINQ Query Samples For Beginners
>>> http://www.eggheadcafe.com/training-topic-area/LINQ-Standard-Query-Operators/33/LINQ-Standard-Query-Oper...

microsoft.public.dotnet.framework

Re: increase the timeout is not the solutionthe query return the result under 1

Naren Kannan

x Login to ForumsZone