Welcome to dbForumz.com!
FAQFAQ    SearchSearch      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

SQL2005 Server 2003 Enterprise - memory options

 
   Database Forums (Home) -> Setup RSS
Next:  MSmerge_history - Production Issue  
Author Message
fred

External


Since: May 14, 2008
Posts: 8



(Msg. 1) Posted: Mon Nov 24, 2008 7:44 am
Post subject: SQL2005 Server 2003 Enterprise - memory options
Archived from groups: microsoft>public>sqlserver>setup (more info?)

Hi,

I have a server running Windows Server 2003 R2 Enterprise SP2, and SQL
Standard 2005 SP2. The server has 8GB RAM.

Should I need to tune the memory (in boot.ini or elsewhere), or will the
default settings be OK.

I think I am correct that I don't need the /PAE switch (since this is loaded
by default since 2003 SP1).

I understand a lot of it is load dependant, but just interested in any rules
of thumb..

My application has just returned a "query was unable to run due to
insufficient memory" error reported form the SQL client, so I guess something
is not right...!

Regards,

FD

 >> Stay informed about: SQL2005 Server 2003 Enterprise - memory options 
Back to top
Login to vote
Mark Han[MSFT]

External


Since: Aug 29, 2008
Posts: 20



(Msg. 2) Posted: Tue Nov 25, 2008 2:25 am
Post subject: RE: SQL2005 Server 2003 Enterprise - memory options [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Hi <customer name>,
Thank you for using Microsoft MSDN Managed Newsgroup. My name is Mark Han.
I am glad to work with you on this issue.

From your description, I understand that you recieve the following error
message and would like me to help to fix it. Is it correct? If I have
misunderstood, please let me know.
"query was unable to run due to insufficient memory"

Based on the current information, the issue seems to be a permance issue;
it might be a bit complex and take us long time to fix it.

To let the SQL Server use more monery, we need to do the following.
A if the SQL Server is 64-bit, the SQL Server will use as much momery as it
can

B if the SQL Server is 32-bit, by default, it use 2 GB. To use more memory,
we need to do the follinng.
1 Enable /PAE Switch in Boot.ini for SQL Servers with RAM > 4GB
Verify the /PAE switch is in the boot.ini file for all servers with
physical RAM > 4GB (reboot is required).
Sample boot.ini:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]

multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003,
Enterprise" /fastdetect /PAE

Note: /3GB and /PAE switches should NOT be used together on SQL servers
The purpose of this step is to make the Window Server use more than 4 GB
memory on 32-bit product.

2. sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
The goal of this step is to have the AWE switch on for SQL Server.

3. sp_configure 'min server memory', x(x means that the number you want to
set )
RECONFIGURE
GO
sp_configure 'max server memory', y(y means that the number you want
to set )
RECONFIGURE
GO
The goal of this step is to configure the memory you want the SQL to
use.

I believe that after you take these steps correctly, the SQL Server will
use more than 4 GB.
You can run the script below and look for min server memory and max server
memory to make sure.
select *
from sys.configurations

If the error still happens after taking the above, we need more information
to diagnosis the issue. So please send me a email. My email address is
v-fathan.TakeThisOut@online.microsoft.com(remove online) and then I will create a
workspace for you to upload the required files

If there is anything unclear, please o let me know.

Best regards,
Mark Han
Microsoft Online Community Support
===========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg.TakeThisOut@microsoft.com.
===========================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or
a Microsoft Support Engineer within 2 business day is acceptable. Please
note that each follow up response may take approximately
2 business days as the support professional working with you may need
further investigation to reach the most efficient resolution.
The offering is not appropriate for situations that require urgent,
real-time or phone-based interactions. Issues of this nature are
best handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/en-us/subscriptions/aa948874.aspx

============================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================

 >> Stay informed about: SQL2005 Server 2003 Enterprise - memory options 
Back to top
Login to vote
fred

External


Since: May 14, 2008
Posts: 8



