March 28, 2008 at 1:47 pm
I've read a bunch of conflicting views of the above. Here's my scenario - Moving SQL 2000 sp4 from a Win2K server to a Win2K3 Advanced Server with 8Gb of RAM. I want to allocate 6Gb for SQL. I've read that I don't need to put PAE in the boot.ini file if we have hot-add memory as it's already enabled. We don't have this feature so I'm guessing I do need to add /PAE to the ini file. Do I also need the /3GB switch added as well? I swear I've read (but cannot find again) that the /3GB switch will cause issues when combined with PAE. The account that runs SQL has the "Lock pages in memory" enabled so I'm fine there. Do I need to turn awe on within SQL? Of course I'm looking for this biggest bang for my buck and want to ensure my configuration is optimal. Anyone have thoughts on this? TIA
-- You can't be late until you show up.
March 28, 2008 at 2:07 pm
first of all you'll need sql2000 enterprise edition !
This is the ref I always use : http://www.sql-server-performance.com/articles/per/awe_memory_sql2000_p1.aspx
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
March 28, 2008 at 2:17 pm
Sorry, missed that part. We are running SQL2K Enterprise Edition, sp4+. I've seen this article and we actually used it on our Win2K server. But now that were moving to Win2K3, I assumed (there's that word!) that there would be differences with the settings? Did I ASSUME incorrectly?
-- You can't be late until you show up.
March 29, 2008 at 12:49 pm
You need the /pae switch (to enable AWE memory at the OS level), but you do not want the /3GB switch (which limits the kernel to only 1 GB of address space. Not healthy with large amounts of memory)
You then need to switch AWE on in SQL, so that SQL can use more than 2 GB memory.
This is assuming it's a 32 bit server. If it's a 64 bit server you need none of the above.
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
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply