Vincent Mesiti, Network Admin (vm*****@renmarkfinancial.com) writes:
I've recently installed SQL Server 2000 on Dell Power Edge 1600sc with
dual processor (2.8ghz) and 1 gig of ram, to use a CRM application
(Maximizer Enterprise 8.0)and since we make the install every time a
user is trying to access data it take about 5 to 10 second to see the
requested data. The performance of the SQL server less than the
pervise version of Maximizer.
I've made a typical install of SQL server 2000 and SP3.
Analysis Services as been installed too.
Without any knowledge about Maximizer Enterprise, it is very difficult
to say. There are of course a couple of standard suggestions:
o Make sure that statistics are up to date.
o Make sure that your tables are not fragmented.
o Check for blocking.
o Use Profiler to catch long-running queries and to review query plans.
o Add indexes to improve performance.
But in the end, I would suggest that you should contact the vendor about
the issue.
I've seen a strange memory workload this week, the used memory was
about 740,390 kb, from my knowledge of SQL, i think this is very not
normal.
That is perfectly normal. SQL Server is designed to grab as much memory
it can. The reason for that is that the more data SQL Server can hold
in cache, the less does it have to read from disk, and the faster the
response time will be. If there are other programs competing for memory
SQL Server will yield memory.
Now, if you are not used to see this memory consumption, it may be that
previously the queries were focused on a such a small part of the database
that SQL Server did not need much cache. If this have changed now, it may
be due to queries that now requires a table scan for some reason. So
a higher memory can be an indication that there are poor querly plans.
--
Erland Sommarskog, SQL Server MVP,
es****@sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp