Re: Seems like only 1GB RAM being used even when higher MAX RAM is

We also had similar situtaion where SqlServer 2000 was using the complete
memeory installed in the server. We have dual core CPU with windows 2003 os.

If your machine is 32 bit your system will never use more than 2 gb RAM per
cpu. So server won't allow SQL to use more than 2gb per CPU. And if it is 64
bit machine than it will use more than 2 gb of RAM per CPU.

As we have dual core machine and had installed 8 gb RAM but 4 gb is just
lying and it is used at all. I may be out of synch but hope this helps to
reduce your problem.


"Ekrem Önsoy" wrote:

I'm following this thread and the problem is really interesting.

However, in your following reply, I wish you'd tell us the "Total Server
Memory" and "Target Server Memory" counters' results.

I know, you gave us lots of proves about the memory consumption. But the
results of these counters would definitely prove you had enough RAM but SQL
Server can't take advantage of it.

--
Ekrem Önsoy



"Larry Epn" <larryepn@xxxxxxxxxxxxxxx> wrote in message
news:2BD8FB94-7940-4707-A0FC-02CB9279BCCE@xxxxxxxxxxxxxxxx
Yes, it does not add up.
I just reconfirmed all of this.
Here is boot.ini:
--------------------------------------
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINNT="Microsoft Windows 2000 Server"
/fastdetect
--------------------------------------
Perfmon shows available MBytes = 2148
so 2Gb are just sitting there.

I made the changes you suggested (set min = 0, max = 2Gb), and restarted
sql
service. I run a halacious join query and watch the memory increase,
increase,increase, and then in task manager it gets stuck at its usual
1062Mb, which is consistent with the PerfMon shows. Then in PerfMon, the
%Disk Time goes through the roof. This is what happens ALL the time,
regardless of what settings are changed.

Your suggestion to move to later versions is valid, but I don't see why I
can't get THIS server to use at least 2Gb (or 1.7Gb who's counting?) !!!

Does Microsoft have any ideas?

Thanks,
Larry


.

Relevant Pages

  • Re: Alocated Memory Error (SQLSERVR)
    ... but my understanding is that the MSDE instances are designed to ... and you don't want it grabbing all that RAM. ... running but non ever going about 200mb of memory usage. ... Server 2000 SP4, ...
    (microsoft.public.windows.server.sbs)
  • Re: Windows 2000 Server StandardEdition /PAE Question
    ... specifically the SQL Server 2000 Standard Edition on that server. ... His point is that applications can only use up to 2 GB or RAM on ... a process running under Windows 2000 or Windows Server 2003 can ... used) with some of the memory being physical memory and some being virtual ...
    (microsoft.public.win2000.general)
  • Re: Would a 2nd processor really be a waste of time???? help
    ... > buy another processor and more ram, however this is what one supplier ... > Your server has only 1 processor. ... installation including changing the bios settings and installing the smp ... The second cpu will probably help ...somewhat. ...
    (comp.unix.sco.misc)
  • Re: Alocated Memory Error (SQLSERVR)
    ... FWIW I am not using sbs 2003 premium, ... non ever going about 200mb of memory usage. ... on what you should throttle the RAM to. ... Server 2000 SP4, ...
    (microsoft.public.windows.server.sbs)
  • Re: Alocated Memory Error (SQLSERVR)
    ... what you should throttle the RAM to. ... Server 2000 SP4, ... The memory problem on my ... shared exchange server address book or anything exchange related). ...
    (microsoft.public.windows.server.sbs)