Thanks for your reply.
But we have increased enough time in ASP. Still having the
same problem. The execution time that it takes in Query
Analyzer is very very less than the time that we hv set in
ASP.
Why I am not getting 'Timed Out Error' in QA and also why
it is working fine without any error in ASP after it is
executed first time in 'Query Analyzer'. Why ASP not able
to execute the stored procedure in first time even though
it has got enough time set in the settings.
Can anybody help me.
tks in advance,
Sri.
Quote:>-----Original Message-----
>My guess is that the first time you execute the proc, SQL
Server has to compile it. That takes a
Quote:>while, so long that it exceeds your time-out. Just
increase the time-out in the app and have the
Quote:>first user take that penalty. Removing blanks will most
probably make no noticeable difference.
Quote:>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>> Hi Everybody,
>> One of the user had written a Stored Procedure with 600
>> lines. The Problem is when it is called from 'ASP', it
>> says 'Timed Out Error'. But when we compile this Stored
>> Procedure in Query Analyzer, it executed without any
>> error. After that 'ASP' users able to use this Stored
>> Procedure with out any problem, I mean 'Timed Out Error'
>> is not coming.
>> So we hv been doing this for the past 10 days. That is
if
>> users execute from 'ASP' for the first time, the error
>> comes. But once it is compiled in Query Analyzer, we are
>> not facing this problem. I don't know, why?.
>> When I went through the Stored Procedure, I am able to
see
>> lot of blank lines and unnecessary spaces. If we
truncate
>> those lines it may come around 350 lines only.
>> I want to know, because of these unnecessary Blank Lines
>> or Spaces is it possible for that error('Timed Out
>> Error'). Can anybody guide me on this?
>> tks in advance,
>> Sri
>.
by