memory prob w/SQL 2000

We just purchased a new server - Dell 6550, quad 2G
processors, 6G RAM running Windows 2000 Advanced Server.
I installed SQL 2000 Standard Edition and moved my
databases to this new system. My problem is that now the
sql service will continually use memory until it gets to
about 1.7G and then it locks up the service. No one can
login to the application that uses the db's and you can't
access the db's via Enterprise Manager or sql Query.
Stopping and restarting the service does not help. I have
to actually reboot the server. I tried using the memory
setting in the sql server properties but it doesn't help.
Any ideas or solutions?
Thanks for your help!
CathyYou need to set the /3GB and /PAE switches in the boot.ini file and enable
the AWE option in SQL Server to use the full 6GB. Since AWE will use all
the memory in a fixed manner you should then set the max memory setting in
Sql Server to something less than 6GB. See here for more details:
http://www.sql-server-performance.com/awe_memory.asp Using AWE Memory
http://www.support.microsoft.com/?id=321363 SQL Server 7 & 2000 memory
usage
http://www.support.microsoft.com/?id=274750 Memory config
http://www.support.microsoft.com/?id=283037 Large Memory Support Is
Available in Windows 2000 (AWE)
http://www.support.microsoft.com/?id=811891 Can not use more than 2GB of
memory
Andrew J. Kelly
SQL Server MVP
"Cathy Tumlinson" <cathyt@.tcmhmrs.org> wrote in message
news:00b301c34497$8bb9b5a0$a101280a@.phx.gbl...
> We just purchased a new server - Dell 6550, quad 2G
> processors, 6G RAM running Windows 2000 Advanced Server.
> I installed SQL 2000 Standard Edition and moved my
> databases to this new system. My problem is that now the
> sql service will continually use memory until it gets to
> about 1.7G and then it locks up the service. No one can
> login to the application that uses the db's and you can't
> access the db's via Enterprise Manager or sql Query.
> Stopping and restarting the service does not help. I have
> to actually reboot the server. I tried using the memory
> setting in the sql server properties but it doesn't help.
> Any ideas or solutions?
> Thanks for your help!
> Cathy|||I didn't catch the std edition in the original post. Std can only support
2GB of ram and you will only get 1.7GB in reality. Having 6GB on that
machine is pretty much a waste if you only have 1 instance of sql server
running. I am not convinced this is a sql server issue. Stopping and
restarting the sql server service should certainly free up any memory it had
previously taken and everything should run as normal. Not that using all
the ram should kill it in the first place. If you have to reboot then I
would suspect a server issue more than a sql one. Does the rest of the OS
behave normally when this happens? What are the cpu's and disks like when
this occurs? To get to the bottom as fast as possible you might want to
call ms pss so they can walk through this with you and they can then get a
much better feel for how everything is acting and set up.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
--
Andrew J. Kelly
SQL Server MVP
"Cathy Tumlinson" <cathyt@.tcmhmrs.org> wrote in message
news:0cc101c344a8$f0ab0480$a501280a@.phx.gbl...
> I'm running MS SQL 2000 Standard Edition. I don't have an
> AWE option.
> Cathy
> >--Original Message--
> >Do you have AWE memory setup on you server? Sometimes I
> found that AWE
> >settings cause this
> >
> >DRC
> >Alphabet collector (MCP,MCSD,MCSA,NECD ECT.)
> >
> >*** Sent via Developersdex http://www.developersdex.com
> ***
> >Don't just participate in USENET...get rewarded for it!
> >.
> >|||you might try the startup parameter -g100 (or higher)
this tells SQL Server to reserve a certain amount of
address space for memory allocations excluding the buffer
pool.
What might be happening is that the buffer pool starting
allocation memory (because so much is available) to the
point where an insufficient amount of address space is
left for other functions
the setting is in the SQL Server properties
page, "General" tab, "Startup Parameters" button
depending on the allocation needs of your particular app,
you may need a higher setting, or you could get by with a
lower setting,
>--Original Message--
>We just purchased a new server - Dell 6550, quad 2G
>processors, 6G RAM running Windows 2000 Advanced
Server.
>I installed SQL 2000 Standard Edition and moved my
>databases to this new system. My problem is that now
the
>sql service will continually use memory until it gets to
>about 1.7G and then it locks up the service. No one can
>login to the application that uses the db's and you
can't
>access the db's via Enterprise Manager or sql Query.
>Stopping and restarting the service does not help. I
have
>to actually reboot the server. I tried using the memory
>setting in the sql server properties but it doesn't help.
>Any ideas or solutions?
>Thanks for your help!
>Cathy
>.
>