Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

contiguous memory issue Expand / Collapse
Author
Message
Posted Friday, July 3, 2009 9:24 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, July 9, 2009 11:36 AM
Points: 2, Visits: 1
we are running sql 2000 sp3 under a win2000 Sp2 OS. we recently upgraded the server ram from 4 gb to 8gb. afterwards, we started to get the error 'not enough contiguous memory'. we did not have this issue when we were just using 4gb but after the upgrade to a bigger memory we started to get one. before rolling back the upgrade as a last resort, we would like to know if there are settings that we could change/modified to get around this problem. we are constraint by the application we are running to stay in current version of the OS as well as the SQL.
Post #747032
Posted Wednesday, July 8, 2009 8:59 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, December 17, 2014 12:14 PM
Points: 176, Visits: 841
Upgrade to at least service pack 4. The sp 4 fix list has 5 or 6 fixes for memory leaks. I dealt with this battle why back when and this message points to a memory leak or memory pressure in memtoleave. You can also look at bumping up your memtoleave allocation to 386 MG. If you google you'll find lots of references on how do to that.

I'd suggest upgrade all the way to 8.00.2187 if you can.
Post #749819
Posted Wednesday, July 8, 2009 9:00 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, December 17, 2014 12:14 PM
Points: 176, Visits: 841
Upgrade to at least service pack 4. The sp 4 fix list has 5 or 6 fixes for memory leaks. I dealt with this battle why back when and this message points to a memory leak or memory pressure in memtoleave. You can also look at bumping up your memtoleave allocation to 386 MG. If you google you'll find lots of references on how do to that.

I'd suggest upgrade all the way to 8.00.2187 if you can.
Post #749820
Posted Wednesday, July 8, 2009 10:52 PM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Wednesday, December 17, 2014 9:58 AM
Points: 2,281, Visits: 4,241
After installing SQL Server 2000 SP4, there is also a hot fix needed in order to get AWE to function correctly: http://support.microsoft.com/kb/899761

SQL = Scarcely Qualifies as a Language
Post #749866
Posted Thursday, July 9, 2009 11:20 AM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Yesterday @ 3:44 PM
Points: 3,221, Visits: 2,375
Are you running 2000 Standard ot 2000 Enterprise ? If you are running SQL 2000 Standard then adding more memory to the server will not help since SQL 2000 Standard is 'limited' on the amount of memory it can address and use - 2 Gb !



Regards
Rudy Komacsar
Senior Database Administrator

"Ave Caesar! - Morituri te salutamus."
Post #750499
Posted Thursday, July 9, 2009 11:41 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, July 9, 2009 11:36 AM
Points: 2, Visits: 1
we are running sql2000 enterprise...we could not go to sp4 bec of the app running against it...our concern is that when we were using just 4 GB RAM we did not have this problem...however after expanding the RAM to 8, we started to have this issue...it seems something was not set right during the upgrade...
Post #750512
Posted Thursday, July 9, 2009 12:38 PM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Yesterday @ 3:44 PM
Points: 3,221, Visits: 2,375

hope this will help & make sense up to the extent that the information applies:

4GB RAM: /3GB (AWE support is not used)
8GB RAM: /3GB /PAE
16GB RAM: /3GB /PAE
16GB + RAM: /PAE

For 64bit SQL Server, use min-max memory after carefull consideration.
no need of /3GB or PAE in 64 bit hardware & software.

http://support.microsoft.com/kb/274750/
This one about large memory in windows
http://support.microsoft.com/kb/283037/
Another great post, is this one regarding memory management in general:
http://blogs.technet.com/askperf/archive/2007/03/23/memory-management-demystifying-3gb.aspx

http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx

http://www.microsoft.com/technet/prodtechnol/sql/2005/tsprfprb.mspx#EYIAC

http://msdn2.microsoft.com/en-us/library/Aa366718.aspx

http://msdn2.microsoft.com/en-us/library/ms190730.aspx





Regards
Rudy Komacsar
Senior Database Administrator

"Ave Caesar! - Morituri te salutamus."
Post #750549
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse