Hello,
I need some assistance configuring SQL 2005 running on an 8GB server running
Windows 2003 Enterprise. I've read some of the SQL 2005 documentation, but
I'm still confused as to what I need to do. Given this configuration, do I
need to do anything for SQL 2005 to be able to utilize the 8GB of RAM, and i
f
I do, what exactly needs to be done? Sorry, I'm a newbie when it comes to SQ
L
2005.
Thanks."Marks70" <Marks70@.discussions.microsoft.com> wrote in message
news:28A505B8-A98A-4394-8802-F04AC63E72B5@.microsoft.com...
> Hello,
> I need some assistance configuring SQL 2005 running on an 8GB server
> running
> Windows 2003 Enterprise. I've read some of the SQL 2005 documentation, but
> I'm still confused as to what I need to do. Given this configuration, do I
> need to do anything for SQL 2005 to be able to utilize the 8GB of RAM, and
> if
> I do, what exactly needs to be done? Sorry, I'm a newbie when it comes to
> SQL
> 2005.
>
When running 64bit Windows and 64bit SQL Server, nothing special needs to be
done.
On 32bit Windows, or when running 32bit SQL Server on 64bit Windows, see the
following BOL topic:
Using AWE
http://msdn2.microsoft.com/en-us/library/ms175581.aspx
However, AWE has a performance penalty, so you might be better off just
using the /3GB switch and limiting SQL Server to non-AWE memory. Basically
each server workload will, at some point, experience a diminishing
performance return for incremental memory addition. Under load, measure the
SQLServer:Buffer Manager: Page reads/sec. If adding memory stops materially
affecting this number at or below 3GB, you probably don't want to use AWE.
David
Tuesday, 14 February 2012
Configuring Memory for SQL 2005 Standard on Windows 2003 Enterpris
Labels:
8gb,
assistance,
configuring,
database,
enterpris,
enterprise,
memory,
microsoft,
mysql,
oracle,
running,
runningwindows,
server,
sql,
standard,
windows
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment