|
 |
asp_databases thread: Trouble with ADO/SQL
Message #1 by "Walter Burrough" <w.burrough@h...> on Sat, 9 Dec 2000 16:43:17 -0000
|
|
Hi,
I have a problem running an sp. The stored procedure is quite complex and I
pass it a comma delimited list of id numbers which identify rows in a table.
The SP loops through the IDs and runs some INSERTS for each using the data
from the rows they identify. It works fine.
The trouble comes when the list gets long. When I pass 20 or so it works but
is rather slow. With a 100 or so, it times out.
What's odd is that it's actually quite quick when I run it direct from the
Query Analyser rather than from ADO.
Does this mean anything to anyone?
Thanks
walter
Message #2 by "Dallas Martin" <dmartin@z...> on Sat, 9 Dec 2000 12:45:35 -0500
|
|
Ah ha!!! Timeout Problem.
It sounds that its the Web Server (IIS) that is timing out.
Increase the Script timeout value and see if it solves your
problem. I had a similar problem and learn my lesson.
Here the code you need:
At the top of your ASP page, insert this
Server.ScriptTimeout = nSeconds
The default is 90 seconds, try increasing this value,
perhaps double.
hth,
Dallas Martin
----- Original Message -----
From: "Walter Burrough" <w.burrough@h...>
To: "ASP Databases" <asp_databases@p...>
Sent: Saturday, December 09, 2000 8:33 PM
Subject: [asp_databases] Trouble with ADO/SQL
> Hi,
> I have a problem running an sp. The stored procedure is quite complex and
I
> pass it a comma delimited list of id numbers which identify rows in a
table.
> The SP loops through the IDs and runs some INSERTS for each using the data
> from the rows they identify. It works fine.
>
> The trouble comes when the list gets long. When I pass 20 or so it works
but
> is rather slow. With a 100 or so, it times out.
>
> What's odd is that it's actually quite quick when I run it direct from the
> Query Analyser rather than from ADO.
>
> Does this mean anything to anyone?
>
> Thanks
> walter
>
>
Message #3 by "Dave Sussman" <davids@i...> on Sun, 10 Dec 2000 11:56:35 -0000
|
|
I'd also recommend running the SQL Profiler to see what ADO is doing.
Dave
"Dallas Martin" <dmartin@z...> wrote in message
news:24249@a..._databases...
>
> Ah ha!!! Timeout Problem.
>
> It sounds that its the Web Server (IIS) that is timing out.
>
> Increase the Script timeout value and see if it solves your
> problem. I had a similar problem and learn my lesson.
>
> Here the code you need:
>
> At the top of your ASP page, insert this
>
> Server.ScriptTimeout = nSeconds
>
> The default is 90 seconds, try increasing this value,
> perhaps double.
>
> hth,
> Dallas Martin
>
>
>
> ----- Original Message -----
> From: "Walter Burrough" <w.burrough@h...>
> To: "ASP Databases" <asp_databases@p...>
> Sent: Saturday, December 09, 2000 8:33 PM
> Subject: [asp_databases] Trouble with ADO/SQL
>
>
> > Hi,
> > I have a problem running an sp. The stored procedure is quite complex
and
> I
> > pass it a comma delimited list of id numbers which identify rows in a
> table.
> > The SP loops through the IDs and runs some INSERTS for each using the
data
> > from the rows they identify. It works fine.
> >
> > The trouble comes when the list gets long. When I pass 20 or so it works
> but
> > is rather slow. With a 100 or so, it times out.
> >
> > What's odd is that it's actually quite quick when I run it direct from
the
> > Query Analyser rather than from ADO.
> >
> > Does this mean anything to anyone?
> >
> > Thanks
> > walter
> >
> >
>
>
|
|
|
View Cart
