There are a few things to consider here.
The browser issue you mention is (possibly) related to how different
browsers load pages - some wait for the entire <table> element to arrive
(i.e. until </table>) before rendering the table for display, others do it
as it comes. Some (I think) delay rendering until [some] images are loaded,
etc. I don't know if these options can be configured or not so might not be
the only issue. Caching [of images] might be having an effect too.
I don't have experience of using recordsets the way you do, without an
ADODB.Connection object, however you should open Recordsets/database
connections for the minimal amount of time possible. Also, I don't know if
you explicitly need to close the database connection with your method or
not.
Is your site the only thing using the SQL Server? If not, do other
sites/systems run noticeably faster after a restart? I wonder if perhaps
there is a mis-configuration with the SQL Server causing the slowdown; is it
fully patched? What is the memory usage like with both SQL and IIS before
and after a restart?
Jevon
"KWilliams" <KWilliams@discussions.microsoft.com> wrote in message
news:DC232790-C789-42DC-9C54-837A435874B1@microsoft.com...[color=blue]
> I'd like to get some good advice about our old ASP site. You can see our
> home
> page at:
>
http://www.douglas-county.com/
>
> ...and an example application page at:
>
http://www.douglas-county.com/employ...topenings2.asp
>
> Our old site uses classic ASP with JavaScript syntax. I'm in the process
> of
> developing a new site that uses XML/XSLT/CSS/ASP.NET/VB.NET, but in the
> meantime, we still have our old site up. It contains a lot of applications
> that use SQL Server 2000 data, and we're having some major performance
> issues.
>
> I already know that one issue is the use of tables for formatting, and I'm
> already correcting that problem by using CSS Positioning with my new site.
> Besides that, here are some of the issues that we're having:
>
> Different Browser Issues?
> The site loads much quicker for me in Mozilla Firefox than it does in IE
> 6.0
> for some reason. If this difference is an obvious sign of something, I'd
> love
> to know what that could be.
>
> Connection Issues?
> I've looked into whether this problem could be due to "leaky connections",
> but this is how I have my connections set up:
>
- <%@language="javascript"%>
-
> <%
-
> var MM_strConn_STRING =
-
> "Provider=SQLOLEDB;Server=SERVERNAME;Database=DBNAME;UID=UID;PWD=PWD"
-
> %>
-
> <%
-
> var Recordset1 = Server.CreateObject("ADODB.Recordset");
-
> Recordset1.ActiveConnection = MM_strConn_STRING;
-
> Recordset1.Source = "SELECT * FROM dbo.tblTABLENAME";
-
> Recordset1.CursorType = 0;
-
> Recordset1.CursorLocation = 2;
-
> Recordset1.LockType = 3;
-
> Recordset1.Open();
-
> var Recordset1_numRows = 0;
-
> %>
-
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-
> "http://www.w3.org/TR/html4/loose.dtd">
-
> <html>
-
> <body>...</body>
-
> </html>
-
> <%
-
> Recordset1.Close();
-
> %>
>
> The reason I'm looking at this as a possible cause is because my Network
> Administrator states that when he restarts the SQL Server, the site loads
> quicker. Then over time, it seems to get bogged down until the server is
> restarted again. It loads much slower for some users than others for some
> reason, and that's when they have the same browser version.
>
> Ok, that's it. If there are any other obvious causes of this issue, please
> let me know. Any constructive criticism would be greatly appreciated.
> Thanks.[/color]
