|
 |
asp_databases thread: Performance Problem with ASP and Database.
Message #1 by "krishna kumar" <krishi_kk@u...> on Fri, 23 Feb 2001 21:02:18
|
|
Hi,
I shall try to give as much details possible about the problem. We had a
full fledged ASP based application that was working fine and then due to
some management decisions, our database was to be moved to a machine of a
lower configuration. As a result of this, we expected the queries to run
slower. But it seems that after switching the machines(database) it does
not return any results at all. We are able to run queries from the backend
and we get the results but when we run from the ASP pages, no results are
got. The number or rows in the database is in the order of millions. We
increased the time out settings of the script and the command so as to
make up for the delay but nothing seems to work. I am in the process of
diagnosing the problem. Some information on how i can find the time
elapsed in connecting to the database and the time the webserver spends on
publishing the database would be of primary interest. I hope i have
explained the problem. If u can help and have questions, kindly email me
and i shall tell u all that i know.
Thanks in advance,
Krishna
Message #2 by "Kamran" <user_15@h...> on Mon, 26 Feb 2001 01:22:11
|
|
Check ot Alex Homer's Display Progress bar. In this interesting article he
queries the database for all records from a table and at the same time
uses the Recordset property of the Recordset object and DHTML features to
show the progress that ASP.dll makes in writing to the script to be sent
to the browser. Link is --->
http://www.asptoday.com/content/articles/20000317.asp
In addition try returning small records at a time.
> Hi,
> I shall try to give as much details possible about the problem. We had
a
> full fledged ASP based application that was working fine and then due to
> some management decisions, our database was to be moved to a machine of
a
> lower configuration. As a result of this, we expected the queries to run
> slower. But it seems that after switching the machines(database) it does
> not return any results at all. We are able to run queries from the
backend
> and we get the results but when we run from the ASP pages, no results
are
> got. The number or rows in the database is in the order of millions. We
> increased the time out settings of the script and the command so as to
> make up for the delay but nothing seems to work. I am in the process of
> diagnosing the problem. Some information on how i can find the time
> elapsed in connecting to the database and the time the webserver spends
on
> publishing the database would be of primary interest. I hope i have
> explained the problem. If u can help and have questions, kindly email me
> and i shall tell u all that i know.
> Thanks in advance,
Message #3 by "krishna kumar" <krishi_kk@u...> on Mon, 26 Feb 2001 14:45:42
|
|
Hi,
Thanks for the link. Even though it seems to be helpful, I could not take
a look at the code as i have not subscribed to ASPToday.com!!!!!!
I have not included the details about the hardware or software in my
earlier mail. My apologies for that. We are using Windows NT 4.0 with
SP6a, IIS. Teradata is our database.
Thanks,
Krishna
> Check ot Alex Homer's Display Progress bar. In this interesting article
he
> queries the database for all records from a table and at the same time
> uses the Recordset property of the Recordset object and DHTML features
to
> show the progress that ASP.dll makes in writing to the script to be
sent
> to the browser. Link is --->
> http://www.asptoday.com/content/articles/20000317.asp
>
> In addition try returning small records at a time.
>
>
>
> > Hi,
> > I shall try to give as much details possible about the problem. We
had
> a
> > full fledged ASP based application that was working fine and then due
to
> > some management decisions, our database was to be moved to a machine
of
> a
> > lower configuration. As a result of this, we expected the queries to
run
> > slower. But it seems that after switching the machines(database) it
does
> > not return any results at all. We are able to run queries from the
> backend
> > and we get the results but when we run from the ASP pages, no results
> are
> > got. The number or rows in the database is in the order of millions.
We
> > increased the time out settings of the script and the command so as to
> > make up for the delay but nothing seems to work. I am in the process
of
> > diagnosing the problem. Some information on how i can find the time
> > elapsed in connecting to the database and the time the webserver
spends
> on
> > publishing the database would be of primary interest. I hope i have
> > explained the problem. If u can help and have questions, kindly email
me
> > and i shall tell u all that i know.
> > Thanks in advance,
|
|
 |