November 18, 2013 at 4:42 am
I did enable AWE last week, set max memory to 3G, then restarted SQL.
November 18, 2013 at 4:45 am
If you're going to add -g700, I would suggest dropping that to 2.5GB. Otherwise, 3GB for SQL buffer pool, 700MB for the MemToLeave, doesn't leave much for the OS.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 18, 2013 at 4:55 am
I notice now, a week later, Task Manager only shows SQLSERVR.EXE using 105 meg. I was expecting it to be much higher. Yet I still get errors trying to update 1 record through a linked server.
November 18, 2013 at 4:58 am
Task manager lies. Don't use task manager to check SQL Server's memory usage, it will often show far too low (limitation in Task Manager). Use performance monitor and the Total Server Memory counter.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 18, 2013 at 5:11 am
Not sure if I'm reading it correctly
"Total Server Memory (kb)" shows a flatline at "100" in the graph. The "last", "avg", "min" and "max" boxes all show 3.2 G.
That looks better.
November 18, 2013 at 5:15 am
homebrew01 (11/10/2013)
I rebooted this morning.I thought AWE was set correctly. I'll have to read up on it ... forgot the details.
I just ran:
sp_configure 'awe enabled', 1
RECONFIGURE
You also need to grant the sql server service account permission in the local secdurity policy "Lock pages in memory", without this AWE will not be enabled
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 18, 2013 at 5:18 am
homebrew01 (11/18/2013)
Not sure if I'm reading it correctly"Total Server Memory (kb)" shows a flatline at "100" in the graph. The "last", "avg", "min" and "max" boxes all show 3.2 G.
That looks better.
Right click -> scale selected counter.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 18, 2013 at 5:29 am
Perhaps tomorrow I will reduce SQL RAM to 2.5 G, and add the -g700 setting, then restart.
November 18, 2013 at 5:38 am
The Performance book mentioned earlier (page 136-137), and this site it pointed me to
http://msdn.microsoft.com/en-us/library/bb613473(v=vs.85).aspx
Say I should set /3GB in the boot.ini (Windows Server 2003, 32 bit, 4 Gig RAM total)
But doesn't perfmon show that SQL is already utilizing 3.2 G with me only enabling AWE and setting Max memory ?
November 18, 2013 at 8:21 am
homebrew01 (11/18/2013)
Perhaps tomorrow I will reduce SQL RAM to 2.5 G, and add the -g700 setting, then restart.
If you dont have AWE enabled correctly and you set the -g700 startup parameter, you're going to seriously restrict the buffer pools memory availability!
Why are you making references to AWE anyway when the OS in use will only support a max of 4GB RAM?
See this link for memory limits on Windows OS'
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 18, 2013 at 10:52 am
Perry Whittle (11/18/2013)
homebrew01 (11/18/2013)
Perhaps tomorrow I will reduce SQL RAM to 2.5 G, and add the -g700 setting, then restart.If you dont have AWE enabled correctly and you set the -g700 startup parameter, you're going to seriously restrict the buffer pools memory availability!
Why are you making references to AWE anyway when the OS in use will only support a max of 4GB RAM?See this link for memory limits on Windows OS'
Because I'm confused :unsure:
If I'm reading PerfMon correctly, SQL is currently using 3.2 G of RAM, which is good.
boot.ini has /PAE, but not /3gb
November 18, 2013 at 4:02 pm
homebrew01 (11/18/2013)
boot.ini has /PAE, but not /3gb
With your current OS and app config putting /PAE into the boot.ini has done little more than force you to reboot the server 😉
Windows 2003 R2 32 bit does not support more than 4GB RAM, period. PAE enables physical address extensions which allow the OS to address more than 4GB RAM, on 32 bit Windows it is an enterprise feature!
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 18, 2013 at 8:11 pm
I should have more clearly said that /PAE was already in the boot.ini, configured by my predecessor.
My goal is to make best use of the 4 G ram that I have, and address the apparent Linked Server issues I am having.
Sorry for my confusing posts.
November 18, 2013 at 10:21 pm
homebrew01 (11/18/2013)
My goal is to make best use of the 4 G ram that I have, and address the apparent Linked Server issues I am having.
Long-term recommendation - upgrade to 64-bit.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 18, 2013 at 11:52 pm
homebrew01 (11/18/2013)
My goal is to make best use of the 4 G ram that I have, and address the apparent Linked Server issues I am having.
As I said before then, setting -g700 startup param will restrict buffer pool available memory.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 15 posts - 16 through 30 (of 30 total)
You must be logged in to reply to this topic. Login to reply