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 12»»

Confused on memory Expand / Collapse
Author
Message
Posted Tuesday, December 2, 2008 12:57 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Friday, February 11, 2011 8:31 PM
Points: 297, Visits: 277
hi m having a server which has 20 gb ram i hav give the 15 gb(max memory) to sqlserver but wen i check in wth permon total memory show on 3.5 GB...
Post #611853
Posted Tuesday, December 2, 2008 2:44 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Friday, February 11, 2011 8:31 PM
Points: 297, Visits: 277
waiting for the suggestions..........
Post #611900
Posted Tuesday, December 2, 2008 2:45 AM
SSC-Enthusiastic

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

Group: General Forum Members
Last Login: Tuesday, September 6, 2011 7:51 AM
Points: 105, Visits: 581
What version of SQL / Windoze are you running, 32-bit or 64-bit?
What are your memory settings for AWE, boot.ini and so on?
Post #611901
Posted Tuesday, December 2, 2008 3:13 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Monday, October 6, 2014 3:58 AM
Points: 1,202, Visits: 1,941
Dear

what is AWE?

Plz tell ....

Thanx


Thanks

Post #611920
Posted Tuesday, December 2, 2008 3:24 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, March 13, 2014 5:49 AM
Points: 1,391, Visits: 608
guptaajay1985 (12/2/2008)
Dear

what is AWE?

Plz tell ....

Thanx


see the link:
http://support.microsoft.com/default.aspx/kb/274750
http://msdn.microsoft.com/en-us/library/ms175581.aspx



Post #611927
Posted Tuesday, December 2, 2008 3:37 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Monday, October 6, 2014 3:58 AM
Points: 1,202, Visits: 1,941
Thanx Dear..

Thanks

Post #611930
Posted Wednesday, December 3, 2008 6:04 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Today @ 2:09 PM
Points: 4,400, Visits: 6,261
SQL Server only takes memory as it is needed. Perhaps you only have (or access) a few GBs of data?

Best,

Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru at GMail
Post #612762
Posted Wednesday, December 3, 2008 8:32 AM


SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Today @ 8:02 AM
Points: 644, Visits: 2,140
Read the previously posted articles, but a quick summary:

1. If you have 64-bit windows, skip this step and go to step 2. If you have 32-bit Windows, right click on the server in object explorer and click Properties. Select the Memory page and make sure AWE is checked (as well as adjusting your memory to desired settings). Save and close.

2. Go to Administrative Tools -> Local Security Policy and inside the window, select Local Policies -> User Rights Assignment.s You will see a whole list of policies on the right hand side. The one you need is Lock pages in Memory. Double click on it and add the service account(s) you are running your SQL Server instance(s) as.

NOTE: This will involve restarting your SQL Service to become effective, so if this is a production environment, beware of that.

This is the quick and dirty version of setting up AWE and Lock Pages in Memory, but read the articles to get a thorough introduction before proceeding.


Gaby
________________________________________________________________
"In theory, theory and practice are the same. In practice, they are not."
- Albert Einstein
Post #612898
Posted Wednesday, December 3, 2008 9:00 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Friday, June 27, 2014 12:43 PM
Points: 13,872, Visits: 9,596
And, of course, if you're using a "Standard" version of Windows Server, you can't address that much RAM anyway.

- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Post #612928
Posted Wednesday, December 3, 2008 10:34 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Today @ 2:09 PM
Points: 4,400, Visits: 6,261
Gaby Abed (12/3/2008)
Read the previously posted articles, but a quick summary:

1. If you have 64-bit windows, skip this step and go to step 2. If you have 32-bit Windows, right click on the server in object explorer and click Properties. Select the Memory page and make sure AWE is checked (as well as adjusting your memory to desired settings). Save and close.

2. Go to Administrative Tools -> Local Security Policy and inside the window, select Local Policies -> User Rights Assignment.s You will see a whole list of policies on the right hand side. The one you need is Lock pages in Memory. Double click on it and add the service account(s) you are running your SQL Server instance(s) as.

NOTE: This will involve restarting your SQL Service to become effective, so if this is a production environment, beware of that.

This is the quick and dirty version of setting up AWE and Lock Pages in Memory, but read the articles to get a thorough introduction before proceeding.


1) if 32 bit you would also need /PAE in the boot.ini file, right?

2) IIRC Lock pages in memory is only useful for SQL Server Enterprise Edition.


Best,

Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru at GMail
Post #613017
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse