[dba-SQLServer] SQL Performance

Well, since you are loathe to give up Advanced Server, what are the
chances of you dropping in another CPU of equivalent specs? Second, with
only one CPU this is a helluva load to put on a single server. Third,
does Query Analyzer run as slowly as your app? (Do some selects etc.
from QA to see.)

Arthur

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim
Lawrence (AccessD)
Sent: Sunday, February 22, 2004 5:11 PM
To: dba-sqlserver at databaseadvisors.com
Subject: RE: [dba-SQLServer] SQL Performance


Hi Arthur:

Thanks for your suggestion but the advanced model is what I purchased
and I am loathe to change now. The other thing is that every other
application that runs off this server is performing perfectly. Even MS
SQL 2000 is, minus the performance, or lack of it. The RAM is not even
being impacted so my thought that it might be a code segment is bleeding
all over, is unfounded. You might be on to something, with SQL and
W2000AdvSer...but where can I look. There is probably a simple setting
somewhere in the registry.

As all my new apps come from MS Action pack, I have passed my problem on
MS and hope they have something.

Thanks again
Jim

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Arthur
Fuller
Sent: Sunday, February 22, 2004 7:34 PM
To: dba-sqlserver at databaseadvisors.com
Subject: RE: [dba-SQLServer] SQL Performance


I have never tested this so be advised that it's nothing more than a
WAG, but you didn't mention the number of processors. The ONLY reason to
run Advanced is multiple processors. I have a tired old dog server with
twin P4-500s and it runs like quick! I have never tried to install
Advanced on a single CPU unit because the docs clearly state that it's
futile. Is it possible for you to back off Advanced and try the
single-CPU version instead?

Another thing to check is how much RAM each process is consuming, or
prepared to consume.

HTH,
Arthur