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

max memory setting SQL 2008 64 bit? Expand / Collapse
Author
Message
Posted Thursday, August 23, 2012 4:19 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, October 16, 2014 6:03 AM
Points: 1,065, Visits: 3,028
Hi,

Operating system - Win server 2008 b4 bit enterprise edition
Version - SQL server 2008 R2 b4 bit enterprie edition
Physical Ram - 8GB

Server dedicated only running SQL 2008 R2, and single instance

Already configured the max memory 4.5 GB at SQL instance. but Sqlserver.exe using more than 5.5 GB in task manager.

what could be issues sqlserver not using under 4.5 GB memory even setting the max memory?

Post #1348991
Posted Thursday, August 23, 2012 4:33 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: Today @ 12:30 PM
Points: 40,154, Visits: 36,541
Not an issue, normal behaviour.

Max server memory sets the size of the buffer pool. There's also the non-buffer memory (CLR, linked server drivers, backup buffers, thread stacks, etc). That's allocated above and beyond the buffer pool. It's usually small, but that depends what you're doing. Lots of CLR and it'll be larger than normal.



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 #1348998
Posted Thursday, August 23, 2012 4:47 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, October 16, 2014 6:03 AM
Points: 1,065, Visits: 3,028
ok, understand why it is using more memory due to backup buffer, and thread stack..

In this server not enable CLR,
also Linked server not created..

each thread stack using 512 KB, so does thread stack should using under max memory only also inside buffer Pool?
Post #1349010
Posted Thursday, August 23, 2012 5:29 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: Today @ 12:30 PM
Points: 40,154, Visits: 36,541
No, thread stacks do not use memory in the buffer pool, they use the non-buffer memory.
CLR disabled does not mean no CLR. The system assemblies can still be used. There's a lot of other things that use the non-buffer memory as well.



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 #1349033
Posted Thursday, August 23, 2012 5:49 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, October 16, 2014 6:03 AM
Points: 1,065, Visits: 3,028
GilaMonster (8/23/2012)
No, thread stacks do not use memory in the buffer pool, they use the non-buffer memory.
CLR disabled does not mean no CLR. The system assemblies can still be used. There's a lot of other things that use the non-buffer memory as well.


Thanks for reply..

I forget to mention first post, I did lock page memory in this server. SQL server service account added into Local Security Policy Setting in 64bit system.

Can we posssible to check there is lot of other things that are using non-buffer memory?
Post #1349043
Posted Thursday, August 23, 2012 6:45 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: Today @ 12:30 PM
Points: 40,154, Visits: 36,541
iirc it's covered in chapter 4 of this: http://www.simple-talk.com/books/sql-books/troubleshooting-sql-server-a-guide-for-the-accidental-dba/


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 #1349071
Posted Friday, August 24, 2012 6:03 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, October 16, 2014 6:03 AM
Points: 1,065, Visits: 3,028
please confirm.

I thought my production server is settle under memory usages.

I did configuration as below

1. set the max memory 6GB (dedicated SQL machine), total 8 GB.

2. configured Lock page memory

(service account add to the Local Security Policy Setting, It is always required to configure at 64bit system) also which accounts can use a process to keep data in physical memory, preventing the system from paging the data to virtual memory on disk.


Now SQLSERVR.EXE process consuming only 89MB only in Task manager till last 4 days, as per current workload process.

Before not configured Lock page memory, that time SQLSERVR.EXE process consuming only 5.5GB and max memory setting 6GB.

thanks
Post #1349605
Posted Monday, August 27, 2012 12:50 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, October 16, 2014 6:03 AM
Points: 1,065, Visits: 3,028
please confirm.

I thought my production server is settle under memory usages.

I did configuration as below

1. set the max memory 6GB (dedicated SQL machine), total 8 GB.

2. configured Lock page memory

(service account add to the Local Security Policy Setting, It is always required to configure at 64bit system) also which accounts can use a process to keep data in physical memory, preventing the system from paging the data to virtual memory on disk.


Now SQLSERVR.EXE process consuming only 89MB only in Task manager till last 4 days, as per current workload process.

Before not configured Lock page memory, that time SQLSERVR.EXE process consuming only 5.5GB and max memory setting 6GB.

thanks


Post #1350221
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse