Autonumber field: enable

Showing posts with label enable. Show all posts

Thursday, March 8, 2012

AWE on SQL Server 2000 & 2005

I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
2000 Enterprose I would like to use AWE,
to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
I have windows2003 server 32 bit version, 16Gb ram on it, running inder SQL
2005 Enterprose I would like to use AWE,
to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
SQL serer DBAYou need the /PAE switch although Win2003 may automatically add it for you.
The /3GB can not be used with 16GB but can with 8GB. It is up to you if you
need the extra directly addressable memory or not. IN either case you will
also need to enable AWE in SQL Server.
Andrew J. Kelly SQL MVP
"Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
> 2000 Enterprose I would like to use AWE,
> to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> I have windows2003 server 32 bit version, 16Gb ram on it, running inder
> SQL
> 2005 Enterprose I would like to use AWE,
> to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> --
> SQL serer DBA|||And if you enable AWE in SQL Server without the PAE switch being on, you
aren't going to get anything. The PAE switch causes a different NT kernel
to be loaded which contains the code to manipulate memory addresses above
the 32 bit address space. Keep in mind that AWE is for data only. No
executable code can exist outside of the 32 bit address space. It's
actually quite rare to have an application with memory pressure due to data
alone.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eoJ8YgtGGHA.312@.TK2MSFTNGP09.phx.gbl...
> You need the /PAE switch although Win2003 may automatically add it for
> you. The /3GB can not be used with 16GB but can with 8GB. It is up to you
> if you need the extra directly addressable memory or not. IN either case
> you will also need to enable AWE in SQL Server.
> --
> Andrew J. Kelly SQL MVP
>
> "Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
> news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>

AWE on SQL Server 2000 & 2005

I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
2000 Enterprose I would like to use AWE,
to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
I have windows2003 server 32 bit version, 16Gb ram on it, running inder SQL
2005 Enterprose I would like to use AWE,
to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
SQL serer DBA
You need the /PAE switch although Win2003 may automatically add it for you.
The /3GB can not be used with 16GB but can with 8GB. It is up to you if you
need the extra directly addressable memory or not. IN either case you will
also need to enable AWE in SQL Server.
Andrew J. Kelly SQL MVP
"Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
> 2000 Enterprose I would like to use AWE,
> to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> I have windows2003 server 32 bit version, 16Gb ram on it, running inder
> SQL
> 2005 Enterprose I would like to use AWE,
> to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> --
> SQL serer DBA
|||And if you enable AWE in SQL Server without the PAE switch being on, you
aren't going to get anything. The PAE switch causes a different NT kernel
to be loaded which contains the code to manipulate memory addresses above
the 32 bit address space. Keep in mind that AWE is for data only. No
executable code can exist outside of the 32 bit address space. It's
actually quite rare to have an application with memory pressure due to data
alone.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eoJ8YgtGGHA.312@.TK2MSFTNGP09.phx.gbl...
> You need the /PAE switch although Win2003 may automatically add it for
> you. The /3GB can not be used with 16GB but can with 8GB. It is up to you
> if you need the extra directly addressable memory or not. IN either case
> you will also need to enable AWE in SQL Server.
> --
> Andrew J. Kelly SQL MVP
>
> "Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
> news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>

AWE on SQL Server 2000 & 2005

I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
2000 Enterprose I would like to use AWE,
to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
I have windows2003 server 32 bit version, 16Gb ram on it, running inder SQL
2005 Enterprose I would like to use AWE,
to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
--
SQL serer DBAYou need the /PAE switch although Win2003 may automatically add it for you.
The /3GB can not be used with 16GB but can with 8GB. It is up to you if you
need the extra directly addressable memory or not. IN either case you will
also need to enable AWE in SQL Server.
--
Andrew J. Kelly SQL MVP
"Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
> 2000 Enterprose I would like to use AWE,
> to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> I have windows2003 server 32 bit version, 16Gb ram on it, running inder
> SQL
> 2005 Enterprose I would like to use AWE,
> to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> --
> SQL serer DBA|||And if you enable AWE in SQL Server without the PAE switch being on, you
aren't going to get anything. The PAE switch causes a different NT kernel
to be loaded which contains the code to manipulate memory addresses above
the 32 bit address space. Keep in mind that AWE is for data only. No
executable code can exist outside of the 32 bit address space. It's
actually quite rare to have an application with memory pressure due to data
alone.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eoJ8YgtGGHA.312@.TK2MSFTNGP09.phx.gbl...
> You need the /PAE switch although Win2003 may automatically add it for
> you. The /3GB can not be used with 16GB but can with 8GB. It is up to you
> if you need the extra directly addressable memory or not. IN either case
> you will also need to enable AWE in SQL Server.
> --
> Andrew J. Kelly SQL MVP
>
> "Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
> news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>>I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
>> 2000 Enterprose I would like to use AWE,
>> to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
>> please let me know if any one have this information.
>>
>> I have windows2003 server 32 bit version, 16Gb ram on it, running inder
>> SQL
>> 2005 Enterprose I would like to use AWE,
>> to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
>> please let me know if any one have this information.
>>
>> --
>> SQL serer DBA
>

Wednesday, March 7, 2012

AWE got 0, said DBCC MEMORYSTATUS...

I have done these steps to config and enable AWE. But, DBCC MEMORYSTATUS
still show AWE=0 on everywhere, liked Memory Manager, Memory node Id =0, etc
.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
-- restart the sql
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'min server memory', 1024
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
The box is a:
Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
Mar 23 2007 16:28:52
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
That's a WinServer 2003 64-bit.
Physical_memory_in_bytes virtual_memory_in_bytes bpool_committed
bpool_commit_target bpool_visible
-- -- --
-- --
8584736768 2147352576 5280 199912
199912
Am I doing it right? How to verify my stuff are consuming memory from the
AWE?
Thanks.You can use Performance on Windows and verify Memory Manager, Total Server
Memory.
Check your SQL Server log when the instance was started, there must be a
'Address Windowing Extensions enabled' message. If AWE was not succesfully
started there must be a related error message.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"light_wt" wrote:

>

