AWE, 3GB and SQL Boost

Please help. Just installed the SQL 2005 enterprise on 2003 standard server with /3GB switch.
Now, in SQL there is an AWE option. Do I need to check that off and where do I set the memory manualy and not dinamicly?
Also, do I boost SQL priority in processors?
Can you please help and give some other tunning pointers? I set couple of boxes with 2000 SQL and always used 3GB switch but forgot the priority on processors and other fine tunning steps. Thanks in advance.George,
How much memory do you have on the server? How much do you want to give to
SQL?
Chris
"George" <George@.discussions.microsoft.com> wrote in message
news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> Please help. Just installed the SQL 2005 enterprise on 2003 standard
> server
> with /3GB switch.
> Now, in SQL there is an AWE option. Do I need to check that off and where
> do
> I set the memory manualy and not dinamicly?
> Also, do I boost SQL priority in processors?
> Can you please help and give some other tunning pointers? I set couple of
> boxes with 2000 SQL and always used 3GB switch but forgot the priority on
> processors and other fine tunning steps. Thanks in advance.
>|||4GB on the server and 3GB to SQL
"Chris Wood" wrote:

> George,
> How much memory do you have on the server? How much do you want to give to
> SQL?
> Chris
> "George" <George@.discussions.microsoft.com> wrote in message
> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
>
>|||George,
On server 2003 the switches should be set by the O/S. You will need to
configure AWE using sp_configure and then set max and min memory. I would
try with 2.5Gb first before you see if you can move up to 3Gb.
Chris
"George" <George@.discussions.microsoft.com> wrote in message
news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...[vbcol=seagreen]
> 4GB on the server and 3GB to SQL
> "Chris Wood" wrote:
>|||Ok. So
1. Set the 3GB switch in Boot.ini (did this before SQL installation)
2. Run the sp_configure and set it to 2.5
Please confirm. Also, is that check for AWE in GUI same as the sp command
via QA?
"Chris Wood" wrote:

> George,
> On server 2003 the switches should be set by the O/S. You will need to
> configure AWE using sp_configure and then set max and min memory. I would
> try with 2.5Gb first before you see if you can move up to 3Gb.
> Chris
> "George" <George@.discussions.microsoft.com> wrote in message
> news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
>
>|||Yes, checking and applying the 'Use AWE to allocate memory' checkbox is the
same as executing the following T-SQL code:
EXEC sys.sp_configure N'awe enabled', N'1'
RECONFIGURE WITH OVERRIDE
BTW, you almost never should boost the SQL process priority. In fact, Books
Online comes with the following warning:
"Raising the priority too high may drain resources from essential operating
system and network functions, resulting in problems shutting down SQL Server
or using other operating system tasks on the server."
Linchi
"George" wrote:
[vbcol=seagreen]
> Ok. So
> 1. Set the 3GB switch in Boot.ini (did this before SQL installation)
> 2. Run the sp_configure and set it to 2.5
> Please confirm. Also, is that check for AWE in GUI same as the sp command
> via QA?
> "Chris Wood" wrote:
>|||Thank you. I checked my prvious installations and you are right. I don't hav
e
it on.
Now, as far as 3GB goes, do I keep it in the boot.ini and do I need some
other switch in addition?
If I put same valuses in both min and max memory, would that mean it is now
FIXED MEMORY SIZE assigned vs dynamically when there is a range?
SQL 2000 had a slider and a check box to choose from fixed and dynamyc (I am
sure you know of that just making a point)
"Linchi Shea" wrote:
[vbcol=seagreen]
> Yes, checking and applying the 'Use AWE to allocate memory' checkbox is th
e
> same as executing the following T-SQL code:
> EXEC sys.sp_configure N'awe enabled', N'1'
> RECONFIGURE WITH OVERRIDE
> BTW, you almost never should boost the SQL process priority. In fact, Book
s
> Online comes with the following warning:
> "Raising the priority too high may drain resources from essential operatin
g
> system and network functions, resulting in problems shutting down SQL Serv
er
> or using other operating system tasks on the server."
> Linchi
> "George" wrote:
>|||Can anyone please confirm I should keep the 3GB in boot.ini and enable AWE i
n
SQL?
"Linchi Shea" wrote:
[vbcol=seagreen]
> Yes, checking and applying the 'Use AWE to allocate memory' checkbox is th
e
> same as executing the following T-SQL code:
> EXEC sys.sp_configure N'awe enabled', N'1'
> RECONFIGURE WITH OVERRIDE
> BTW, you almost never should boost the SQL process priority. In fact, Book
s
> Online comes with the following warning:
> "Raising the priority too high may drain resources from essential operatin
g
> system and network functions, resulting in problems shutting down SQL Serv
er
> or using other operating system tasks on the server."
> Linchi
> "George" wrote:
>|||Chris, thanks. I can not go higher than 2.1 GB. Please help.
"Chris Wood" wrote:

> George,
> On server 2003 the switches should be set by the O/S. You will need to
> configure AWE using sp_configure and then set max and min memory. I would
> try with 2.5Gb first before you see if you can move up to 3Gb.
> Chris
> "George" <George@.discussions.microsoft.com> wrote in message
> news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
>
>|||George,
Have you seen this:- http://support.microsoft.com/kb/283037/en-us
Chris
"George" <George@.discussions.microsoft.com> wrote in message
news:F90DAA9C-1226-4E6F-9445-D4C3696A4556@.microsoft.com...[vbcol=seagreen]
> Chris, thanks. I can not go higher than 2.1 GB. Please help.
> "Chris Wood" wrote:
>