View Single Post
Old September 21st, 2004, 08:22 AM
Hal Levy Hal Levy is offline
Friend of Wrox
Points: 3,489, Level: 24
Points: 3,489, Level: 24 Points: 3,489, Level: 24 Points: 3,489, Level: 24
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
Join Date: Jun 2003
Location: Central, NJ, USA.
Posts: 1,101
Thanks: 0
Thanked 2 Times in 2 Posts

I, of course, bow to Peter when he gives an answer- He's much smarter than I am. I don't think, however, that the key to solving your problem is a migration to .NET but with dealing with the data issues. You need to look at how long the Queries take to run using a query tool and then compare it to the page response. If the time is the same, the issue isn't the ASP.

That said, depending on the quality of the ASP code (and for that matter, the VB code in your business objects) you could improve performance.

I'd test a Query time directly to the DB versus the query running through the application. If the response time is very different, you can justify re-writing the application.

I am sure you have done the obvious, like using stored proc's instead of using SQL embeded in code...

Hal Levy
Web Developer, PDI Inc.

NOT a Wiley/Wrox Employee