Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


max memory setting SQL 2008 64 bit?


max memory setting SQL 2008 64 bit?

Author
Message
SQL Galaxy
SQL Galaxy
Ten Centuries
Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)

Group: General Forum Members
Points: 1218 Visits: 3465
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?
GilaMonster
GilaMonster
SSC-Forever
SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)

Group: General Forum Members
Points: 47198 Visits: 44367
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, MVP, M.Sc (Comp Sci)
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


SQL Galaxy
SQL Galaxy
Ten Centuries
Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)

Group: General Forum Members
Points: 1218 Visits: 3465
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?
GilaMonster
GilaMonster
SSC-Forever
SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)

Group: General Forum Members
Points: 47198 Visits: 44367
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, MVP, M.Sc (Comp Sci)
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


SQL Galaxy
SQL Galaxy
Ten Centuries
Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)

Group: General Forum Members
Points: 1218 Visits: 3465
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?
GilaMonster
GilaMonster
SSC-Forever
SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)

Group: General Forum Members
Points: 47198 Visits: 44367
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, MVP, M.Sc (Comp Sci)
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


SQL Galaxy
SQL Galaxy
Ten Centuries
Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)

Group: General Forum Members
Points: 1218 Visits: 3465
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
SQL Galaxy
SQL Galaxy
Ten Centuries
Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)

Group: General Forum Members
Points: 1218 Visits: 3465
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
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search