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

Tech-Archive recommends: Speed Up your PC by fixing your registry

Yes if you really do have Enterprise editions of both the OS and SQL Server you can use AWE and PAE to access more than 2GB as per the documentation listed.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Tomar" <Tomar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:1580B829-B63D-4D00-90DE-1EB87952713E@xxxxxxxxxxxxxxxx
It is Sql 200 enterprise, 2003 Enterprise edition. And we have a cluster of
dual core server(32 bit). Both machines are equipped with 8gb of RAM. We have
tried all sort of option but still sql is unable to use more 1.5 - 1.7 gb per
CPU.

The userbase of our application is 1500+ and it is database oriented
application so we see heavy traffic in the application. As such we don't have
any issues with anything but I don't know why it does not go more than 2gb.

I will try the URL sent by you. Hopefully it will solve the problem.

--Hemant

"Ekrem Önsoy" wrote:

First of all, it's not me who is experiencing this problem. The OP is
someone else.

Regarding to your scenario, you said your SQL Server 2000 instance is
installed on a Windows Server 2003 OS.

If your SQL Server 2000 is Enterprise Edition and your Windows Server 2003
is also Enterprise Edition then you can take advantage of your 8GB of RAM.

How to configure SQL Server to use more than 2 GB of physical memory:
http://support.microsoft.com/kb/274750/en-us

Memory Support and Windows Operating Systems:
http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx

--
Ekrem Önsoy




"Tomar" <Tomar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:10DC38B4-106F-4B31-A0AC-7E576A4CFB46@xxxxxxxxxxxxxxxx
> 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: SQL-SERVER 2005 SP2 und Microsoft Dynamics 5.0 (ehem. Navision
    ... Wert ist immer zwischen 84,7 -99,8 akt. ... es geht darum wieviel % der Daten, die der SQL Server wollte bereits in seinem Workspace waren. ... 16 GB 2 GB RAM ...
    (microsoft.public.de.sqlserver)
  • Re: WSUS
    ... Les Connor [SBS MVP] ... Is your server exhibiting significant performance problems, and if so, how ... SQL Server: ... >No wonder SBS brings servers with 4GB of RAM to their knees. ...
    (microsoft.public.windows.server.sbs)
  • =?Utf-8?Q?Re:_sqlserver.exe_kommt_nicht_=C3=BCb?= =?Utf-8?Q?er_100mb?=
    ... 300ms im RAM gehalten werden. ... Morgen werden wir mehr Speicher einbauen und nochmal die Zeiten auslesen. ... um den Server selbst zu tracen. ... MCTS: Microsoft SQL Server 2005 ...
    (microsoft.public.de.sqlserver)
  • RE: Fulltext failure on a 2 node cluster
    ... Server full-text search resource online: "SQL Cluster Resource 'Full Text' ...
    (microsoft.public.sqlserver.clustering)
  • Re: HELP PLEASE ~ ???
    ... You mentioned that it went ahead and added a SQL ... SQL Server 2000 database for all my data. ... find the connectionString in the newly recreated SQLExpress database. ... The connection string specifies a local Sql Server Express instance ...
    (microsoft.public.dotnet.framework.aspnet)