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 «««1234»»

More Memory Expand / Collapse
Author
Message
Posted Monday, April 14, 2014 12:04 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 2:01 PM
Points: 40,390, Visits: 36,823
DaveK2014 (4/14/2014)
I Tried running each one separate and all of them together and they give the same errors see attached. Maybe I have something wrong.


Looks like someone has tried to enable direct updates to the system tables.

Run this:
EXEC sp_configure 'allow updates', 0
RECONFIGURE

Then try running Keith's queries again.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1561618
Posted Monday, April 14, 2014 1:07 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, September 18, 2014 10:14 AM
Points: 36, Visits: 52
after running the allow updates to zero I get this

Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
Msg 5845, Level 16, State 1, Line 2
Address Windowing Extensions (AWE) requires the 'lock pages in memory' privilege which is not currently present in the access token of the process.

I have added the lock pages in group policy to my account but I am thinking that might not be the right account to set it on. My Sql server services run on the same account as the lock pages was set to.
Post #1561649
Posted Monday, April 14, 2014 4:40 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 2:01 PM
Points: 40,390, Visits: 36,823
EXEC sp_configure 'AWE Enabled',0
RECONFIGURE

It shouldn't be on for a 64-bit process.
Looks like someone's been playing fast and loose with your config settings.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1561690
Posted Thursday, April 17, 2014 9:16 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, November 11, 2014 9:22 AM
Points: 216, Visits: 1,372
Keith Tate (4/14/2014)

...
Second if you want it to take 7GB of memory then set the "min server memory" and it will take that amount of memory.
...



Actually, the Min Memory setting is a 'floor' setting, in that SQL will only hold the minimum amount of memory once it has breached that minimum value - in your quote, Keith, 7GB. Until then, ie, until SQL actually takes up 7GB or more, SQL will only use the memory it needs, it does not initially grab all 7GB - see technet article.
Post #1562712
Posted Thursday, April 17, 2014 9:56 AM


Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: 2 days ago @ 7:09 PM
Points: 593, Visits: 931
That is correct, I guess I should have stated that if you want to have 7 GB, after SQL Server has acquired at least 7 GB for the buffer pool then it won't release below 7 GB of memory, but it seemed wordy

But you are right it was misleading my bad.




Microsoft Certified Master - SQL Server 2008
Follow me on twitter: @keith_tate

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1562740
Posted Tuesday, May 6, 2014 9:58 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, September 18, 2014 10:14 AM
Points: 36, Visits: 52
I am still looking for some more help on this if anyone has some more ideas.

So just to go over it again we have Server 2008R2 running a 32bit version of sql 2008.

We turned on AWE set the min to 0 and max to 6144Megs.

I checked the account running our sql server service and set Lock page file in memory and perform file maintenance task to the same account.

Reboot the sql server.

Now sql is using 200 Megs of data, the server has about 8 gigs available but the page file is using 8+ gigs.

Any thoughts?

Thanks again.
Post #1568055
Posted Tuesday, May 6, 2014 10:41 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 2:01 PM
Points: 40,390, Visits: 36,823
SQL doesn't use the page file.

How are you checking its size and how is the page file configured? (and why are you concerned about its size?)



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1568087
Posted Tuesday, May 6, 2014 10:44 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, September 18, 2014 10:14 AM
Points: 36, Visits: 52
Just using task manager to see the PF size.

our sql server was using upwards of 3.8 gigs now its down to 200 megs so that should be slightly concerning wouldn't you think?
Post #1568089
Posted Tuesday, May 6, 2014 10:54 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 2:01 PM
Points: 40,390, Visits: 36,823
What do you mean by '200MB of data' and where are you seeing that?


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1568094
Posted Tuesday, May 6, 2014 10:59 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, September 18, 2014 10:14 AM
Points: 36, Visits: 52
Sorry that's the memory usage showing for the Sqlserver.exe in Task manager. Since its 64bit its a bit more accurate then the 32bit os. I also checked in process monitor and it is showing 200 megs as well.

We want to make sure Sql can use as much memory as it wants up to the 6 gigs max we set.
Post #1568096
« Prev Topic | Next Topic »

Add to briefcase «««1234»»

Permissions Expand / Collapse