> I have done these steps to config and enable AWE. But, DBCC MEMORYSTATUS
> still show AWE=0 on everywhere, liked Memory Manager, Memory node Id =0, e
tc.
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> -- restart the sql
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'min server memory', 1024
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
> The box is a:
> Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
> Mar 23 2007 16:28:52
> Copyright (c) 1988-2005 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
> That's a WinServer 2003 64-bit.
> Physical_memory_in_bytes virtual_memory_in_bytes bpool_committed
> bpool_commit_target bpool_visible
> -- -- --
> -- --
> 8584736768 2147352576 5280 199912
> 199912
> Am I doing it right? How to verify my stuff are consuming memory from the
> AWE?
> Thanks.
>|||Did you add your SQL Server service account to "Lock pages in memory" list
before performing this action?
Otherwise, it would not let you set AWE enable.
How to: Enable the Lock Pages in Memory Option (Windows):
http://msdn2.microsoft.com/en-us/library/ms190730.aspx
Ekrem ?nsoy
"light_wt" <lightwt@.discussions.microsoft.com> wrote in message
news:2217E528-6E89-4C83-987C-FAA270A30FE3@.microsoft.com...
>

> I have done these steps to config and enable AWE. But, DBCC MEMORYSTATUS
> still show AWE=0 on everywhere, liked Memory Manager, Memory node Id =0,
> etc.
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> -- restart the sql
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'min server memory', 1024
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
> The box is a:
> Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
> Mar 23 2007 16:28:52
> Copyright (c) 1988-2005 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
> That's a WinServer 2003 64-bit.
> Physical_memory_in_bytes virtual_memory_in_bytes bpool_committed
> bpool_commit_target bpool_visible
> -- -- --
> -- --
> 8584736768 2147352576 5280 199912
> 199912
> Am I doing it right? How to verify my stuff are consuming memory from the
> AWE?
> Thanks.
>|||Also, there are AWE specific counters under SQLServer:Buffer Manager. Take a
look at these AWE counters to see if there are any AWE-related memory
activities.
Linchi
"light_wt" wrote:

>

> I have done these steps to config and enable AWE. But, DBCC MEMORYSTATUS
> still show AWE=0 on everywhere, liked Memory Manager, Memory node Id =0, e
tc.
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> -- restart the sql
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'min server memory', 1024
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
> The box is a:
> Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
> Mar 23 2007 16:28:52
> Copyright (c) 1988-2005 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
> That's a WinServer 2003 64-bit.
> Physical_memory_in_bytes virtual_memory_in_bytes bpool_committed
> bpool_commit_target bpool_visible
> -- -- --
> -- --
> 8584736768 2147352576 5280 199912
> 199912
> Am I doing it right? How to verify my stuff are consuming memory from the
> AWE?
> Thanks.
>|||thanks everyone for your ideas.
i've look at the SQL Server Log, after the instances started, the AWE is
enable.
i've check the userid who can do Lock Memory and is the same perosn who own
the Job.
in perfmon, I have added all AWE-related counters in SQLServer:Buffer
Manager
and changed the vertical counter to 5.
nothing happen. AWE got 0.
Am I missing something?
thanks.

AWE got 0, said DBCC MEMORYSTATUS...

I have done these steps to config and enable AWE. But, DBCC MEMORYSTATUS
still show AWE=0 on everywhere, liked Memory Manager, Memory node Id =0, etc.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
-- restart the sql
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'min server memory', 1024
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
The box is a:
Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
Mar 23 2007 16:28:52
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
That's a WinServer 2003 64-bit.
Physical_memory_in_bytes virtual_memory_in_bytes bpool_committed
bpool_commit_target bpool_visible
-- -- --
-- --
8584736768 2147352576 5280 199912
199912
Am I doing it right? How to verify my stuff are consuming memory from the
AWE?
Thanks.
You can use Performance on Windows and verify Memory Manager, Total Server
Memory.
Check your SQL Server log when the instance was started, there must be a
'Address Windowing Extensions enabled' message. If AWE was not succesfully
started there must be a related error message.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"light_wt" wrote:

>

> I have done these steps to config and enable AWE. But, DBCC MEMORYSTATUS
> still show AWE=0 on everywhere, liked Memory Manager, Memory node Id =0, etc.
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> -- restart the sql
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'min server memory', 1024
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
> The box is a:
> Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
> Mar 23 2007 16:28:52
> Copyright (c) 1988-2005 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
> That's a WinServer 2003 64-bit.
> Physical_memory_in_bytes virtual_memory_in_bytes bpool_committed
> bpool_commit_target bpool_visible
> -- -- --
> -- --
> 8584736768 2147352576 5280 199912
> 199912
> Am I doing it right? How to verify my stuff are consuming memory from the
> AWE?
> Thanks.
>
|||Did you add your SQL Server service account to "Lock pages in memory" list
before performing this action?
Otherwise, it would not let you set AWE enable.
How to: Enable the Lock Pages in Memory Option (Windows):
http://msdn2.microsoft.com/en-us/library/ms190730.aspx
Ekrem ?nsoy
"light_wt" <lightwt@.discussions.microsoft.com> wrote in message
news:2217E528-6E89-4C83-987C-FAA270A30FE3@.microsoft.com...
>

> I have done these steps to config and enable AWE. But, DBCC MEMORYSTATUS
> still show AWE=0 on everywhere, liked Memory Manager, Memory node Id =0,
> etc.
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> -- restart the sql
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'min server memory', 1024
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
> The box is a:
> Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
> Mar 23 2007 16:28:52
> Copyright (c) 1988-2005 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
> That's a WinServer 2003 64-bit.
> Physical_memory_in_bytes virtual_memory_in_bytes bpool_committed
> bpool_commit_target bpool_visible
> -- -- --
> -- --
> 8584736768 2147352576 5280 199912
> 199912
> Am I doing it right? How to verify my stuff are consuming memory from the
> AWE?
> Thanks.
>
|||Also, there are AWE specific counters under SQLServer:Buffer Manager. Take a
look at these AWE counters to see if there are any AWE-related memory
activities.
Linchi
"light_wt" wrote:

>

