Re: iis/asp + sql2000 a bit slow

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Florian (REMOVEUPPERCASEwizard_oz_at_gmx.net)
Date: 02/07/04 

Date: Sat, 07 Feb 2004 04:59:15 GMT

> WScript.Echo? I thought your were using ASP ...

Well, as I pointed out I was putting the crucial code into a .vbs file to
make sure IIS is not the cause of the problem, hence the WScript.Echo

> I suspect that you are suffering the consequences of failing to
encapsulate
> your queries into a stored procedure. You're doing too much processing in
> the client.

I have never done anything with stored procedures and I'm not sure why 6
"easy" queries are considered to be too much processing? But I will look
into how stored procedures work and try that. I usually code my web pages in
perl/mysql and I see why ;-) Can't do in this example though ...

> Your bottleneck is not the queries: it is the time needed to send the
> queries and return their results across the network. In addition,
recordset
> loops are very expensive: you should use GetRows to stuff your data into
> arrays and loop through the arrays instead. You will see a great increase
in
> performance if you follow these guidelines.

I actually converted the test script to use GetRows and that didn't seem to
help very much, if at all.

Thanks so far!!!

Relevant Pages

  • Re: Access migration to SQL Server
    ... caveat in the first sentence, i.e. remove access all together and you don't ... > about having to convert all your queries to views and stored procedures. ... > using a named query parameter to look up a value from a form control and ...
    (microsoft.public.access.conversion)
  • Re: Access migration to SQL Server
    ... caveat in the first sentence, i.e. remove access all together and you don't ... > about having to convert all your queries to views and stored procedures. ... > using a named query parameter to look up a value from a form control and ...
    (microsoft.public.sqlserver.server)
  • Re: Off Topic - Access to Postgres
    ... >>However, I find that using views, stored procedures and pass through queries ... >procedures and pass-through queries. ... >The reason pass-through queries are a problem for Access (and stored ... - To the extent that your application relies on server-side objects, ...
    (comp.databases.ms-access)
  • Re: Off Topic - Access to Postgres
    ... If sprocs and pass through queries are not the solution then ... >However, I find that using views, stored procedures and pass through queries ... The reason pass-through queries are a problem for Access (and stored ... may have to create a saved pass-through query, ...
    (comp.databases.ms-access)
  • Re: queries Vs Stored Procs
    ... > queries in one stored procedure rule. ... > should put each branch into its own stored procedures. ... to have a chain of Procs rather than a chain of queries. ... a single procedure can execute and use the results from several ...
    (microsoft.public.sqlserver.programming)