sql2k sp4 awe fix
-
Hi,
Just read the download page for sql2k sp4 with this addition :
Running Address Windowing Extensions (AWE) with SQL Server 2000 SP4
Important We have found an issue with the final build of SQL Server 2000 SP4 that affects customers who run SQL Server with AWE support enabled. This issue does not affect the Itanium-based computers or other components of SQL Server beyond the relational databases, such as SQL Server 2000 Analysis Services, SQL Server 2000 Reporting Services, and SQL Server 2000 Notification Services. This issue only affects computers that have more than 2 GB of memory where AWE has been enabled and where more than half of the total system memory is being allocated to a single instance of SQL Server. Customers who have this configuration should apply the hotfix in the following Microsoft Knowledge Base article after they upgrade to SQL Server 2000 SP4:
899761 FIX: Not all memory is available when AWE is enabled on a computer that is running a 32-bit version of SQL Server 2000 SP4I hope this solves the issue
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
-
Thanks, We've been waiting for quite some time...
-
Has anyone installed this hotfix? I downloaded it & tried to install it but it says it doesn't find any valid installations that it is used for.
Our machine is win 2k Advanced server with SQL Enterprise Edition 32 bit w/4 Gbs of memory. I am pretty sure we fit the requirements for the hotfix. So I am not sure what is going on.
Has anyone else run into this issue?
John
-
No you may not fit it because before Windows 2003 you need a special Intel chip to enable it but Windows 2003 comes with a configuration to reduce the need for the Intel chip. One more thing service packs are .sql files Windows use as needed. Try it on a sand box you can actually count how many Windows use based on your configurations. Hope this helps.
Kind regards,
Gift Peddie
Kind regards,
Gift Peddie -
Gift,
What are you referring to when you say you need a special Intel chip to enable "it"? What is it?
Thanks,
John
-
I was referring to AWE it comes with big boxes like Unisy 8way or 32way but most standard boxes you have to add it in your optional list of hardware.
Kind regards,
Gift Peddie
Kind regards,
Gift Peddie -
Gift,
As far as I know, the only requirement for AWE is that you have more than 2 or 3 GB of RAM. We currently have AWE enabled on our server and it is a 2 way. So I think your info is incorrect.
Thanks,
John
-
John,
when you only have 4 Gb ram on your server AWE would be overhead because you should only use /3gb switch in the boot.ini
Have a look at http://www.sql-server-performance.com/awe_memory.asp
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
-
Thanks for the link! A very informative article. So currently I should disable AWE & put the /3GB switch in the boot.ini. In the near future we hope to put another 4 GB into the server. Then should I take the /3GB switch out of the boot.ini & enable AWE or should I add the /PAE switch to the boot.ini? I wasn't clear on that from the article.
Thanks,
John
-
Actually, AWE would not even be used. SQL Server would ignore it when starting on a server with <=4GB RAM.
-
When you have 8Gb ram you should alter your boot.ini to use /3Gb _and_ /pae and _not_enable AWE !
This is what we have in the boot.ini :
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Advanced Server 3GB PAE" /fastdetect /3GB /pae
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
-
Ok, thanks for correcting me on this! This is my first experience with needing to use any of these switches. The server we are working on had the AWE enabled by my co-worker so I just assumed that was the correct way to do it.
So this is the reason that the hotfix said I did not have an installation that fit its requirement. Even though AWE was enabled, SQL was really ignoring it. Since it was ignoring it, SQL was only seeing 2 GB of the 4 GB correct? This may give us a performance boost by using the /3gb switch instead.
Thanks again,
John
-
correct.
HTH
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
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply