By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,856 Members | 2,163 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,856 IT Pros & Developers. It's quick & easy.

16 gig of memory (AWE or WSRM)

P: n/a
I have a Windows 2003 Enterprise Server with 16 gig of memory on board.

What is the best way to allow SQL Server 2000 to access that memory?

Should I turn on the AWE Memory and set a maximum?
Or Should I use the WSRM to "unlock" the lock addition memory?

Apparently, I can not do both as WSRM will not manage AWE Memory.

Any advice or early warnings you can assist me with before I play
around too much would be greatly appreciated.

Thank you in advance.

Jul 23 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Ray
If this server is dedicated to SQL Server then AWE is the way to go. WSRM
will only restrict processes and will not by itself allow SQL to use more
than 2GB of RAM. Since the server has exactly 16GB of RAM you might play
with the /3GB switch and AWE to maximize you memory use.

"brian" <bb********@PROvalUSA.com> wrote in message
news:11**********************@g14g2000cwa.googlegr oups.com...
I have a Windows 2003 Enterprise Server with 16 gig of memory on board.

What is the best way to allow SQL Server 2000 to access that memory?

Should I turn on the AWE Memory and set a maximum?
Or Should I use the WSRM to "unlock" the lock addition memory?

Apparently, I can not do both as WSRM will not manage AWE Memory.

Any advice or early warnings you can assist me with before I play
around too much would be greatly appreciated.

Thank you in advance.

Jul 23 '05 #2

P: n/a

"brian" <bb********@PROvalUSA.com> wrote in message
news:11**********************@g14g2000cwa.googlegr oups.com...
I have a Windows 2003 Enterprise Server with 16 gig of memory on board.

What is the best way to allow SQL Server 2000 to access that memory?

Should I turn on the AWE Memory and set a maximum?
Or Should I use the WSRM to "unlock" the lock addition memory?

Apparently, I can not do both as WSRM will not manage AWE Memory.

Any advice or early warnings you can assist me with before I play
around too much would be greatly appreciated.

Thank you in advance.


http://support.microsoft.com/default...b;en-us;274750

Simon
Jul 23 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.