> I have done these steps to config and enable AWE. But, DBCC MEMORYSTATUS
> still show AWE=0 on everywhere, liked Memory Manager, Memory node Id =0, etc.
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> -- restart the sql
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'min server memory', 1024
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
> The box is a:
> Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
> Mar 23 2007 16:28:52
> Copyright (c) 1988-2005 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
> That's a WinServer 2003 64-bit.
> Physical_memory_in_bytes virtual_memory_in_bytes bpool_committed
> bpool_commit_target bpool_visible
> -- -- --
> -- --
> 8584736768 2147352576 5280 199912
> 199912
> Am I doing it right? How to verify my stuff are consuming memory from the
> AWE?
> Thanks.
>
|||thanks everyone for your ideas.
i've look at the SQL Server Log, after the instances started, the AWE is
enable.
i've check the userid who can do Lock Memory and is the same perosn who own
the Job.
in perfmon, I have added all AWE-related counters in SQLServer:Buffer
Manager
and changed the vertical counter to 5.
nothing happen. AWE got 0.
Am I missing something?
thanks.

AWE got 0, said DBCC MEMORYSTATUS...

:)
I have done these steps to config and enable AWE. But, DBCC MEMORYSTATUS
still show AWE=0 on everywhere, liked Memory Manager, Memory node Id =0, etc.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
-- restart the sql
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'min server memory', 1024
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
The box is a:
Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
Mar 23 2007 16:28:52
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
That's a WinServer 2003 64-bit.
Physical_memory_in_bytes virtual_memory_in_bytes bpool_committed
bpool_commit_target bpool_visible
-- -- --
-- --
8584736768 2147352576 5280 199912
199912
Am I doing it right? How to verify my stuff are consuming memory from the
AWE?
Thanks.You can use Performance on Windows and verify Memory Manager, Total Server
Memory.
Check your SQL Server log when the instance was started, there must be a
'Address Windowing Extensions enabled' message. If AWE was not succesfully
started there must be a related error message.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"light_wt" wrote:
> :)
> I have done these steps to config and enable AWE. But, DBCC MEMORYSTATUS
> still show AWE=0 on everywhere, liked Memory Manager, Memory node Id =0, etc.
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> -- restart the sql
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'min server memory', 1024
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
> The box is a:
> Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
> Mar 23 2007 16:28:52
> Copyright (c) 1988-2005 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
> That's a WinServer 2003 64-bit.
> Physical_memory_in_bytes virtual_memory_in_bytes bpool_committed
> bpool_commit_target bpool_visible
> -- -- --
> -- --
> 8584736768 2147352576 5280 199912
> 199912
> Am I doing it right? How to verify my stuff are consuming memory from the
> AWE?
> Thanks.
>|||Did you add your SQL Server service account to "Lock pages in memory" list
before performing this action?
Otherwise, it would not let you set AWE enable.
How to: Enable the Lock Pages in Memory Option (Windows):
http://msdn2.microsoft.com/en-us/library/ms190730.aspx
--
Ekrem Ã?nsoy
"light_wt" <lightwt@.discussions.microsoft.com> wrote in message
news:2217E528-6E89-4C83-987C-FAA270A30FE3@.microsoft.com...
> :)
> I have done these steps to config and enable AWE. But, DBCC MEMORYSTATUS
> still show AWE=0 on everywhere, liked Memory Manager, Memory node Id =0,
> etc.
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> -- restart the sql
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'min server memory', 1024
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
> The box is a:
> Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
> Mar 23 2007 16:28:52
> Copyright (c) 1988-2005 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
> That's a WinServer 2003 64-bit.
> Physical_memory_in_bytes virtual_memory_in_bytes bpool_committed
> bpool_commit_target bpool_visible
> -- -- --
> -- --
> 8584736768 2147352576 5280 199912
> 199912
> Am I doing it right? How to verify my stuff are consuming memory from the
> AWE?
> Thanks.
>|||Also, there are AWE specific counters under SQLServer:Buffer Manager. Take a
look at these AWE counters to see if there are any AWE-related memory
activities.
Linchi
"light_wt" wrote:
> :)
> I have done these steps to config and enable AWE. But, DBCC MEMORYSTATUS
> still show AWE=0 on everywhere, liked Memory Manager, Memory node Id =0, etc.
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> -- restart the sql
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'min server memory', 1024
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
> The box is a:
> Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
> Mar 23 2007 16:28:52
> Copyright (c) 1988-2005 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
> That's a WinServer 2003 64-bit.
> Physical_memory_in_bytes virtual_memory_in_bytes bpool_committed
> bpool_commit_target bpool_visible
> -- -- --
> -- --
> 8584736768 2147352576 5280 199912
> 199912
> Am I doing it right? How to verify my stuff are consuming memory from the
> AWE?
> Thanks.
>|||thanks everyone for your ideas.
i've look at the SQL Server Log, after the instances started, the AWE is
enable.
i've check the userid who can do Lock Memory and is the same perosn who own
the Job.
in perfmon, I have added all AWE-related counters in SQLServer:Buffer
Manager
and changed the vertical counter to 5.
nothing happen. AWE got 0.
Am I missing something?
thanks.

AWE enabled on 64 bit system ?

Do we need to enable AWE on a 64 bit system ?
Do we need to add the /PAE switch ?
Can someone send me the link that specifically talks about these settings on
a 64 bit server , if one exists ? ThanksNo
On true 64 bit Intel Itanium Processor based Systems, there is no need for
AWE /3GB or PAE switches.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Hassan" <hassanboy@.hotmail.com> wrote in message
news:u7c7lKiuFHA.2948@.TK2MSFTNGP15.phx.gbl...
> Do we need to enable AWE on a 64 bit system ?
> Do we need to add the /PAE switch ?
> Can someone send me the link that specifically talks about these settings
> on a 64 bit server , if one exists ? Thanks
>|||Although, interestingly enough, enabling 'lock pages in memory' can be
beneficial: http://blogs.msdn.com/slavao/archiv.../31/458545.aspx
Thanks,
--
Ryan Stonecipher
Microsoft Sql Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:ukm9LtiuFHA.2568@.TK2MSFTNGP15.phx.gbl...
> No
> On true 64 bit Intel Itanium Processor based Systems, there is no need for
> AWE /3GB or PAE switches.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Hassan" <hassanboy@.hotmail.com> wrote in message
> news:u7c7lKiuFHA.2948@.TK2MSFTNGP15.phx.gbl...
>

AWE enabled on 64 bit system ?

