Our web server is running Windows 2000 Advanced Server which we also use 

as

a SQL Server running Version 7.0.   The problem is that the SQL Server is

slow as hell sometimes.  The computer has almost 400 mb of ram and is a

PentiumIII 500.  I know it's not the best setup, but for what we are

throwing at it, it should be childs play.  If you try to go to a web page

that access's the sql server, then sometimes (not always) it will take so

long that it will time out waiting for the server to respond.  The browser

window will just say "web site found, waiting for reply".  We probably 

only

get around 200 - 300 hits a day.  This problem is holding us back.  When I

installed SQL server, I just basically left everything defaulted.  Also on

the server, the hard drive is "hardly ever" accessed, which leads me to

believe that ram, or lack thereof is not the problem.  I am stuck.  The

thing that bugs me is sometimes it will work instantly, then you hit 

refresh

and it will take 20 seconds for the page to come up. (All this on the lan 

by

the way).  Sometimes it's the other way around. You go to the page and it

will keep timing out, after hitting refresh and waiting to see what 

happens

a few times, then suddenly it starts going pretty good again.



The sql code is pretty straight forward.  Open a connection then loop and

print about 1 - 5 records, there isin't even hardly any code.  If it's

straight html or vbscript with no sql server connections, then it's fast.  

I

open a connection to a dbf file also using odbc and thats all really fast

too.  Anyone have any tips to this problem?  I am getting pretty 

desperate.

Thanks

This might not be a simple problem. Are you sure it's SQL Server that's

causing the slowdown, and not IIS?



You need to narrow down exactly what the problem is. Try a combination

of the following:



1. Get hold of SQL 7.0 SP2. It cures some very bad 'optimization

features' (my quotes).

2. Try the queries in Query Analyzer to see how fast they run.

3. Use Performance Monitor to see what's happening.

	- Disk Queue

	- Memory



You could also try changing the default netlibrary to IP. MS said that

they'd found this was the fastest, but I'm not sure if that's still the

case. There's an MSDN article about this sort of thing - an MSDN search

should pull it up.



Dave





"James D" wrote in message

news:<6553BCF3E25DD2118F0A00AA00AE6AAA21C7E5@t...>...

> Our web server is running Windows 2000 Advanced Server which we also

use 

> as

> a SQL Server running Version 7.0.   The problem is that the SQL Server

is

> slow as hell sometimes.  The computer has almost 400 mb of ram and is

a

> PentiumIII 500.  I know it's not the best setup, but for what we are

> throwing at it, it should be childs play.  If you try to go to a web

page

> that access's the sql server, then sometimes (not always) it will take

so

> long that it will time out waiting for the server to respond.  The

browser

> window will just say "web site found, waiting for reply".  We probably



> only

> get around 200 - 300 hits a day.  This problem is holding us back.

When I

> installed SQL server, I just basically left everything defaulted.

Also on

> the server, the hard drive is "hardly ever" accessed, which leads me

to

> believe that ram, or lack thereof is not the problem.  I am stuck.

The

> thing that bugs me is sometimes it will work instantly, then you hit 

> refresh

> and it will take 20 seconds for the page to come up. (All this on the

lan 

> by

> the way).  Sometimes it's the other way around. You go to the page and

it

> will keep timing out, after hitting refresh and waiting to see what 

> happens

> a few times, then suddenly it starts going pretty good again.

> 

> The sql code is pretty straight forward.  Open a connection then loop

and

> print about 1 - 5 records, there isin't even hardly any code.  If it's

> straight html or vbscript with no sql server connections, then it's

fast.  

> I

> open a connection to a dbf file also using odbc and thats all really

fast

> too.  Anyone have any tips to this problem?  I am getting pretty 

> desperate.

> Thanks

> 

> 




$subst('Email.Unsub')