(Msg. 3) Posted: Tue Nov 25, 2008 2:26 am
Post subject: RE: SQL2005 Server 2003 Enterprise - memory options [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Many thanks Mark,

I will work through this and keep you posted.

Regards.

"Mark Han[MSFT]" wrote:

> Hi <customer name>,
> Thank you for using Microsoft MSDN Managed Newsgroup. My name is Mark Han.
> I am glad to work with you on this issue.
>
> From your description, I understand that you recieve the following error
> message and would like me to help to fix it. Is it correct? If I have
> misunderstood, please let me know.
> "query was unable to run due to insufficient memory"
>
> Based on the current information, the issue seems to be a permance issue;
> it might be a bit complex and take us long time to fix it.
>
> To let the SQL Server use more monery, we need to do the following.
> A if the SQL Server is 64-bit, the SQL Server will use as much momery as it
> can
>
> B if the SQL Server is 32-bit, by default, it use 2 GB. To use more memory,
> we need to do the follinng.
> 1 Enable /PAE Switch in Boot.ini for SQL Servers with RAM > 4GB
> Verify the /PAE switch is in the boot.ini file for all servers with
> physical RAM > 4GB (reboot is required).
> Sample boot.ini:
> [boot loader]
> timeout=30
> default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
> [operating systems]
>
> multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003,
> Enterprise" /fastdetect /PAE
>
> Note: /3GB and /PAE switches should NOT be used together on SQL servers
> The purpose of this step is to make the Window Server use more than 4 GB
> memory on 32-bit product.
>
> 2. sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> The goal of this step is to have the AWE switch on for SQL Server.
>
> 3. sp_configure 'min server memory', x(x means that the number you want to
> set )
> RECONFIGURE
> GO
> sp_configure 'max server memory', y(y means that the number you want
> to set )
> RECONFIGURE
> GO
> The goal of this step is to configure the memory you want the SQL to
> use.
>
> I believe that after you take these steps correctly, the SQL Server will
> use more than 4 GB.
> You can run the script below and look for min server memory and max server
> memory to make sure.
> select *
> from sys.configurations
>
> If the error still happens after taking the above, we need more information
> to diagnosis the issue. So please send me a email. My email address is
> v-fathan.TakeThisOut@online.microsoft.com(remove online) and then I will create a
> workspace for you to upload the required files
>
> If there is anything unclear, please o let me know.
>
> Best regards,
> Mark Han
> Microsoft Online Community Support
> ===========================================================
> Delighting our customers is our #1 priority. We welcome your
> comments and suggestions about how we can improve the
> support we provide to you. Please feel free to let my manager
> know what you think of the level of service provided. You can
> send feedback directly to my manager at: msdnmg.TakeThisOut@microsoft.com.
> ===========================================================
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications.
>
> Note: MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or
> a Microsoft Support Engineer within 2 business day is acceptable. Please
> note that each follow up response may take approximately
> 2 business days as the support professional working with you may need
> further investigation to reach the most efficient resolution.
> The offering is not appropriate for situations that require urgent,
> real-time or phone-based interactions. Issues of this nature are
> best handled working with a dedicated Microsoft Support Engineer by
> contacting Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/en-us/subscriptions/aa948874.aspx
>
> ============================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
> =========================================================
>
>
 >> Stay informed about: SQL2005 Server 2003 Enterprise - memory options 
Back to top
Login to vote
fred

External


Since: May 14, 2008
Posts: 8



(Msg. 4) Posted: Tue Nov 25, 2008 12:11 pm
Post subject: RE: SQL2005 Server 2003 Enterprise - memory options [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Mark,

I am looking for guidance on the MIN and MAX settings for memory allocation.
Minimum seems to be fairly striaghtforward, I but have come across various
conflicting sources of information on the MAX setting.

Some say leave it to the default (2147483647MB)!, others say a sensible
limit should be set. Is this limit the total that SQL can use, or will SQL
also use Paging if an upper limit is reached?

In a server with a total of 8GB, running applications as well as SQL, I was
thinking of setting it to around 4096 (4GB). What does this actually mean?
What happens if SQL needs to use more than this 4GB - will it resort to
paging?

Regards,

FD
 >> Stay informed about: SQL2005 Server 2003 Enterprise - memory options 
Back to top
Login to vote
Mark Han[MSFT]

External


Since: Aug 29, 2008
Posts: 20



(Msg. 5) Posted: Wed Nov 26, 2008 3:25 am
Post subject: RE: SQL2005 Server 2003 Enterprise - memory options [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Hi FD,

Thank you for the update.

in order to address your concern, I would like to explain the following
1 The min server memory and max server memory configuration options
establish upper and lower limits to the amount of memory used by the buffer
pool of the Microsoft SQL Server Database Engine. The buffer pool does not
immediately acquire the amount of memory specified in min server memory.
The buffer pool starts with only the memory required to initialize. As the
Database Engine workload increases, it keeps acquiring the memory required
to support the workload. The buffer pool does not free any of the acquired
memory until it reaches the amount specified in min server memory. Once min
server memory is reached, the buffer pool then uses the standard algorithm
to acquire and free memory as needed. The only difference is that the
buffer pool never drops its memory allocation below the level specified in
min server memory, and never acquires more memory than the level specified
in max server memory.

2 There are two principal methods for setting the SQL Server memory options
manually:

In the first method, set min server memory and max server memory to the
same value. This value corresponds to the fixed amount of memory to
allocate to the SQL Server buffer pool after the value is reached.

In the second method, set min server memory and max server memory to span a
range of memory values. This method is useful where system or database
administrators want to configure an instance of SQL Server in conjunction
with the memory requirements of other applications that run on the same
computer.

Based on the above, the answer to your question:
Q: Is this limit the total that SQL can use,
A: Yes, the min server memory and max server memory configuration option
limit the total that SQL can use.

Q: or will SQL also use Paging if an upper limit is reached?
A: if you set the memory options manually, generally, SQL won't paging once
an upper limit is reached.

Q: In a server with a total of 8GB, running applications as well as SQL, I
was thinking of setting it to around 4096 (4GB). What does this actually
mean? What happens if SQL needs to use more than this 4GB - will it
resort to paging?
A: If you would like to completely rang the memory the SQL can use, you can
use max/min memory to set the rang. If you manually set the max memory(4
GB) of the SQL Server, when SQL needs to use more than this 4GB, SQL won't
acquires more memory.

Hope the above helpful.

Best regards,
Mark Han
Microsoft Online Community Support
=========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg DeleteThis @microsoft.com.
=========================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================
 >> Stay informed about: SQL2005 Server 2003 Enterprise - memory options 
Back to top
Login to vote
fred

External


Since: May 14, 2008
Posts: 8



(Msg. 6) Posted: Wed Nov 26, 2008 3:25 am
Post subject: RE: SQL2005 Server 2003 Enterprise - memory options [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

That's great, thanks for the explanation Mark.

"Mark Han[MSFT]" wrote:

> Hi FD,
>
> Thank you for the update.
>
> in order to address your concern, I would like to explain the following
> 1 The min server memory and max server memory configuration options
> establish upper and lower limits to the amount of memory used by the buffer
> pool of the Microsoft SQL Server Database Engine. The buffer pool does not
> immediately acquire the amount of memory specified in min server memory.
> The buffer pool starts with only the memory required to initialize. As the
> Database Engine workload increases, it keeps acquiring the memory required
> to support the workload. The buffer pool does not free any of the acquired
> memory until it reaches the amount specified in min server memory. Once min
> server memory is reached, the buffer pool then uses the standard algorithm
> to acquire and free memory as needed. The only difference is that the
> buffer pool never drops its memory allocation below the level specified in
> min server memory, and never acquires more memory than the level specified
> in max server memory.
>
> 2 There are two principal methods for setting the SQL Server memory options
> manually:
>
> In the first method, set min server memory and max server memory to the
> same value. This value corresponds to the fixed amount of memory to
> allocate to the SQL Server buffer pool after the value is reached.
>
> In the second method, set min server memory and max server memory to span a
> range of memory values. This method is useful where system or database
> administrators want to configure an instance of SQL Server in conjunction
> with the memory requirements of other applications that run on the same
> computer.
>
> Based on the above, the answer to your question:
> Q: Is this limit the total that SQL can use,
> A: Yes, the min server memory and max server memory configuration option
> limit the total that SQL can use.
>
> Q: or will SQL also use Paging if an upper limit is reached?
> A: if you set the memory options manually, generally, SQL won't paging once
> an upper limit is reached.
>
> Q: In a server with a total of 8GB, running applications as well as SQL, I
> was thinking of setting it to around 4096 (4GB). What does this actually
> mean? What happens if SQL needs to use more than this 4GB - will it
> resort to paging?
> A: If you would like to completely rang the memory the SQL can use, you can
> use max/min memory to set the rang. If you manually set the max memory(4
> GB) of the SQL Server, when SQL needs to use more than this 4GB, SQL won't
> acquires more memory.
>
> Hope the above helpful.
>
> Best regards,
> Mark Han
> Microsoft Online Community Support
> =========================================================
> Delighting our customers is our #1 priority. We welcome your
> comments and suggestions about how we can improve the
> support we provide to you. Please feel free to let my manager
> know what you think of the level of service provided. You can
> send feedback directly to my manager at: msdnmg RemoveThis @microsoft.com.
> =========================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
> =========================================================
>
>
 >> Stay informed about: SQL2005 Server 2003 Enterprise - memory options 
Back to top
Login to vote
Display posts from previous:   
   Database Forums (Home) -> Setup All times are: Pacific Time (US & Canada)
Page 1 of 1

 
You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]