Do we need to enable AWE on a 64 bit system ?
Do we need to add the /PAE switch ?
Can someone send me the link that specifically talks about these settings on
a 64 bit server , if one exists ? Thanks
No
On true 64 bit Intel Itanium Processor based Systems, there is no need for
AWE /3GB or PAE switches.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Hassan" <hassanboy@.hotmail.com> wrote in message
news:u7c7lKiuFHA.2948@.TK2MSFTNGP15.phx.gbl...
> Do we need to enable AWE on a 64 bit system ?
> Do we need to add the /PAE switch ?
> Can someone send me the link that specifically talks about these settings
> on a 64 bit server , if one exists ? Thanks
>
|||Although, interestingly enough, enabling 'lock pages in memory' can be
beneficial: http://blogs.msdn.com/slavao/archive...31/458545.aspx
Thanks,
Ryan Stonecipher
Microsoft Sql Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:ukm9LtiuFHA.2568@.TK2MSFTNGP15.phx.gbl...
> No
> On true 64 bit Intel Itanium Processor based Systems, there is no need for
> AWE /3GB or PAE switches.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Hassan" <hassanboy@.hotmail.com> wrote in message
> news:u7c7lKiuFHA.2948@.TK2MSFTNGP15.phx.gbl...
>

AWE enabled on 64 bit system ?

Do we need to enable AWE on a 64 bit system ?
Do we need to add the /PAE switch ?
Can someone send me the link that specifically talks about these settings on
a 64 bit server , if one exists ? ThanksNo
On true 64 bit Intel Itanium Processor based Systems, there is no need for
AWE /3GB or PAE switches.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Hassan" <hassanboy@.hotmail.com> wrote in message
news:u7c7lKiuFHA.2948@.TK2MSFTNGP15.phx.gbl...
> Do we need to enable AWE on a 64 bit system ?
> Do we need to add the /PAE switch ?
> Can someone send me the link that specifically talks about these settings
> on a 64 bit server , if one exists ? Thanks
>|||Although, interestingly enough, enabling 'lock pages in memory' can be
beneficial: http://blogs.msdn.com/slavao/archive/2005/08/31/458545.aspx
Thanks,
--
Ryan Stonecipher
Microsoft Sql Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:ukm9LtiuFHA.2568@.TK2MSFTNGP15.phx.gbl...
> No
> On true 64 bit Intel Itanium Processor based Systems, there is no need for
> AWE /3GB or PAE switches.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Hassan" <hassanboy@.hotmail.com> wrote in message
> news:u7c7lKiuFHA.2948@.TK2MSFTNGP15.phx.gbl...
>> Do we need to enable AWE on a 64 bit system ?
>> Do we need to add the /PAE switch ?
>> Can someone send me the link that specifically talks about these settings
>> on a 64 bit server , if one exists ? Thanks
>

AWE enabled

Hi, please let me know if I enable AWE and PAE and turn on /3 GB switch, why
can't I see sqlserver.exe or total/target server memory more that 2.72 GB?
Event though there is a page/sec goes upto 6000. Server must need memory more
than 3 GB. My email address is : atiqur_rahman02@.yahoo.com or you can paste
here. Thanks for your help!
How much memory does your server machine have? What is the version and
edition of the operating system and SQL Server you are using?
Anith

AWE enable and SQL Server 2005 x64 bits

Hello,

I am setting up a new server with Windows Server 2003 x64 bits and SQL Server 2005 x64 bits. Under 32 bits of Windows we normally use /3GB and enable AWE under SQL Server (both SQL 2000 and SQL 2005) and allocate 6 GB of fixed memory to SQL Server.

Does any one know whether I should do the same thing under the x64 bits platform. I read some articles on the web that it is no longer required to use AWE under SQL 2005 x64 bits?

Please advise.

Thanks.

You don't need to enable AWE via sp_configure if you are running the 64bit version on x64, as 64bit SQL doesn't need to use the AWE api to address the larger memory space.

It is recommended to grant the SQL service account the OS privilege "Lock pages in memory". By doing this you are preventing the OS from swapping SQL's memory pages to disk and allowing SQL itself to reduce it's working set when the OS requires it to do so. This should give you a performance benefit under tight memory situations. One of the odd results of using "lock pages in memory" is that we will use the AWE api to map the virtual address space into and out of physical memory (in fact the "lock pages in memory" privilege is a requirement for using AWE with 32bit). As a result the "AWE allocated" value from dbcc memorystatus will show a value, indicating that AWE is enabled even though it is disabled in sp_configure.

In summary, the 64bit version of SQL Server can address all the memory on the server without having to use AWE. A perf benefit may be observed when "lock pages in memory" is enabled and this results in the use of AWE internally, irrespective of the sp_configure setting.

thx, Simon.

|||

Hi Simon

Thanks you for your advice. Are you suggesting that we should turn on "local pages in memory" under x64 bits platform as well even though SQL can address all the memory on the server?

One more question, do you know if I need /PAE under x64 bits of Windows?

Thanks.

|||

I just found an article under MS and according to this article from MS, PAE is not available in Windows x64...

Thanks..

|||Do you still need the /3GB switch in a 2005 x64 install if you have 16GB of memory?|||No

AWE enable and SQL Server 2005 x64 bits

Hello,

Does any one know whether I should do the same thing under the x64 bits platform. I read some articles on the web that it is no longer required to use AWE under SQL 2005 x64 bits?

Please advise.

Thanks.

You don't need to enable AWE via sp_configure if you are running the 64bit version on x64, as 64bit SQL doesn't need to use the AWE api to address the larger memory space.

thx, Simon.

|||

Hi Simon

Thanks you for your advice. Are you suggesting that we should turn on "local pages in memory" under x64 bits platform as well even though SQL can address all the memory on the server?

One more question, do you know if I need /PAE under x64 bits of Windows?

Thanks.

|||

I just found an article under MS and according to this article from MS, PAE is not available in Windows x64...

Thanks..

|||Do you still need the /3GB switch in a 2005 x64 install if you have 16GB of memory?|||No

