Re: More than 2G of Ram

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Randy (randyvATitolDOTcom)
Date: 12/15/04


Date: Wed, 15 Dec 2004 14:21:56 -0600

Thanks for the quick reply. We are running standard edition, I double
checked that. The wierd thing is that enterprise manager says it can go up
to 3.5 gig. Do you think that could be a problem, or cause the problem
when we hit around 2G? i.e. I'm thinking that we need to set that down
to 2G since that is all standard edition can support.

If it helps at all, the error we were getting was

17120: Sql Server could not spawn process_loginread thread

"Tom Moreau" <tom@dont.spam.me.cips.ca> wrote in message
news:uDSZW8t4EHA.1596@tk2msftngp13.phx.gbl...
> SQL Server 2000 Standard Edition supports at most 2GB of RAM. Check the
> BOL
> topic "Maximum Capacity Specifications".
>
> --
> Tom
>
> ---------------------------------------------------------------
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
>
> "Randy" <randyvATitolDOTcom> wrote in message
> news:%23x3dalt4EHA.1292@TK2MSFTNGP10.phx.gbl...
> I have a Windows 2003 standard server running Sql 2000 standard sp3a. The
> server has 3.5G of ram.
>
> When I go into Enterprise Manager, look at the Server properties,
> Memory
> tab, Sql server is allowed to use a maximum of 3.5G of ram.
>
> My question is, do I have to use the /3G switch in the boot.ini inorder
> to
> allow sql to use memory above 2G? I'm thinking that I should add the
> /3G
> switch to the boot.ini file and reduce the max sql server memory so that I
> allow some for the operating system.
>
> The other day we some strange errors where nobody could connect. After
> researching the errors, they appear to be memory related but no specific
> causes. Sql Server was using exactly 2G of ram. The other unusual
> part
> too is that this server has been running this way for almost a year now.
> Not sure why we would have first run into this problem now.
>
> -Randy
>
>



Relevant Pages

  • Re: FTS Performance in SQL 2005
    ... we had no end of problems with SQL FTS. ... Looking for a SQL Server replication book? ... The Memory Usage and VM Size never increase over about 65 MB and 20MB. ... cost relative to the whole batch, ...
    (microsoft.public.sqlserver.fulltext)
  • Re: FTS Performance in SQL 2005
    ... we had no end of problems with SQL FTS. ... Looking for a SQL Server replication book? ... The Memory Usage and VM Size never increase over about 65 MB and 20MB. ... cost relative to the whole batch, ...
    (microsoft.public.sqlserver.fulltext)
  • RE: Consolidating instances of SQL server
    ... SQL Server is designed to use memory. ... The maximum amount of memory SQL Server can use varies depending on your ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • RE: The DBMS returned an unspecified error.
    ... | We are using Microsoft's JDBC driver for Java database access to SQL ... | Insufficient memory available. ... even though SQL Server 2000 is configured to use up to the ... the problem is most likely in the MemToLeave ...
    (microsoft.public.sqlserver.jdbcdriver)
  • RE: multiple instances of sql - 2 Gb memory limitation?
    ... The 2GB Memory limitation is per instance and the SQL Server can be ... Configure memory for more than 2 GB in SQL Server ... Microsoft Windows 2000 Advanced Server or Microsoft Windows 2000 Datacenter ...
    (microsoft.public.sqlserver.server)