AWE and Target Server Memory

Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
This is the script we used to enable AWE and set Max Memory, essentially
leaving 2GB for the OS.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
Just so you are aware, we do have the boot.ini with the PAE and 3GB switches
set.
The question I have, is what I am seeing for Target and Total Server Memory:
Target Server Memory(KB) = 4087767
Total Server Memory(KB) = 4087747
I was expecting to see more Target Server Memory being used (closer to 6GB)
rather than only 4087767KB / 3.898GB.
Please explain.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200609/1What version of SQL Server are you using?
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:663faf808d6ce@.uwe...
Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
This is the script we used to enable AWE and set Max Memory, essentially
leaving 2GB for the OS.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
Just so you are aware, we do have the boot.ini with the PAE and 3GB switches
set.
The question I have, is what I am seeing for Target and Total Server Memory:
Target Server Memory(KB) = 4087767
Total Server Memory(KB) = 4087747
I was expecting to see more Target Server Memory being used (closer to 6GB)
rather than only 4087767KB / 3.898GB.
Please explain.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200609/1|||SQL 2000
Tom Moreau wrote:
>What version of SQL Server are you using?
>Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
>This is the script we used to enable AWE and set Max Memory, essentially
>leaving 2GB for the OS.
>sp_configure 'show advanced options', 1
>RECONFIGURE
>GO
>sp_configure 'awe enabled', 1
>RECONFIGURE
>GO
>sp_configure 'max server memory', 6144
>RECONFIGURE
>GO
>Just so you are aware, we do have the boot.ini with the PAE and 3GB switche
s
>set.
>The question I have, is what I am seeing for Target and Total Server Memory
:
>Target Server Memory(KB) = 4087767
>Total Server Memory(KB) = 4087747
>I was expecting to see more Target Server Memory being used (closer to 6GB)
>rather than only 4087767KB / 3.898GB.
>Please explain.
Message posted via http://www.droptable.com|||Which SP level? What's the result of running:
SELECT @.@.VERSION
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:663fdb867f662@.uwe...
SQL 2000
Tom Moreau wrote:
>What version of SQL Server are you using?
>Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
>This is the script we used to enable AWE and set Max Memory, essentially
>leaving 2GB for the OS.
>sp_configure 'show advanced options', 1
>RECONFIGURE
>GO
>sp_configure 'awe enabled', 1
>RECONFIGURE
>GO
>sp_configure 'max server memory', 6144
>RECONFIGURE
>GO
>Just so you are aware, we do have the boot.ini with the PAE and 3GB
>switches
>set.
>The question I have, is what I am seeing for Target and Total Server
>Memory:
>Target Server Memory(KB) = 4087767
>Total Server Memory(KB) = 4087747
>I was expecting to see more Target Server Memory being used (closer to 6GB)
>rather than only 4087767KB / 3.898GB.
>Please explain.
Message posted via http://www.droptable.com|||Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
NT 5.2 (Build 3790: Service Pack 1)
Tom Moreau wrote:[vbcol=seagreen]
>Which SP level? What's the result of running:
>SELECT @.@.VERSION
>SQL 2000
>Tom Moreau wrote:
>[quoted text clipped - 27 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200609/1|||What happens if you set the min server memory and restart SQL Server?
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:664097d00a0ed@.uwe...
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
NT 5.2 (Build 3790: Service Pack 1)
Tom Moreau wrote:[vbcol=seagreen]
>Which SP level? What's the result of running:
>SELECT @.@.VERSION
>SQL 2000
>Tom Moreau wrote:
>[quoted text clipped - 27 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200609/1|||I am away from the office and will not have access to the server until
tomorrow around 10:00 MST. Even then we will not be able to restart the
service until late tomorrow evening. Do you have a theory about setting "min
server memory"? I believe I recall on the "max server memory" the minimum is
set to 4. Anyway, just trying to follow your thought process on why the "min
server memory" might be inhibiting memory use.
Tom Moreau wrote:[vbcol=seagreen]
>What happens if you set the min server memory and restart SQL Server?
>Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
>Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Window
s
>NT 5.2 (Build 3790: Service Pack 1)
>Tom Moreau wrote:
>[quoted text clipped - 7 lines]
Message posted via http://www.droptable.com|||In SQL 2005, server memory will gradually climb to the max server memory,
whether or not you're using AWE. In SQL 2000, it's supposed to take it in
one chunk, IIRC. I'm thinking that if max = min = whatever you really want,
then you may be forcing it up to that level straight away.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:6641520a8602d@.uwe...
I am away from the office and will not have access to the server until
tomorrow around 10:00 MST. Even then we will not be able to restart the
service until late tomorrow evening. Do you have a theory about setting "min
server memory"? I believe I recall on the "max server memory" the minimum is
set to 4. Anyway, just trying to follow your thought process on why the "min
server memory" might be inhibiting memory use.
Tom Moreau wrote:[vbcol=seagreen]
>What happens if you set the min server memory and restart SQL Server?
>Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
>Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on
>Windows
>NT 5.2 (Build 3790: Service Pack 1)
>Tom Moreau wrote:
>[quoted text clipped - 7 lines]
Message posted via http://www.droptable.com|||This is the 'expected behavior' of 8.00.2039 and is fixed in 8.00.2040. See
http://support.microsoft.com/defaul...kb;en-us;899761
Linchi
"cbrichards via droptable.com" wrote:

> Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windo
ws
> NT 5.2 (Build 3790: Service Pack 1)
>
> Tom Moreau wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200609/1
>

AWE and Target Server Memory

Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
This is the script we used to enable AWE and set Max Memory, essentially
leaving 2GB for the OS.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
Just so you are aware, we do have the boot.ini with the PAE and 3GB switches
set.
The question I have, is what I am seeing for Target and Total Server Memory:
Target Server Memory(KB) = 4087767
Total Server Memory(KB) = 4087747
I was expecting to see more Target Server Memory being used (closer to 6GB)
rather than only 4087767KB / 3.898GB.
Please explain.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200609/1
What version of SQL Server are you using?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:663faf808d6ce@.uwe...
Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
This is the script we used to enable AWE and set Max Memory, essentially
leaving 2GB for the OS.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
Just so you are aware, we do have the boot.ini with the PAE and 3GB switches
set.
The question I have, is what I am seeing for Target and Total Server Memory:
Target Server Memory(KB) = 4087767
Total Server Memory(KB) = 4087747
I was expecting to see more Target Server Memory being used (closer to 6GB)
rather than only 4087767KB / 3.898GB.
Please explain.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200609/1
|||SQL 2000
Tom Moreau wrote:
>What version of SQL Server are you using?
>Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
>This is the script we used to enable AWE and set Max Memory, essentially
>leaving 2GB for the OS.
>sp_configure 'show advanced options', 1
>RECONFIGURE
>GO
>sp_configure 'awe enabled', 1
>RECONFIGURE
>GO
>sp_configure 'max server memory', 6144
>RECONFIGURE
>GO
>Just so you are aware, we do have the boot.ini with the PAE and 3GB switches
>set.
>The question I have, is what I am seeing for Target and Total Server Memory:
>Target Server Memory(KB) = 4087767
>Total Server Memory(KB) = 4087747
>I was expecting to see more Target Server Memory being used (closer to 6GB)
>rather than only 4087767KB / 3.898GB.
>Please explain.
Message posted via http://www.droptable.com
|||Which SP level? What's the result of running:
SELECT @.@.VERSION
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:663fdb867f662@.uwe...
SQL 2000
Tom Moreau wrote:
>What version of SQL Server are you using?
>Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
>This is the script we used to enable AWE and set Max Memory, essentially
>leaving 2GB for the OS.
>sp_configure 'show advanced options', 1
>RECONFIGURE
>GO
>sp_configure 'awe enabled', 1
>RECONFIGURE
>GO
>sp_configure 'max server memory', 6144
>RECONFIGURE
>GO
>Just so you are aware, we do have the boot.ini with the PAE and 3GB
>switches
>set.
>The question I have, is what I am seeing for Target and Total Server
>Memory:
>Target Server Memory(KB) = 4087767
>Total Server Memory(KB) = 4087747
>I was expecting to see more Target Server Memory being used (closer to 6GB)
>rather than only 4087767KB / 3.898GB.
>Please explain.
Message posted via http://www.droptable.com
|||Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
NT 5.2 (Build 3790: Service Pack 1)
Tom Moreau wrote:[vbcol=seagreen]
>Which SP level? What's the result of running:
>SELECT @.@.VERSION
>SQL 2000
>Tom Moreau wrote:
>[quoted text clipped - 27 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200609/1
|||What happens if you set the min server memory and restart SQL Server?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:664097d00a0ed@.uwe...
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
NT 5.2 (Build 3790: Service Pack 1)
Tom Moreau wrote:[vbcol=seagreen]
>Which SP level? What's the result of running:
>SELECT @.@.VERSION
>SQL 2000
>Tom Moreau wrote:
>[quoted text clipped - 27 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200609/1
|||I am away from the office and will not have access to the server until
tomorrow around 10:00 MST. Even then we will not be able to restart the
service until late tomorrow evening. Do you have a theory about setting "min
server memory"? I believe I recall on the "max server memory" the minimum is
set to 4. Anyway, just trying to follow your thought process on why the "min
server memory" might be inhibiting memory use.
Tom Moreau wrote:[vbcol=seagreen]
>What happens if you set the min server memory and restart SQL Server?
>Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
>Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
>NT 5.2 (Build 3790: Service Pack 1)
>Tom Moreau wrote:
>[quoted text clipped - 7 lines]
Message posted via http://www.droptable.com
|||In SQL 2005, server memory will gradually climb to the max server memory,
whether or not you're using AWE. In SQL 2000, it's supposed to take it in
one chunk, IIRC. I'm thinking that if max = min = whatever you really want,
then you may be forcing it up to that level straight away.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:6641520a8602d@.uwe...
I am away from the office and will not have access to the server until
tomorrow around 10:00 MST. Even then we will not be able to restart the
service until late tomorrow evening. Do you have a theory about setting "min
server memory"? I believe I recall on the "max server memory" the minimum is
set to 4. Anyway, just trying to follow your thought process on why the "min
server memory" might be inhibiting memory use.
Tom Moreau wrote:[vbcol=seagreen]
>What happens if you set the min server memory and restart SQL Server?
>Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
>Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on
>Windows
>NT 5.2 (Build 3790: Service Pack 1)
>Tom Moreau wrote:
>[quoted text clipped - 7 lines]
Message posted via http://www.droptable.com
|||This is the 'expected behavior' of 8.00.2039 and is fixed in 8.00.2040. See
http://support.microsoft.com/default...b;en-us;899761
Linchi
"cbrichards via droptable.com" wrote:

> Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
> NT 5.2 (Build 3790: Service Pack 1)
>
> Tom Moreau wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200609/1
>

Saturday, February 25, 2012

AWE + 8GB

I have the \PAE switch in the boot.ini file. Do I also need the \3GB ? What
is that used for ? If i dont use it, can i still enable AWE ?
I have 8GB of RAM and also enabled AWE option. Just wondering what the \3GB
switch does in addition to \PAE/PAE is an OS switch needed if you want any application to have access to
memory beyond 4GB.
Normally, applications cannot address or use any memory beyond 2GB. However,
if you have /PAE on in the OS, you can configure AWE in SQL Server so that
SQL Server, as an application, can access memory above 2 GB. It access that
memory sort of like a page fault, using some memory as a map, to be able to
access the memory in the higher range.
/3GB is an OS flag that allows any app to ADDRESS memory up to 3GB. That
means that if you have both /3GB and AWE in SQL Server, the memory in the
203GB range can be directly accessed, rather than going through the AWE
maps. Direct access is always faster than mapped addressing.
So to summarize the two OS flags:
/PAE allows an app within the OS to use memory beyond 4GB
/3GB allows an app to directly address memory in the 2-3GB range
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:#L1K98nkDHA.688@.TK2MSFTNGP10.phx.gbl...
> I have the \PAE switch in the boot.ini file. Do I also need the \3GB ?
What
> is that used for ? If i dont use it, can i still enable AWE ?
> I have 8GB of RAM and also enabled AWE option. Just wondering what the
\3GB
> switch does in addition to \PAE
>|||So its best advisable then even though we may set a max limit to say 5 or
6GB on an 8GB RAM box to use both switches right ?
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:%2376kiKokDHA.2732@.TK2MSFTNGP11.phx.gbl...
> /PAE is an OS switch needed if you want any application to have access to
> memory beyond 4GB.
> Normally, applications cannot address or use any memory beyond 2GB.
However,
> if you have /PAE on in the OS, you can configure AWE in SQL Server so
that
> SQL Server, as an application, can access memory above 2 GB. It access
that
> memory sort of like a page fault, using some memory as a map, to be able
to
> access the memory in the higher range.
> /3GB is an OS flag that allows any app to ADDRESS memory up to 3GB. That
> means that if you have both /3GB and AWE in SQL Server, the memory in the
> 203GB range can be directly accessed, rather than going through the AWE
> maps. Direct access is always faster than mapped addressing.
> So to summarize the two OS flags:
> /PAE allows an app within the OS to use memory beyond 4GB
> /3GB allows an app to directly address memory in the 2-3GB range
> --
> HTH
> --
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:#L1K98nkDHA.688@.TK2MSFTNGP10.phx.gbl...
> > I have the \PAE switch in the boot.ini file. Do I also need the \3GB ?
> What
> > is that used for ? If i dont use it, can i still enable AWE ?
> > I have 8GB of RAM and also enabled AWE option. Just wondering what the
> \3GB
> > switch does in addition to \PAE
> >
> >
>|||Yes, up to 16 GB you should use both. After 16, the memory maps that AWE
needs take so much space and must be directly accessible, so if you use /3GB
and only leave 1 GB for the OS and the AWE maps, it is not enough. So after
16GB, you should not use AWE and /3GB both.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:OXA4IdokDHA.1948@.TK2MSFTNGP12.phx.gbl...
> So its best advisable then even though we may set a max limit to say 5 or
> 6GB on an 8GB RAM box to use both switches right ?
>
> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
> news:%2376kiKokDHA.2732@.TK2MSFTNGP11.phx.gbl...
> > /PAE is an OS switch needed if you want any application to have access
to
> > memory beyond 4GB.
> > Normally, applications cannot address or use any memory beyond 2GB.
> However,
> > if you have /PAE on in the OS, you can configure AWE in SQL Server so
> that
> > SQL Server, as an application, can access memory above 2 GB. It access
> that
> > memory sort of like a page fault, using some memory as a map, to be able
> to
> > access the memory in the higher range.
> >
> > /3GB is an OS flag that allows any app to ADDRESS memory up to 3GB. That
> > means that if you have both /3GB and AWE in SQL Server, the memory in
the
> > 203GB range can be directly accessed, rather than going through the AWE
> > maps. Direct access is always faster than mapped addressing.
> >
> > So to summarize the two OS flags:
> > /PAE allows an app within the OS to use memory beyond 4GB
> > /3GB allows an app to directly address memory in the 2-3GB range
> >
> > --
> > HTH
> > --
> > Kalen Delaney
> > SQL Server MVP
> > www.SolidQualityLearning.com
> >
> >
> > "Hassan" <fatima_ja@.hotmail.com> wrote in message
> > news:#L1K98nkDHA.688@.TK2MSFTNGP10.phx.gbl...
> > > I have the \PAE switch in the boot.ini file. Do I also need the \3GB ?
> > What
> > > is that used for ? If i dont use it, can i still enable AWE ?
> > > I have 8GB of RAM and also enabled AWE option. Just wondering what the
> > \3GB
> > > switch does in addition to \PAE
> > >
> > >
> >
> >
>|||"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23L1K98nkDHA.688@.TK2MSFTNGP10.phx.gbl...
> I have the \PAE switch in the boot.ini file. Do I also need the \3GB ?
What
> is that used for ? If i dont use it, can i still enable AWE ?
> I have 8GB of RAM and also enabled AWE option. Just wondering what the
\3GB
> switch does in addition to \PAE
Just to add to what has already been said, be careful of AWE because it does
not always provide benefit. The additional level of indirection has some
overhead: I ran a large number of benchmarks a couple of years ago on a 16Gb
32 way machine and we found that every test process of our application ran
slightly _slower_ with AWE switched on!
If your application is using AWE as cache, demanding Gb of data to be
present in RAM for it to run at an acceptable speed, it is likely that you
have an inefficient application. In this case, tweaking the app will provide
you orders of magnitude better performance than throwing hardware at the
problem.
Of course, this is assuming you live in a perfect world...
On the other hand you may be using a single SQL Server instance to host many
SQL Server applications on different databases, in which case I can see that
AWE may provide some benefit in that case. In this case, however, it may
well be that you have partitioned the applications onto separate SQL Server
instances instead.
AWE gives me palpitations from the old x86 DOS days with the 640k/1Mb memory
barrier, paging LIM/EMS banks, upper memory and extended memory. I had a
little cottage industry crafting config.sys and autoexec.bat to make
combinations of apps work together without having to reboot or crash. Ahhh
those were the days.
Kind Regards, Howard|||I want to use AWE cos we have 8GB of RAM sitting on the box and do not wish
to see it go waste . The folks always say to throw as much memory as you can
and were just doing that ...How can we determine if our AWE is using cache
as you mentioned and that we might need to tweak the app bcos of the same ?
"Howard Long" <howard@.howardlongxxx.com> wrote in message
news:bmj3ap$df8$1@.sparta.btinternet.com...
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23L1K98nkDHA.688@.TK2MSFTNGP10.phx.gbl...
> > I have the \PAE switch in the boot.ini file. Do I also need the \3GB ?
> What
> > is that used for ? If i dont use it, can i still enable AWE ?
> > I have 8GB of RAM and also enabled AWE option. Just wondering what the
> \3GB
> > switch does in addition to \PAE
> Just to add to what has already been said, be careful of AWE because it
does
> not always provide benefit. The additional level of indirection has some
> overhead: I ran a large number of benchmarks a couple of years ago on a
16Gb
> 32 way machine and we found that every test process of our application ran
> slightly _slower_ with AWE switched on!
> If your application is using AWE as cache, demanding Gb of data to be
> present in RAM for it to run at an acceptable speed, it is likely that you
> have an inefficient application. In this case, tweaking the app will
provide
> you orders of magnitude better performance than throwing hardware at the
> problem.
> Of course, this is assuming you live in a perfect world...
> On the other hand you may be using a single SQL Server instance to host
many
> SQL Server applications on different databases, in which case I can see
that
> AWE may provide some benefit in that case. In this case, however, it may
> well be that you have partitioned the applications onto separate SQL
Server
> instances instead.
> AWE gives me palpitations from the old x86 DOS days with the 640k/1Mb
memory
> barrier, paging LIM/EMS banks, upper memory and extended memory. I had a
> little cottage industry crafting config.sys and autoexec.bat to make
> combinations of apps work together without having to reboot or crash. Ahhh
> those were the days.
> Kind Regards, Howard
>

AWE - SQL Server 2000 - Memory usage

Hi all!
We have a SQL Server 2000 Enterprise machine with 3.75 GB of ram in it.
Microsoft gave the advise to enable the "AWE" sql server option and the
"/3GB" windows option.
(http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech)
But when I go to the task manager I see SQL server is only using about 144
mb ?
And the total system memory usage is 2.6 GB... and i cannot see the process
that is using that amount of memory.....
-How can I see what it using so much memory?
-Is this a normal situation when you enablee /3GB and AWE or do you see
sqlserver.exe consuming more memory in your task manager?
I want to know if there is something wrong with our configuration.
Thanks in advance for your answer!
Best regards
Floris van HaasterTask Manager isn't AWE aware. Use Perf Mon instead.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Floris van Haaster" <floris@.NO-SPAM-datasmit.nl> wrote in message
news:435de4b3$0$11072$e4fe514c@.news.xs4all.nl...
> Hi all!
> We have a SQL Server 2000 Enterprise machine with 3.75 GB of ram in it.
> Microsoft gave the advise to enable the "AWE" sql server option and the "/3GB" windows option.
> (http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech)
> But when I go to the task manager I see SQL server is only using about 144 mb ?
> And the total system memory usage is 2.6 GB... and i cannot see the process that is using that
> amount of memory.....
> -How can I see what it using so much memory?
> -Is this a normal situation when you enablee /3GB and AWE or do you see sqlserver.exe consuming
> more memory in your task manager?
> I want to know if there is something wrong with our configuration.
> Thanks in advance for your answer!
> Best regards
> Floris van Haaster
>|||Ok thanks,
But what meter shows the correct value?
When i take a look @. "SQLServer:Memory Manager > Maximum Workspace memory
(KB)" it's value = 1175344 KB and that's only 1 GB or so...
Or do i have to look at another counter?
Best regards
Floris
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> schreef
in bericht news:%230isnEU2FHA.3228@.TK2MSFTNGP15.phx.gbl...
> Task Manager isn't AWE aware. Use Perf Mon instead.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Floris van Haaster" <floris@.NO-SPAM-datasmit.nl> wrote in message
> news:435de4b3$0$11072$e4fe514c@.news.xs4all.nl...
>> Hi all!
>> We have a SQL Server 2000 Enterprise machine with 3.75 GB of ram in it.
>> Microsoft gave the advise to enable the "AWE" sql server option and the
>> "/3GB" windows option.
>> (http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech)
>> But when I go to the task manager I see SQL server is only using about
>> 144 mb ?
>> And the total system memory usage is 2.6 GB... and i cannot see the
>> process that is using that amount of memory.....
>> -How can I see what it using so much memory?
>> -Is this a normal situation when you enablee /3GB and AWE or do you see
>> sqlserver.exe consuming more memory in your task manager?
>> I want to know if there is something wrong with our configuration.
>> Thanks in advance for your answer!
>> Best regards
>> Floris van Haaster
>>
>|||Use "Buffer Manager: Total Pages" or DBCC MEMORYSTATUS command
(http://support.microsoft.com/?id=271624), check Buffer Counts, Committed,
which should be close to what you are consuming through AWE. Assuming AWE is
enabled.
Later versions (service packs) of SQL Server 2000 also have Visible counter
in DBCC MEMORYSTATUS output which will show how much of AWE-allocated memory
is actually mapped into virtual address space of SQL Server.
HTH,
Boris.
Boris Baryshnikov
Program Manager, SQL Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Floris van Haaster" <floris@.NO-SPAM-datasmit.nl> wrote in message
news:435e27bf$0$11063$e4fe514c@.news.xs4all.nl...
> Ok thanks,
> But what meter shows the correct value?
> When i take a look @. "SQLServer:Memory Manager > Maximum Workspace memory
> (KB)" it's value = 1175344 KB and that's only 1 GB or so...
> Or do i have to look at another counter?
> Best regards
> Floris
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> schreef
> in bericht news:%230isnEU2FHA.3228@.TK2MSFTNGP15.phx.gbl...
>> Task Manager isn't AWE aware. Use Perf Mon instead.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Floris van Haaster" <floris@.NO-SPAM-datasmit.nl> wrote in message
>> news:435de4b3$0$11072$e4fe514c@.news.xs4all.nl...
>> Hi all!
>> We have a SQL Server 2000 Enterprise machine with 3.75 GB of ram in it.
>> Microsoft gave the advise to enable the "AWE" sql server option and the
>> "/3GB" windows option.
>> (http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech)
>> But when I go to the task manager I see SQL server is only using about
>> 144 mb ?
>> And the total system memory usage is 2.6 GB... and i cannot see the
>> process that is using that amount of memory.....
>> -How can I see what it using so much memory?
>> -Is this a normal situation when you enablee /3GB and AWE or do you see
>> sqlserver.exe consuming more memory in your task manager?
>> I want to know if there is something wrong with our configuration.
>> Thanks in advance for your answer!
>> Best regards
>> Floris van Haaster
>>
>

Thursday, March 8, 2012

AWE on SQL Server 2000 & 2005

AWE on SQL Server 2000 & 2005

AWE on SQL Server 2000 & 2005

Wednesday, March 7, 2012

AWE got 0, said DBCC MEMORYSTATUS...

AWE got 0, said DBCC MEMORYSTATUS...

AWE got 0, said DBCC MEMORYSTATUS...

AWE enabled on 64 bit system ?

AWE enabled on 64 bit system ?

AWE enabled on 64 bit system ?

AWE enabled

AWE enable and SQL Server 2005 x64 bits

AWE enable and SQL Server 2005 x64 bits

AWE and Target Server Memory

AWE and Target Server Memory

AWE and Target Server Memory

AWE and Target Server Memory

Saturday, February 25, 2012

AWE + 8GB

AWE - SQL Server 2000 - Memory usage

AWE - SQL Server 2000 - Memory usage

AWE - SQL Server 2000 - Memory usage

Autonumber field

Blog Archive

About Me