I have a two node cluster with SQL Server 2005 that I am having difficulty
getting AWE to work. I have granted the "lock pages in memory" right to the
domain account that the SQL Server service is running under on both nodes
and run the following commands to setup the AWE memory.
sp_configure 'awe enabled', 1
go
reconfigure with override
go
sp_configure 'max server memory','6144'
go
reconfigure with override
go
I get the following error message when these statements complete:
Msg 5845, Level 16, State 1, Line 1
Address Windowing Extensions (AWE) requires the 'lock pages in memory'
privilege which is not currently present in the access token of the process.
Don't grant the privilege to the account. Grant it to the domain group you
designated when you installed SQL.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:uREFgcPrHHA.4324@.TK2MSFTNGP04.phx.gbl...
>I have a two node cluster with SQL Server 2005 that I am having difficulty
>getting AWE to work. I have granted the "lock pages in memory" right to
>the domain account that the SQL Server service is running under on both
>nodes and run the following commands to setup the AWE memory.
> sp_configure 'awe enabled', 1
> go
> reconfigure with override
> go
> sp_configure 'max server memory','6144'
> go
> reconfigure with override
> go
> I get the following error message when these statements complete:
> Msg 5845, Level 16, State 1, Line 1
> Address Windowing Extensions (AWE) requires the 'lock pages in memory'
> privilege which is not currently present in the access token of the
> process.
>
>
>
|||We got the same error, we restarted SQL, went back in and looked - it is now
enabled ;) We are on SP2 of Windows and SQL 2005.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:uREFgcPrHHA.4324@.TK2MSFTNGP04.phx.gbl...
>I have a two node cluster with SQL Server 2005 that I am having difficulty
>getting AWE to work. I have granted the "lock pages in memory" right to
>the domain account that the SQL Server service is running under on both
>nodes and run the following commands to setup the AWE memory.
> sp_configure 'awe enabled', 1
> go
> reconfigure with override
> go
> sp_configure 'max server memory','6144'
> go
> reconfigure with override
> go
> I get the following error message when these statements complete:
> Msg 5845, Level 16, State 1, Line 1
> Address Windowing Extensions (AWE) requires the 'lock pages in memory'
> privilege which is not currently present in the access token of the
> process.
>
>
>
|||The Microsoft documentation said to add the security account but I did
actually add both the account and the security group before I got the error.
Do you think that I need to reboot to aleviate the error message?
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:eBNxIPQrHHA.1508@.TK2MSFTNGP05.phx.gbl...
> Don't grant the privilege to the account. Grant it to the domain group
> you designated when you installed SQL.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Cgal" <cgallelli@.newsgroups.nospam> wrote in message
> news:uREFgcPrHHA.4324@.TK2MSFTNGP04.phx.gbl...
>
|||A reboot probably won't hurt.
It does seem to fix a lot of things in the Microsoft world.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:OEtitcTrHHA.3248@.TK2MSFTNGP03.phx.gbl...
> The Microsoft documentation said to add the security account but I did
> actually add both the account and the security group before I got the
> error.
> Do you think that I need to reboot to aleviate the error message?
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:eBNxIPQrHHA.1508@.TK2MSFTNGP05.phx.gbl...
>
|||In order for new Windows level security permissions to be active (such as the
lock pages in memory right) the account must log out and back in. As this is
a service account, the services simply need to be restarted.
Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration /
Microsoft Office SharePoint Server 2007: Configuration)
MCITP (dbadmin, dbdev)
"Cgal" wrote:
> The Microsoft documentation said to add the security account but I did
> actually add both the account and the security group before I got the error.
> Do you think that I need to reboot to aleviate the error message?
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:eBNxIPQrHHA.1508@.TK2MSFTNGP05.phx.gbl...
>
>
Showing posts with label node. Show all posts
Showing posts with label node. Show all posts
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.
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.
Saturday, February 25, 2012
AWE / Maximum Server Memory
We have a clustered environment with each node having 8GB memory, Win2k3
Enterprise Edition SP2, and SQL2k Enterprise Edition SP4.
I have read a few articles on AWE and the following link provided me with a
lot of information, but I still have a few questions:
http://www.sql-server-performance.com/awe_memory.asp
I understand that the switches that I should use are /3GB /PAE.
In the above article it stated that AWE technology is used only for the RAM
that exceeds the base 4GB of RAM. It further states that once the AWE
Enabled option is set to 1, SQL Server will take all of the RAM except 128MB
reserved for the OS. My question here is whether this statement refers to
128MB of the available AWE memory (e.g. the 128MB of the 4GB that is not from
the base 4GB in an 8GB configuration). So with the /3GB switch and AWE
enabled, does the operating system have approxiamtely 1.128GB dedicated to
the OS or only 128MB (this latter seems much too low).
When setting "Maximum Server Memory" does this refer to the entire 8GB (my
guess is yes)? And with no other applications running, should this be set to
8GB or (8GB - 1.128GB => 6.872GB).
The only other applications that we have running are the Vertias Client for
Backups and Symantec's Antivirus besides the standard Windows 2003 services.
I'm sure most production environments have something very similar. What
sould the recommended "Maximum Server Memory" be set to for a 8GB environment
with these services running.
Thanks,
Larry
Larry
> When setting "Maximum Server Memory" does this refer to the entire 8GB (my
> guess is yes)? And with no other applications running, should this be set
> to
> 8GB or (8GB - 1.128GB => 6.872GB).
Yes , you can set up even to 7GB :-))
> The only other applications that we have running are the Vertias Client
> for
> Backups and Symantec's Antivirus besides the standard Windows 2003
> services.
> I'm sure most production environments have something very similar. What
> sould the recommended "Maximum Server Memory" be set to for a 8GB
> environment
> with these services running.
You have to determine how much memory does each proccess take and
according to it set the MAX memory
"Larry Herbinaux" <LarryHerbinaux@.discussions.microsoft.com> wrote in
message news:7E65D50A-7BA1-4F5E-B62A-B8F9792C77CC@.microsoft.com...
> We have a clustered environment with each node having 8GB memory, Win2k3
> Enterprise Edition SP2, and SQL2k Enterprise Edition SP4.
> I have read a few articles on AWE and the following link provided me with
> a
> lot of information, but I still have a few questions:
> http://www.sql-server-performance.com/awe_memory.asp
> I understand that the switches that I should use are /3GB /PAE.
> In the above article it stated that AWE technology is used only for the
> RAM
> that exceeds the base 4GB of RAM. It further states that once the AWE
> Enabled option is set to 1, SQL Server will take all of the RAM except
> 128MB
> reserved for the OS. My question here is whether this statement refers to
> 128MB of the available AWE memory (e.g. the 128MB of the 4GB that is not
> from
> the base 4GB in an 8GB configuration). So with the /3GB switch and AWE
> enabled, does the operating system have approxiamtely 1.128GB dedicated to
> the OS or only 128MB (this latter seems much too low).
> When setting "Maximum Server Memory" does this refer to the entire 8GB (my
> guess is yes)? And with no other applications running, should this be set
> to
> 8GB or (8GB - 1.128GB => 6.872GB).
> The only other applications that we have running are the Vertias Client
> for
> Backups and Symantec's Antivirus besides the standard Windows 2003
> services.
> I'm sure most production environments have something very similar. What
> sould the recommended "Maximum Server Memory" be set to for a 8GB
> environment
> with these services running.
> Thanks,
> Larry
|||just to mention to be carefuly on mem counting having full 4gb of mem.
close to 4gb boundary, there may be memory mapped area used by motherboard
[pci cards etc], which may take almost 0,5gb of memory.
so, instead of 4gb, you may find available only 3,5gb appx or so
"Larry Herbinaux" <LarryHerbinaux@.discussions.microsoft.com> je napisao u
poruci interesnoj
grupi:7E65D50A-7BA1-4F5E-B62A-B8F9792C77CC@.microsoft.com...
> We have a clustered environment with each node having 8GB memory, Win2k3
> Enterprise Edition SP2, and SQL2k Enterprise Edition SP4.
> enabled, does the operating system have approxiamtely 1.128GB dedicated to
> the OS or only 128MB (this latter seems much too low).
>
> Larry
Enterprise Edition SP2, and SQL2k Enterprise Edition SP4.
I have read a few articles on AWE and the following link provided me with a
lot of information, but I still have a few questions:
http://www.sql-server-performance.com/awe_memory.asp
I understand that the switches that I should use are /3GB /PAE.
In the above article it stated that AWE technology is used only for the RAM
that exceeds the base 4GB of RAM. It further states that once the AWE
Enabled option is set to 1, SQL Server will take all of the RAM except 128MB
reserved for the OS. My question here is whether this statement refers to
128MB of the available AWE memory (e.g. the 128MB of the 4GB that is not from
the base 4GB in an 8GB configuration). So with the /3GB switch and AWE
enabled, does the operating system have approxiamtely 1.128GB dedicated to
the OS or only 128MB (this latter seems much too low).
When setting "Maximum Server Memory" does this refer to the entire 8GB (my
guess is yes)? And with no other applications running, should this be set to
8GB or (8GB - 1.128GB => 6.872GB).
The only other applications that we have running are the Vertias Client for
Backups and Symantec's Antivirus besides the standard Windows 2003 services.
I'm sure most production environments have something very similar. What
sould the recommended "Maximum Server Memory" be set to for a 8GB environment
with these services running.
Thanks,
Larry
Larry
> When setting "Maximum Server Memory" does this refer to the entire 8GB (my
> guess is yes)? And with no other applications running, should this be set
> to
> 8GB or (8GB - 1.128GB => 6.872GB).
Yes , you can set up even to 7GB :-))
> The only other applications that we have running are the Vertias Client
> for
> Backups and Symantec's Antivirus besides the standard Windows 2003
> services.
> I'm sure most production environments have something very similar. What
> sould the recommended "Maximum Server Memory" be set to for a 8GB
> environment
> with these services running.
You have to determine how much memory does each proccess take and
according to it set the MAX memory
"Larry Herbinaux" <LarryHerbinaux@.discussions.microsoft.com> wrote in
message news:7E65D50A-7BA1-4F5E-B62A-B8F9792C77CC@.microsoft.com...
> We have a clustered environment with each node having 8GB memory, Win2k3
> Enterprise Edition SP2, and SQL2k Enterprise Edition SP4.
> I have read a few articles on AWE and the following link provided me with
> a
> lot of information, but I still have a few questions:
> http://www.sql-server-performance.com/awe_memory.asp
> I understand that the switches that I should use are /3GB /PAE.
> In the above article it stated that AWE technology is used only for the
> RAM
> that exceeds the base 4GB of RAM. It further states that once the AWE
> Enabled option is set to 1, SQL Server will take all of the RAM except
> 128MB
> reserved for the OS. My question here is whether this statement refers to
> 128MB of the available AWE memory (e.g. the 128MB of the 4GB that is not
> from
> the base 4GB in an 8GB configuration). So with the /3GB switch and AWE
> enabled, does the operating system have approxiamtely 1.128GB dedicated to
> the OS or only 128MB (this latter seems much too low).
> When setting "Maximum Server Memory" does this refer to the entire 8GB (my
> guess is yes)? And with no other applications running, should this be set
> to
> 8GB or (8GB - 1.128GB => 6.872GB).
> The only other applications that we have running are the Vertias Client
> for
> Backups and Symantec's Antivirus besides the standard Windows 2003
> services.
> I'm sure most production environments have something very similar. What
> sould the recommended "Maximum Server Memory" be set to for a 8GB
> environment
> with these services running.
> Thanks,
> Larry
|||just to mention to be carefuly on mem counting having full 4gb of mem.
close to 4gb boundary, there may be memory mapped area used by motherboard
[pci cards etc], which may take almost 0,5gb of memory.
so, instead of 4gb, you may find available only 3,5gb appx or so
"Larry Herbinaux" <LarryHerbinaux@.discussions.microsoft.com> je napisao u
poruci interesnoj
grupi:7E65D50A-7BA1-4F5E-B62A-B8F9792C77CC@.microsoft.com...
> We have a clustered environment with each node having 8GB memory, Win2k3
> Enterprise Edition SP2, and SQL2k Enterprise Edition SP4.
> enabled, does the operating system have approxiamtely 1.128GB dedicated to
> the OS or only 128MB (this latter seems much too low).
>
> Larry
AWE / Maximum Server Memory
We have a clustered environment with each node having 8GB memory, Win2k3
Enterprise Edition SP2, and SQL2k Enterprise Edition SP4.
I have read a few articles on AWE and the following link provided me with a
lot of information, but I still have a few questions:
http://www.sql-server-performance.com/awe_memory.asp
I understand that the switches that I should use are /3GB /PAE.
In the above article it stated that AWE technology is used only for the RAM
that exceeds the base 4GB of RAM. It further states that once the AWE
Enabled option is set to 1, SQL Server will take all of the RAM except 128MB
reserved for the OS. My question here is whether this statement refers to
128MB of the available AWE memory (e.g. the 128MB of the 4GB that is not from
the base 4GB in an 8GB configuration). So with the /3GB switch and AWE
enabled, does the operating system have approxiamtely 1.128GB dedicated to
the OS or only 128MB (this latter seems much too low).
When setting "Maximum Server Memory" does this refer to the entire 8GB (my
guess is yes)? And with no other applications running, should this be set to
8GB or (8GB - 1.128GB => 6.872GB).
The only other applications that we have running are the Vertias Client for
Backups and Symantec's Antivirus besides the standard Windows 2003 services.
I'm sure most production environments have something very similar. What
sould the recommended "Maximum Server Memory" be set to for a 8GB environment
with these services running.
Thanks,
LarryLarry
> When setting "Maximum Server Memory" does this refer to the entire 8GB (my
> guess is yes)? And with no other applications running, should this be set
> to
> 8GB or (8GB - 1.128GB => 6.872GB).
Yes , you can set up even to 7GB :-))
> The only other applications that we have running are the Vertias Client
> for
> Backups and Symantec's Antivirus besides the standard Windows 2003
> services.
> I'm sure most production environments have something very similar. What
> sould the recommended "Maximum Server Memory" be set to for a 8GB
> environment
> with these services running.
You have to determine how much memory does each proccess take and
according to it set the MAX memory
"Larry Herbinaux" <LarryHerbinaux@.discussions.microsoft.com> wrote in
message news:7E65D50A-7BA1-4F5E-B62A-B8F9792C77CC@.microsoft.com...
> We have a clustered environment with each node having 8GB memory, Win2k3
> Enterprise Edition SP2, and SQL2k Enterprise Edition SP4.
> I have read a few articles on AWE and the following link provided me with
> a
> lot of information, but I still have a few questions:
> http://www.sql-server-performance.com/awe_memory.asp
> I understand that the switches that I should use are /3GB /PAE.
> In the above article it stated that AWE technology is used only for the
> RAM
> that exceeds the base 4GB of RAM. It further states that once the AWE
> Enabled option is set to 1, SQL Server will take all of the RAM except
> 128MB
> reserved for the OS. My question here is whether this statement refers to
> 128MB of the available AWE memory (e.g. the 128MB of the 4GB that is not
> from
> the base 4GB in an 8GB configuration). So with the /3GB switch and AWE
> enabled, does the operating system have approxiamtely 1.128GB dedicated to
> the OS or only 128MB (this latter seems much too low).
> When setting "Maximum Server Memory" does this refer to the entire 8GB (my
> guess is yes)? And with no other applications running, should this be set
> to
> 8GB or (8GB - 1.128GB => 6.872GB).
> The only other applications that we have running are the Vertias Client
> for
> Backups and Symantec's Antivirus besides the standard Windows 2003
> services.
> I'm sure most production environments have something very similar. What
> sould the recommended "Maximum Server Memory" be set to for a 8GB
> environment
> with these services running.
> Thanks,
> Larry|||just to mention to be carefuly on mem counting having full 4gb of mem.
close to 4gb boundary, there may be memory mapped area used by motherboard
[pci cards etc], which may take almost 0,5gb of memory.
so, instead of 4gb, you may find available only 3,5gb appx or so
"Larry Herbinaux" <LarryHerbinaux@.discussions.microsoft.com> je napisao u
poruci interesnoj
grupi:7E65D50A-7BA1-4F5E-B62A-B8F9792C77CC@.microsoft.com...
> We have a clustered environment with each node having 8GB memory, Win2k3
> Enterprise Edition SP2, and SQL2k Enterprise Edition SP4.
> enabled, does the operating system have approxiamtely 1.128GB dedicated to
> the OS or only 128MB (this latter seems much too low).
>
> Larry
Enterprise Edition SP2, and SQL2k Enterprise Edition SP4.
I have read a few articles on AWE and the following link provided me with a
lot of information, but I still have a few questions:
http://www.sql-server-performance.com/awe_memory.asp
I understand that the switches that I should use are /3GB /PAE.
In the above article it stated that AWE technology is used only for the RAM
that exceeds the base 4GB of RAM. It further states that once the AWE
Enabled option is set to 1, SQL Server will take all of the RAM except 128MB
reserved for the OS. My question here is whether this statement refers to
128MB of the available AWE memory (e.g. the 128MB of the 4GB that is not from
the base 4GB in an 8GB configuration). So with the /3GB switch and AWE
enabled, does the operating system have approxiamtely 1.128GB dedicated to
the OS or only 128MB (this latter seems much too low).
When setting "Maximum Server Memory" does this refer to the entire 8GB (my
guess is yes)? And with no other applications running, should this be set to
8GB or (8GB - 1.128GB => 6.872GB).
The only other applications that we have running are the Vertias Client for
Backups and Symantec's Antivirus besides the standard Windows 2003 services.
I'm sure most production environments have something very similar. What
sould the recommended "Maximum Server Memory" be set to for a 8GB environment
with these services running.
Thanks,
LarryLarry
> When setting "Maximum Server Memory" does this refer to the entire 8GB (my
> guess is yes)? And with no other applications running, should this be set
> to
> 8GB or (8GB - 1.128GB => 6.872GB).
Yes , you can set up even to 7GB :-))
> The only other applications that we have running are the Vertias Client
> for
> Backups and Symantec's Antivirus besides the standard Windows 2003
> services.
> I'm sure most production environments have something very similar. What
> sould the recommended "Maximum Server Memory" be set to for a 8GB
> environment
> with these services running.
You have to determine how much memory does each proccess take and
according to it set the MAX memory
"Larry Herbinaux" <LarryHerbinaux@.discussions.microsoft.com> wrote in
message news:7E65D50A-7BA1-4F5E-B62A-B8F9792C77CC@.microsoft.com...
> We have a clustered environment with each node having 8GB memory, Win2k3
> Enterprise Edition SP2, and SQL2k Enterprise Edition SP4.
> I have read a few articles on AWE and the following link provided me with
> a
> lot of information, but I still have a few questions:
> http://www.sql-server-performance.com/awe_memory.asp
> I understand that the switches that I should use are /3GB /PAE.
> In the above article it stated that AWE technology is used only for the
> RAM
> that exceeds the base 4GB of RAM. It further states that once the AWE
> Enabled option is set to 1, SQL Server will take all of the RAM except
> 128MB
> reserved for the OS. My question here is whether this statement refers to
> 128MB of the available AWE memory (e.g. the 128MB of the 4GB that is not
> from
> the base 4GB in an 8GB configuration). So with the /3GB switch and AWE
> enabled, does the operating system have approxiamtely 1.128GB dedicated to
> the OS or only 128MB (this latter seems much too low).
> When setting "Maximum Server Memory" does this refer to the entire 8GB (my
> guess is yes)? And with no other applications running, should this be set
> to
> 8GB or (8GB - 1.128GB => 6.872GB).
> The only other applications that we have running are the Vertias Client
> for
> Backups and Symantec's Antivirus besides the standard Windows 2003
> services.
> I'm sure most production environments have something very similar. What
> sould the recommended "Maximum Server Memory" be set to for a 8GB
> environment
> with these services running.
> Thanks,
> Larry|||just to mention to be carefuly on mem counting having full 4gb of mem.
close to 4gb boundary, there may be memory mapped area used by motherboard
[pci cards etc], which may take almost 0,5gb of memory.
so, instead of 4gb, you may find available only 3,5gb appx or so
"Larry Herbinaux" <LarryHerbinaux@.discussions.microsoft.com> je napisao u
poruci interesnoj
grupi:7E65D50A-7BA1-4F5E-B62A-B8F9792C77CC@.microsoft.com...
> We have a clustered environment with each node having 8GB memory, Win2k3
> Enterprise Edition SP2, and SQL2k Enterprise Edition SP4.
> enabled, does the operating system have approxiamtely 1.128GB dedicated to
> the OS or only 128MB (this latter seems much too low).
>
> Larry
AWE / Maximum Server Memory
We have a clustered environment with each node having 8GB memory, Win2k3
Enterprise Edition SP2, and SQL2k Enterprise Edition SP4.
I have read a few articles on AWE and the following link provided me with a
lot of information, but I still have a few questions:
http://www.sql-server-performance.com/awe_memory.asp
I understand that the switches that I should use are /3GB /PAE.
In the above article it stated that AWE technology is used only for the RAM
that exceeds the base 4GB of RAM. It further states that once the AWE
Enabled option is set to 1, SQL Server will take all of the RAM except 128MB
reserved for the OS. My question here is whether this statement refers to
128MB of the available AWE memory (e.g. the 128MB of the 4GB that is not fro
m
the base 4GB in an 8GB configuration). So with the /3GB switch and AWE
enabled, does the operating system have approxiamtely 1.128GB dedicated to
the OS or only 128MB (this latter seems much too low).
When setting "Maximum Server Memory" does this refer to the entire 8GB (my
guess is yes)? And with no other applications running, should this be set t
o
8GB or (8GB - 1.128GB => 6.872GB).
The only other applications that we have running are the Vertias Client for
Backups and Symantec's Antivirus besides the standard Windows 2003 services.
I'm sure most production environments have something very similar. What
sould the recommended "Maximum Server Memory" be set to for a 8GB environmen
t
with these services running.
Thanks,
LarryLarry
> When setting "Maximum Server Memory" does this refer to the entire 8GB (my
> guess is yes)? And with no other applications running, should this be set
> to
> 8GB or (8GB - 1.128GB => 6.872GB).
Yes , you can set up even to 7GB :-))
> The only other applications that we have running are the Vertias Client
> for
> Backups and Symantec's Antivirus besides the standard Windows 2003
> services.
> I'm sure most production environments have something very similar. What
> sould the recommended "Maximum Server Memory" be set to for a 8GB
> environment
> with these services running.
You have to determine how much memory does each proccess take and
according to it set the MAX memory
"Larry Herbinaux" <LarryHerbinaux@.discussions.microsoft.com> wrote in
message news:7E65D50A-7BA1-4F5E-B62A-B8F9792C77CC@.microsoft.com...
> We have a clustered environment with each node having 8GB memory, Win2k3
> Enterprise Edition SP2, and SQL2k Enterprise Edition SP4.
> I have read a few articles on AWE and the following link provided me with
> a
> lot of information, but I still have a few questions:
> http://www.sql-server-performance.com/awe_memory.asp
> I understand that the switches that I should use are /3GB /PAE.
> In the above article it stated that AWE technology is used only for the
> RAM
> that exceeds the base 4GB of RAM. It further states that once the AWE
> Enabled option is set to 1, SQL Server will take all of the RAM except
> 128MB
> reserved for the OS. My question here is whether this statement refers to
> 128MB of the available AWE memory (e.g. the 128MB of the 4GB that is not
> from
> the base 4GB in an 8GB configuration). So with the /3GB switch and AWE
> enabled, does the operating system have approxiamtely 1.128GB dedicated to
> the OS or only 128MB (this latter seems much too low).
> When setting "Maximum Server Memory" does this refer to the entire 8GB (my
> guess is yes)? And with no other applications running, should this be set
> to
> 8GB or (8GB - 1.128GB => 6.872GB).
> The only other applications that we have running are the Vertias Client
> for
> Backups and Symantec's Antivirus besides the standard Windows 2003
> services.
> I'm sure most production environments have something very similar. What
> sould the recommended "Maximum Server Memory" be set to for a 8GB
> environment
> with these services running.
> Thanks,
> Larry|||just to mention to be carefuly on mem counting having full 4gb of mem.
close to 4gb boundary, there may be memory mapped area used by motherboard
[pci cards etc], which may take almost 0,5gb of memory.
so, instead of 4gb, you may find available only 3,5gb appx or so
"Larry Herbinaux" <LarryHerbinaux@.discussions.microsoft.com> je napisao u
poruci interesnoj
grupi:7E65D50A-7BA1-4F5E-B62A-B8F9792C77CC@.microsoft.com...
> We have a clustered environment with each node having 8GB memory, Win2k3
> Enterprise Edition SP2, and SQL2k Enterprise Edition SP4.
> enabled, does the operating system have approxiamtely 1.128GB dedicated to
> the OS or only 128MB (this latter seems much too low).
>
> Larry
Enterprise Edition SP2, and SQL2k Enterprise Edition SP4.
I have read a few articles on AWE and the following link provided me with a
lot of information, but I still have a few questions:
http://www.sql-server-performance.com/awe_memory.asp
I understand that the switches that I should use are /3GB /PAE.
In the above article it stated that AWE technology is used only for the RAM
that exceeds the base 4GB of RAM. It further states that once the AWE
Enabled option is set to 1, SQL Server will take all of the RAM except 128MB
reserved for the OS. My question here is whether this statement refers to
128MB of the available AWE memory (e.g. the 128MB of the 4GB that is not fro
m
the base 4GB in an 8GB configuration). So with the /3GB switch and AWE
enabled, does the operating system have approxiamtely 1.128GB dedicated to
the OS or only 128MB (this latter seems much too low).
When setting "Maximum Server Memory" does this refer to the entire 8GB (my
guess is yes)? And with no other applications running, should this be set t
o
8GB or (8GB - 1.128GB => 6.872GB).
The only other applications that we have running are the Vertias Client for
Backups and Symantec's Antivirus besides the standard Windows 2003 services.
I'm sure most production environments have something very similar. What
sould the recommended "Maximum Server Memory" be set to for a 8GB environmen
t
with these services running.
Thanks,
LarryLarry
> When setting "Maximum Server Memory" does this refer to the entire 8GB (my
> guess is yes)? And with no other applications running, should this be set
> to
> 8GB or (8GB - 1.128GB => 6.872GB).
Yes , you can set up even to 7GB :-))
> The only other applications that we have running are the Vertias Client
> for
> Backups and Symantec's Antivirus besides the standard Windows 2003
> services.
> I'm sure most production environments have something very similar. What
> sould the recommended "Maximum Server Memory" be set to for a 8GB
> environment
> with these services running.
You have to determine how much memory does each proccess take and
according to it set the MAX memory
"Larry Herbinaux" <LarryHerbinaux@.discussions.microsoft.com> wrote in
message news:7E65D50A-7BA1-4F5E-B62A-B8F9792C77CC@.microsoft.com...
> We have a clustered environment with each node having 8GB memory, Win2k3
> Enterprise Edition SP2, and SQL2k Enterprise Edition SP4.
> I have read a few articles on AWE and the following link provided me with
> a
> lot of information, but I still have a few questions:
> http://www.sql-server-performance.com/awe_memory.asp
> I understand that the switches that I should use are /3GB /PAE.
> In the above article it stated that AWE technology is used only for the
> RAM
> that exceeds the base 4GB of RAM. It further states that once the AWE
> Enabled option is set to 1, SQL Server will take all of the RAM except
> 128MB
> reserved for the OS. My question here is whether this statement refers to
> 128MB of the available AWE memory (e.g. the 128MB of the 4GB that is not
> from
> the base 4GB in an 8GB configuration). So with the /3GB switch and AWE
> enabled, does the operating system have approxiamtely 1.128GB dedicated to
> the OS or only 128MB (this latter seems much too low).
> When setting "Maximum Server Memory" does this refer to the entire 8GB (my
> guess is yes)? And with no other applications running, should this be set
> to
> 8GB or (8GB - 1.128GB => 6.872GB).
> The only other applications that we have running are the Vertias Client
> for
> Backups and Symantec's Antivirus besides the standard Windows 2003
> services.
> I'm sure most production environments have something very similar. What
> sould the recommended "Maximum Server Memory" be set to for a 8GB
> environment
> with these services running.
> Thanks,
> Larry|||just to mention to be carefuly on mem counting having full 4gb of mem.
close to 4gb boundary, there may be memory mapped area used by motherboard
[pci cards etc], which may take almost 0,5gb of memory.
so, instead of 4gb, you may find available only 3,5gb appx or so
"Larry Herbinaux" <LarryHerbinaux@.discussions.microsoft.com> je napisao u
poruci interesnoj
grupi:7E65D50A-7BA1-4F5E-B62A-B8F9792C77CC@.microsoft.com...
> We have a clustered environment with each node having 8GB memory, Win2k3
> Enterprise Edition SP2, and SQL2k Enterprise Edition SP4.
> enabled, does the operating system have approxiamtely 1.128GB dedicated to
> the OS or only 128MB (this latter seems much too low).
>
> Larry
AWE
Our current production environment consists of an 2 node (active-active) SQL
Server 2000 SP3a database cluster. It was recently rebuilt and we did not
reenable Address Windowing Extensions (AWE). Is it recommended that I turn
it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I am
asking this because it appears to be performing well with AWE off. Also
should I allocate 7 GB of RAM to for 'max server memory'? It is not set now,
but is performing well without it.
Thanks,
Jay
Hi,
If you have 8 GB ram please enable AWE. My value for SQL Server will be from
6 to 6.5 GB.
I will leave the rest to OS and other applications.
Thanks
Hari
SQL Server MVP
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
> Our current production environment consists of an 2 node (active-active)
> SQL
> Server 2000 SP3a database cluster. It was recently rebuilt and we did not
> reenable Address Windowing Extensions (AWE). Is it recommended that I
> turn
> it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I
> am
> asking this because it appears to be performing well with AWE off. Also
> should I allocate 7 GB of RAM to for 'max server memory'? It is not set
> now,
> but is performing well without it.
> Thanks,
> Jay
|||"jay d" wrote:
> Our current production environment consists of an 2 node (active-active) SQL
> Server 2000 SP3a database cluster. It was recently rebuilt and we did not
> reenable Address Windowing Extensions (AWE). Is it recommended that I turn
> it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I am
> asking this because it appears to be performing well with AWE off. Also
> should I allocate 7 GB of RAM to for 'max server memory'? It is not set now,
> but is performing well without it.
Jay,
If the servers are running well without AWE, I would say keep it turned
off.
In my experience, the AWE implementation has some bugs. Better to keep
it simple unless you need the extra memory.
-- J
|||Just because you have lots of ram does not mean sql server will be able to
use it all effectively. It depends a lot on your data and how you access it.
If your cache hit ratio and page life expectancy arealways high and your
response times are good you may not need to turn it on. But if you do you
certainly should not set it to 7gb since you have an active - active
configuration. Since AWE memory is not dynamic you can have a situation
where one instance gets 7GB and leaves only 1GB for the other instance and
the OS and performance will suffer on all fronts.
Andrew J. Kelly SQL MVP
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
> Our current production environment consists of an 2 node (active-active)
> SQL
> Server 2000 SP3a database cluster. It was recently rebuilt and we did not
> reenable Address Windowing Extensions (AWE). Is it recommended that I
> turn
> it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I
> am
> asking this because it appears to be performing well with AWE off. Also
> should I allocate 7 GB of RAM to for 'max server memory'? It is not set
> now,
> but is performing well without it.
> Thanks,
> Jay
|||Thank you all for the help. One more quick question. If I am 3 instances
should I set the max server memory to 7 GIG on each of them or do I divide
the RAM among the 3 instances? ex Instance 1 - 3 GIG, Instance 2 - 3 GIG,
and Instance 3 - 2 GIG.
Thanks,
Jay
"Andrew J. Kelly" wrote:
> Just because you have lots of ram does not mean sql server will be able to
> use it all effectively. It depends a lot on your data and how you access it.
> If your cache hit ratio and page life expectancy arealways high and your
> response times are good you may not need to turn it on. But if you do you
> certainly should not set it to 7gb since you have an active - active
> configuration. Since AWE memory is not dynamic you can have a situation
> where one instance gets 7GB and leaves only 1GB for the other instance and
> the OS and performance will suffer on all fronts.
> --
> Andrew J. Kelly SQL MVP
>
> "jay d" <jayd@.discussions.microsoft.com> wrote in message
> news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
>
>
|||As I stated when you set AWE it is no longer dynamic. The first instance to
come up will grab all the memory it can up to the MAX Memory setting. If
you set it to 7GB for each instance and you only have 8GB total there isn't
enough to go around. When you use AWE you can not share the memory. So if
you really do have three instances that is probably the real reason why AWE
is turned off to begin with.
Andrew J. Kelly SQL MVP
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:9144E391-55F4-4B7F-9858-321A6973AE50@.microsoft.com...[vbcol=seagreen]
> Thank you all for the help. One more quick question. If I am 3 instances
> should I set the max server memory to 7 GIG on each of them or do I divide
> the RAM among the 3 instances? ex Instance 1 - 3 GIG, Instance 2 - 3 GIG,
> and Instance 3 - 2 GIG.
> Thanks,
> Jay
> "Andrew J. Kelly" wrote:
|||Hi,
Thanks, I will enable AWE. If I have 2 instances of SQL running, should I
set each instance to 3 GIG RAM and then leave 2 GIG for the OS, just in case
one node of the cluster fails and both instances end up on the same node for
awhile?
Thanks,
Jay
"Hari Prasad" wrote:
> Hi,
> If you have 8 GB ram please enable AWE. My value for SQL Server will be from
> 6 to 6.5 GB.
> I will leave the rest to OS and other applications.
> Thanks
> Hari
> SQL Server MVP
> "jay d" <jayd@.discussions.microsoft.com> wrote in message
> news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
>
>
|||Just be sure not to apply SP4 for SQL Server. There is a bug with respect
to AWE. They are working on a fix.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:8A900118-4F9B-4378-87F5-15EA79CC42F4@.microsoft.com...
Hi,
Thanks, I will enable AWE. If I have 2 instances of SQL running, should I
set each instance to 3 GIG RAM and then leave 2 GIG for the OS, just in case
one node of the cluster fails and both instances end up on the same node for
awhile?
Thanks,
Jay
"Hari Prasad" wrote:
> Hi,
> If you have 8 GB ram please enable AWE. My value for SQL Server will be
> from
> 6 to 6.5 GB.
> I will leave the rest to OS and other applications.
> Thanks
> Hari
> SQL Server MVP
> "jay d" <jayd@.discussions.microsoft.com> wrote in message
> news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
>
>
Server 2000 SP3a database cluster. It was recently rebuilt and we did not
reenable Address Windowing Extensions (AWE). Is it recommended that I turn
it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I am
asking this because it appears to be performing well with AWE off. Also
should I allocate 7 GB of RAM to for 'max server memory'? It is not set now,
but is performing well without it.
Thanks,
Jay
Hi,
If you have 8 GB ram please enable AWE. My value for SQL Server will be from
6 to 6.5 GB.
I will leave the rest to OS and other applications.
Thanks
Hari
SQL Server MVP
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
> Our current production environment consists of an 2 node (active-active)
> SQL
> Server 2000 SP3a database cluster. It was recently rebuilt and we did not
> reenable Address Windowing Extensions (AWE). Is it recommended that I
> turn
> it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I
> am
> asking this because it appears to be performing well with AWE off. Also
> should I allocate 7 GB of RAM to for 'max server memory'? It is not set
> now,
> but is performing well without it.
> Thanks,
> Jay
|||"jay d" wrote:
> Our current production environment consists of an 2 node (active-active) SQL
> Server 2000 SP3a database cluster. It was recently rebuilt and we did not
> reenable Address Windowing Extensions (AWE). Is it recommended that I turn
> it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I am
> asking this because it appears to be performing well with AWE off. Also
> should I allocate 7 GB of RAM to for 'max server memory'? It is not set now,
> but is performing well without it.
Jay,
If the servers are running well without AWE, I would say keep it turned
off.
In my experience, the AWE implementation has some bugs. Better to keep
it simple unless you need the extra memory.
-- J
|||Just because you have lots of ram does not mean sql server will be able to
use it all effectively. It depends a lot on your data and how you access it.
If your cache hit ratio and page life expectancy arealways high and your
response times are good you may not need to turn it on. But if you do you
certainly should not set it to 7gb since you have an active - active
configuration. Since AWE memory is not dynamic you can have a situation
where one instance gets 7GB and leaves only 1GB for the other instance and
the OS and performance will suffer on all fronts.
Andrew J. Kelly SQL MVP
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
> Our current production environment consists of an 2 node (active-active)
> SQL
> Server 2000 SP3a database cluster. It was recently rebuilt and we did not
> reenable Address Windowing Extensions (AWE). Is it recommended that I
> turn
> it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I
> am
> asking this because it appears to be performing well with AWE off. Also
> should I allocate 7 GB of RAM to for 'max server memory'? It is not set
> now,
> but is performing well without it.
> Thanks,
> Jay
|||Thank you all for the help. One more quick question. If I am 3 instances
should I set the max server memory to 7 GIG on each of them or do I divide
the RAM among the 3 instances? ex Instance 1 - 3 GIG, Instance 2 - 3 GIG,
and Instance 3 - 2 GIG.
Thanks,
Jay
"Andrew J. Kelly" wrote:
> Just because you have lots of ram does not mean sql server will be able to
> use it all effectively. It depends a lot on your data and how you access it.
> If your cache hit ratio and page life expectancy arealways high and your
> response times are good you may not need to turn it on. But if you do you
> certainly should not set it to 7gb since you have an active - active
> configuration. Since AWE memory is not dynamic you can have a situation
> where one instance gets 7GB and leaves only 1GB for the other instance and
> the OS and performance will suffer on all fronts.
> --
> Andrew J. Kelly SQL MVP
>
> "jay d" <jayd@.discussions.microsoft.com> wrote in message
> news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
>
>
|||As I stated when you set AWE it is no longer dynamic. The first instance to
come up will grab all the memory it can up to the MAX Memory setting. If
you set it to 7GB for each instance and you only have 8GB total there isn't
enough to go around. When you use AWE you can not share the memory. So if
you really do have three instances that is probably the real reason why AWE
is turned off to begin with.
Andrew J. Kelly SQL MVP
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:9144E391-55F4-4B7F-9858-321A6973AE50@.microsoft.com...[vbcol=seagreen]
> Thank you all for the help. One more quick question. If I am 3 instances
> should I set the max server memory to 7 GIG on each of them or do I divide
> the RAM among the 3 instances? ex Instance 1 - 3 GIG, Instance 2 - 3 GIG,
> and Instance 3 - 2 GIG.
> Thanks,
> Jay
> "Andrew J. Kelly" wrote:
|||Hi,
Thanks, I will enable AWE. If I have 2 instances of SQL running, should I
set each instance to 3 GIG RAM and then leave 2 GIG for the OS, just in case
one node of the cluster fails and both instances end up on the same node for
awhile?
Thanks,
Jay
"Hari Prasad" wrote:
> Hi,
> If you have 8 GB ram please enable AWE. My value for SQL Server will be from
> 6 to 6.5 GB.
> I will leave the rest to OS and other applications.
> Thanks
> Hari
> SQL Server MVP
> "jay d" <jayd@.discussions.microsoft.com> wrote in message
> news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
>
>
|||Just be sure not to apply SP4 for SQL Server. There is a bug with respect
to AWE. They are working on a fix.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:8A900118-4F9B-4378-87F5-15EA79CC42F4@.microsoft.com...
Hi,
Thanks, I will enable AWE. If I have 2 instances of SQL running, should I
set each instance to 3 GIG RAM and then leave 2 GIG for the OS, just in case
one node of the cluster fails and both instances end up on the same node for
awhile?
Thanks,
Jay
"Hari Prasad" wrote:
> Hi,
> If you have 8 GB ram please enable AWE. My value for SQL Server will be
> from
> 6 to 6.5 GB.
> I will leave the rest to OS and other applications.
> Thanks
> Hari
> SQL Server MVP
> "jay d" <jayd@.discussions.microsoft.com> wrote in message
> news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
>
>
AWE
Our current production environment consists of an 2 node (active-active) SQL
Server 2000 SP3a database cluster. It was recently rebuilt and we did not
reenable Address Windowing Extensions (AWE). Is it recommended that I turn
it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I am
asking this because it appears to be performing well with AWE off. Also
should I allocate 7 GB of RAM to for 'max server memory'? It is not set now,
but is performing well without it.
Thanks,
JayHi,
If you have 8 GB ram please enable AWE. My value for SQL Server will be from
6 to 6.5 GB.
I will leave the rest to OS and other applications.
Thanks
Hari
SQL Server MVP
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
> Our current production environment consists of an 2 node (active-active)
> SQL
> Server 2000 SP3a database cluster. It was recently rebuilt and we did not
> reenable Address Windowing Extensions (AWE). Is it recommended that I
> turn
> it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I
> am
> asking this because it appears to be performing well with AWE off. Also
> should I allocate 7 GB of RAM to for 'max server memory'? It is not set
> now,
> but is performing well without it.
> Thanks,
> Jay|||"jay d" wrote:
> Our current production environment consists of an 2 node (active-active) SQL
> Server 2000 SP3a database cluster. It was recently rebuilt and we did not
> reenable Address Windowing Extensions (AWE). Is it recommended that I turn
> it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I am
> asking this because it appears to be performing well with AWE off. Also
> should I allocate 7 GB of RAM to for 'max server memory'? It is not set now,
> but is performing well without it.
Jay,
If the servers are running well without AWE, I would say keep it turned
off.
In my experience, the AWE implementation has some bugs. Better to keep
it simple unless you need the extra memory.
-- J|||Just because you have lots of ram does not mean sql server will be able to
use it all effectively. It depends a lot on your data and how you access it.
If your cache hit ratio and page life expectancy arealways high and your
response times are good you may not need to turn it on. But if you do you
certainly should not set it to 7gb since you have an active - active
configuration. Since AWE memory is not dynamic you can have a situation
where one instance gets 7GB and leaves only 1GB for the other instance and
the OS and performance will suffer on all fronts.
--
Andrew J. Kelly SQL MVP
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
> Our current production environment consists of an 2 node (active-active)
> SQL
> Server 2000 SP3a database cluster. It was recently rebuilt and we did not
> reenable Address Windowing Extensions (AWE). Is it recommended that I
> turn
> it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I
> am
> asking this because it appears to be performing well with AWE off. Also
> should I allocate 7 GB of RAM to for 'max server memory'? It is not set
> now,
> but is performing well without it.
> Thanks,
> Jay|||Thank you all for the help. One more quick question. If I am 3 instances
should I set the max server memory to 7 GIG on each of them or do I divide
the RAM among the 3 instances? ex Instance 1 - 3 GIG, Instance 2 - 3 GIG,
and Instance 3 - 2 GIG.
Thanks,
Jay
"Andrew J. Kelly" wrote:
> Just because you have lots of ram does not mean sql server will be able to
> use it all effectively. It depends a lot on your data and how you access it.
> If your cache hit ratio and page life expectancy arealways high and your
> response times are good you may not need to turn it on. But if you do you
> certainly should not set it to 7gb since you have an active - active
> configuration. Since AWE memory is not dynamic you can have a situation
> where one instance gets 7GB and leaves only 1GB for the other instance and
> the OS and performance will suffer on all fronts.
> --
> Andrew J. Kelly SQL MVP
>
> "jay d" <jayd@.discussions.microsoft.com> wrote in message
> news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
> > Our current production environment consists of an 2 node (active-active)
> > SQL
> > Server 2000 SP3a database cluster. It was recently rebuilt and we did not
> > reenable Address Windowing Extensions (AWE). Is it recommended that I
> > turn
> > it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I
> > am
> > asking this because it appears to be performing well with AWE off. Also
> > should I allocate 7 GB of RAM to for 'max server memory'? It is not set
> > now,
> > but is performing well without it.
> >
> > Thanks,
> > Jay
>
>|||As I stated when you set AWE it is no longer dynamic. The first instance to
come up will grab all the memory it can up to the MAX Memory setting. If
you set it to 7GB for each instance and you only have 8GB total there isn't
enough to go around. When you use AWE you can not share the memory. So if
you really do have three instances that is probably the real reason why AWE
is turned off to begin with.
--
Andrew J. Kelly SQL MVP
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:9144E391-55F4-4B7F-9858-321A6973AE50@.microsoft.com...
> Thank you all for the help. One more quick question. If I am 3 instances
> should I set the max server memory to 7 GIG on each of them or do I divide
> the RAM among the 3 instances? ex Instance 1 - 3 GIG, Instance 2 - 3 GIG,
> and Instance 3 - 2 GIG.
> Thanks,
> Jay
> "Andrew J. Kelly" wrote:
>> Just because you have lots of ram does not mean sql server will be able
>> to
>> use it all effectively. It depends a lot on your data and how you access
>> it.
>> If your cache hit ratio and page life expectancy arealways high and your
>> response times are good you may not need to turn it on. But if you do
>> you
>> certainly should not set it to 7gb since you have an active - active
>> configuration. Since AWE memory is not dynamic you can have a situation
>> where one instance gets 7GB and leaves only 1GB for the other instance
>> and
>> the OS and performance will suffer on all fronts.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "jay d" <jayd@.discussions.microsoft.com> wrote in message
>> news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
>> > Our current production environment consists of an 2 node
>> > (active-active)
>> > SQL
>> > Server 2000 SP3a database cluster. It was recently rebuilt and we did
>> > not
>> > reenable Address Windowing Extensions (AWE). Is it recommended that I
>> > turn
>> > it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM.
>> > I
>> > am
>> > asking this because it appears to be performing well with AWE off.
>> > Also
>> > should I allocate 7 GB of RAM to for 'max server memory'? It is not
>> > set
>> > now,
>> > but is performing well without it.
>> >
>> > Thanks,
>> > Jay
>>|||Hi,
Thanks, I will enable AWE. If I have 2 instances of SQL running, should I
set each instance to 3 GIG RAM and then leave 2 GIG for the OS, just in case
one node of the cluster fails and both instances end up on the same node for
awhile?
Thanks,
Jay
"Hari Prasad" wrote:
> Hi,
> If you have 8 GB ram please enable AWE. My value for SQL Server will be from
> 6 to 6.5 GB.
> I will leave the rest to OS and other applications.
> Thanks
> Hari
> SQL Server MVP
> "jay d" <jayd@.discussions.microsoft.com> wrote in message
> news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
> > Our current production environment consists of an 2 node (active-active)
> > SQL
> > Server 2000 SP3a database cluster. It was recently rebuilt and we did not
> > reenable Address Windowing Extensions (AWE). Is it recommended that I
> > turn
> > it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I
> > am
> > asking this because it appears to be performing well with AWE off. Also
> > should I allocate 7 GB of RAM to for 'max server memory'? It is not set
> > now,
> > but is performing well without it.
> >
> > Thanks,
> > Jay
>
>|||Just be sure not to apply SP4 for SQL Server. There is a bug with respect
to AWE. They are working on a fix.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:8A900118-4F9B-4378-87F5-15EA79CC42F4@.microsoft.com...
Hi,
Thanks, I will enable AWE. If I have 2 instances of SQL running, should I
set each instance to 3 GIG RAM and then leave 2 GIG for the OS, just in case
one node of the cluster fails and both instances end up on the same node for
awhile?
Thanks,
Jay
"Hari Prasad" wrote:
> Hi,
> If you have 8 GB ram please enable AWE. My value for SQL Server will be
> from
> 6 to 6.5 GB.
> I will leave the rest to OS and other applications.
> Thanks
> Hari
> SQL Server MVP
> "jay d" <jayd@.discussions.microsoft.com> wrote in message
> news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
> > Our current production environment consists of an 2 node (active-active)
> > SQL
> > Server 2000 SP3a database cluster. It was recently rebuilt and we did
> > not
> > reenable Address Windowing Extensions (AWE). Is it recommended that I
> > turn
> > it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I
> > am
> > asking this because it appears to be performing well with AWE off. Also
> > should I allocate 7 GB of RAM to for 'max server memory'? It is not set
> > now,
> > but is performing well without it.
> >
> > Thanks,
> > Jay
>
>
Server 2000 SP3a database cluster. It was recently rebuilt and we did not
reenable Address Windowing Extensions (AWE). Is it recommended that I turn
it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I am
asking this because it appears to be performing well with AWE off. Also
should I allocate 7 GB of RAM to for 'max server memory'? It is not set now,
but is performing well without it.
Thanks,
JayHi,
If you have 8 GB ram please enable AWE. My value for SQL Server will be from
6 to 6.5 GB.
I will leave the rest to OS and other applications.
Thanks
Hari
SQL Server MVP
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
> Our current production environment consists of an 2 node (active-active)
> SQL
> Server 2000 SP3a database cluster. It was recently rebuilt and we did not
> reenable Address Windowing Extensions (AWE). Is it recommended that I
> turn
> it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I
> am
> asking this because it appears to be performing well with AWE off. Also
> should I allocate 7 GB of RAM to for 'max server memory'? It is not set
> now,
> but is performing well without it.
> Thanks,
> Jay|||"jay d" wrote:
> Our current production environment consists of an 2 node (active-active) SQL
> Server 2000 SP3a database cluster. It was recently rebuilt and we did not
> reenable Address Windowing Extensions (AWE). Is it recommended that I turn
> it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I am
> asking this because it appears to be performing well with AWE off. Also
> should I allocate 7 GB of RAM to for 'max server memory'? It is not set now,
> but is performing well without it.
Jay,
If the servers are running well without AWE, I would say keep it turned
off.
In my experience, the AWE implementation has some bugs. Better to keep
it simple unless you need the extra memory.
-- J|||Just because you have lots of ram does not mean sql server will be able to
use it all effectively. It depends a lot on your data and how you access it.
If your cache hit ratio and page life expectancy arealways high and your
response times are good you may not need to turn it on. But if you do you
certainly should not set it to 7gb since you have an active - active
configuration. Since AWE memory is not dynamic you can have a situation
where one instance gets 7GB and leaves only 1GB for the other instance and
the OS and performance will suffer on all fronts.
--
Andrew J. Kelly SQL MVP
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
> Our current production environment consists of an 2 node (active-active)
> SQL
> Server 2000 SP3a database cluster. It was recently rebuilt and we did not
> reenable Address Windowing Extensions (AWE). Is it recommended that I
> turn
> it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I
> am
> asking this because it appears to be performing well with AWE off. Also
> should I allocate 7 GB of RAM to for 'max server memory'? It is not set
> now,
> but is performing well without it.
> Thanks,
> Jay|||Thank you all for the help. One more quick question. If I am 3 instances
should I set the max server memory to 7 GIG on each of them or do I divide
the RAM among the 3 instances? ex Instance 1 - 3 GIG, Instance 2 - 3 GIG,
and Instance 3 - 2 GIG.
Thanks,
Jay
"Andrew J. Kelly" wrote:
> Just because you have lots of ram does not mean sql server will be able to
> use it all effectively. It depends a lot on your data and how you access it.
> If your cache hit ratio and page life expectancy arealways high and your
> response times are good you may not need to turn it on. But if you do you
> certainly should not set it to 7gb since you have an active - active
> configuration. Since AWE memory is not dynamic you can have a situation
> where one instance gets 7GB and leaves only 1GB for the other instance and
> the OS and performance will suffer on all fronts.
> --
> Andrew J. Kelly SQL MVP
>
> "jay d" <jayd@.discussions.microsoft.com> wrote in message
> news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
> > Our current production environment consists of an 2 node (active-active)
> > SQL
> > Server 2000 SP3a database cluster. It was recently rebuilt and we did not
> > reenable Address Windowing Extensions (AWE). Is it recommended that I
> > turn
> > it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I
> > am
> > asking this because it appears to be performing well with AWE off. Also
> > should I allocate 7 GB of RAM to for 'max server memory'? It is not set
> > now,
> > but is performing well without it.
> >
> > Thanks,
> > Jay
>
>|||As I stated when you set AWE it is no longer dynamic. The first instance to
come up will grab all the memory it can up to the MAX Memory setting. If
you set it to 7GB for each instance and you only have 8GB total there isn't
enough to go around. When you use AWE you can not share the memory. So if
you really do have three instances that is probably the real reason why AWE
is turned off to begin with.
--
Andrew J. Kelly SQL MVP
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:9144E391-55F4-4B7F-9858-321A6973AE50@.microsoft.com...
> Thank you all for the help. One more quick question. If I am 3 instances
> should I set the max server memory to 7 GIG on each of them or do I divide
> the RAM among the 3 instances? ex Instance 1 - 3 GIG, Instance 2 - 3 GIG,
> and Instance 3 - 2 GIG.
> Thanks,
> Jay
> "Andrew J. Kelly" wrote:
>> Just because you have lots of ram does not mean sql server will be able
>> to
>> use it all effectively. It depends a lot on your data and how you access
>> it.
>> If your cache hit ratio and page life expectancy arealways high and your
>> response times are good you may not need to turn it on. But if you do
>> you
>> certainly should not set it to 7gb since you have an active - active
>> configuration. Since AWE memory is not dynamic you can have a situation
>> where one instance gets 7GB and leaves only 1GB for the other instance
>> and
>> the OS and performance will suffer on all fronts.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "jay d" <jayd@.discussions.microsoft.com> wrote in message
>> news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
>> > Our current production environment consists of an 2 node
>> > (active-active)
>> > SQL
>> > Server 2000 SP3a database cluster. It was recently rebuilt and we did
>> > not
>> > reenable Address Windowing Extensions (AWE). Is it recommended that I
>> > turn
>> > it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM.
>> > I
>> > am
>> > asking this because it appears to be performing well with AWE off.
>> > Also
>> > should I allocate 7 GB of RAM to for 'max server memory'? It is not
>> > set
>> > now,
>> > but is performing well without it.
>> >
>> > Thanks,
>> > Jay
>>|||Hi,
Thanks, I will enable AWE. If I have 2 instances of SQL running, should I
set each instance to 3 GIG RAM and then leave 2 GIG for the OS, just in case
one node of the cluster fails and both instances end up on the same node for
awhile?
Thanks,
Jay
"Hari Prasad" wrote:
> Hi,
> If you have 8 GB ram please enable AWE. My value for SQL Server will be from
> 6 to 6.5 GB.
> I will leave the rest to OS and other applications.
> Thanks
> Hari
> SQL Server MVP
> "jay d" <jayd@.discussions.microsoft.com> wrote in message
> news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
> > Our current production environment consists of an 2 node (active-active)
> > SQL
> > Server 2000 SP3a database cluster. It was recently rebuilt and we did not
> > reenable Address Windowing Extensions (AWE). Is it recommended that I
> > turn
> > it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I
> > am
> > asking this because it appears to be performing well with AWE off. Also
> > should I allocate 7 GB of RAM to for 'max server memory'? It is not set
> > now,
> > but is performing well without it.
> >
> > Thanks,
> > Jay
>
>|||Just be sure not to apply SP4 for SQL Server. There is a bug with respect
to AWE. They are working on a fix.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:8A900118-4F9B-4378-87F5-15EA79CC42F4@.microsoft.com...
Hi,
Thanks, I will enable AWE. If I have 2 instances of SQL running, should I
set each instance to 3 GIG RAM and then leave 2 GIG for the OS, just in case
one node of the cluster fails and both instances end up on the same node for
awhile?
Thanks,
Jay
"Hari Prasad" wrote:
> Hi,
> If you have 8 GB ram please enable AWE. My value for SQL Server will be
> from
> 6 to 6.5 GB.
> I will leave the rest to OS and other applications.
> Thanks
> Hari
> SQL Server MVP
> "jay d" <jayd@.discussions.microsoft.com> wrote in message
> news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
> > Our current production environment consists of an 2 node (active-active)
> > SQL
> > Server 2000 SP3a database cluster. It was recently rebuilt and we did
> > not
> > reenable Address Windowing Extensions (AWE). Is it recommended that I
> > turn
> > it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I
> > am
> > asking this because it appears to be performing well with AWE off. Also
> > should I allocate 7 GB of RAM to for 'max server memory'? It is not set
> > now,
> > but is performing well without it.
> >
> > Thanks,
> > Jay
>
>
AWE
Our current production environment consists of an 2 node (active-active) SQL
Server 2000 SP3a database cluster. It was recently rebuilt and we did not
reenable Address Windowing Extensions (AWE). Is it recommended that I turn
it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I am
asking this because it appears to be performing well with AWE off. Also
should I allocate 7 GB of RAM to for 'max server memory'? It is not set now
,
but is performing well without it.
Thanks,
JayHi,
If you have 8 GB ram please enable AWE. My value for SQL Server will be from
6 to 6.5 GB.
I will leave the rest to OS and other applications.
Thanks
Hari
SQL Server MVP
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
> Our current production environment consists of an 2 node (active-active)
> SQL
> Server 2000 SP3a database cluster. It was recently rebuilt and we did not
> reenable Address Windowing Extensions (AWE). Is it recommended that I
> turn
> it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I
> am
> asking this because it appears to be performing well with AWE off. Also
> should I allocate 7 GB of RAM to for 'max server memory'? It is not set
> now,
> but is performing well without it.
> Thanks,
> Jay|||"jay d" wrote:
> Our current production environment consists of an 2 node (active-active) S
QL
> Server 2000 SP3a database cluster. It was recently rebuilt and we did not
> reenable Address Windowing Extensions (AWE). Is it recommended that I tur
n
> it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I a
m
> asking this because it appears to be performing well with AWE off. Also
> should I allocate 7 GB of RAM to for 'max server memory'? It is not set n
ow,
> but is performing well without it.
Jay,
If the servers are running well without AWE, I would say keep it turned
off.
In my experience, the AWE implementation has some bugs. Better to keep
it simple unless you need the extra memory.
-- J|||Just because you have lots of ram does not mean sql server will be able to
use it all effectively. It depends a lot on your data and how you access it.
If your cache hit ratio and page life expectancy arealways high and your
response times are good you may not need to turn it on. But if you do you
certainly should not set it to 7gb since you have an active - active
configuration. Since AWE memory is not dynamic you can have a situation
where one instance gets 7GB and leaves only 1GB for the other instance and
the OS and performance will suffer on all fronts.
Andrew J. Kelly SQL MVP
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
> Our current production environment consists of an 2 node (active-active)
> SQL
> Server 2000 SP3a database cluster. It was recently rebuilt and we did not
> reenable Address Windowing Extensions (AWE). Is it recommended that I
> turn
> it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I
> am
> asking this because it appears to be performing well with AWE off. Also
> should I allocate 7 GB of RAM to for 'max server memory'? It is not set
> now,
> but is performing well without it.
> Thanks,
> Jay|||Thank you all for the help. One more quick question. If I am 3 instances
should I set the max server memory to 7 GIG on each of them or do I divide
the RAM among the 3 instances? ex Instance 1 - 3 GIG, Instance 2 - 3 GIG,
and Instance 3 - 2 GIG.
Thanks,
Jay
"Andrew J. Kelly" wrote:
> Just because you have lots of ram does not mean sql server will be able to
> use it all effectively. It depends a lot on your data and how you access i
t.
> If your cache hit ratio and page life expectancy arealways high and your
> response times are good you may not need to turn it on. But if you do you
> certainly should not set it to 7gb since you have an active - active
> configuration. Since AWE memory is not dynamic you can have a situation
> where one instance gets 7GB and leaves only 1GB for the other instance and
> the OS and performance will suffer on all fronts.
> --
> Andrew J. Kelly SQL MVP
>
> "jay d" <jayd@.discussions.microsoft.com> wrote in message
> news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
>
>|||As I stated when you set AWE it is no longer dynamic. The first instance to
come up will grab all the memory it can up to the MAX Memory setting. If
you set it to 7GB for each instance and you only have 8GB total there isn't
enough to go around. When you use AWE you can not share the memory. So if
you really do have three instances that is probably the real reason why AWE
is turned off to begin with.
Andrew J. Kelly SQL MVP
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:9144E391-55F4-4B7F-9858-321A6973AE50@.microsoft.com...[vbcol=seagreen]
> Thank you all for the help. One more quick question. If I am 3 instances
> should I set the max server memory to 7 GIG on each of them or do I divide
> the RAM among the 3 instances? ex Instance 1 - 3 GIG, Instance 2 - 3 GIG,
> and Instance 3 - 2 GIG.
> Thanks,
> Jay
> "Andrew J. Kelly" wrote:
>|||Hi,
Thanks, I will enable AWE. If I have 2 instances of SQL running, should I
set each instance to 3 GIG RAM and then leave 2 GIG for the OS, just in case
one node of the cluster fails and both instances end up on the same node for
awhile?
Thanks,
Jay
"Hari Prasad" wrote:
> Hi,
> If you have 8 GB ram please enable AWE. My value for SQL Server will be fr
om
> 6 to 6.5 GB.
> I will leave the rest to OS and other applications.
> Thanks
> Hari
> SQL Server MVP
> "jay d" <jayd@.discussions.microsoft.com> wrote in message
> news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
>
>|||Just be sure not to apply SP4 for SQL Server. There is a bug with respect
to AWE. They are working on a fix.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:8A900118-4F9B-4378-87F5-15EA79CC42F4@.microsoft.com...
Hi,
Thanks, I will enable AWE. If I have 2 instances of SQL running, should I
set each instance to 3 GIG RAM and then leave 2 GIG for the OS, just in case
one node of the cluster fails and both instances end up on the same node for
awhile?
Thanks,
Jay
"Hari Prasad" wrote:
> Hi,
> If you have 8 GB ram please enable AWE. My value for SQL Server will be
> from
> 6 to 6.5 GB.
> I will leave the rest to OS and other applications.
> Thanks
> Hari
> SQL Server MVP
> "jay d" <jayd@.discussions.microsoft.com> wrote in message
> news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
>
>
Server 2000 SP3a database cluster. It was recently rebuilt and we did not
reenable Address Windowing Extensions (AWE). Is it recommended that I turn
it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I am
asking this because it appears to be performing well with AWE off. Also
should I allocate 7 GB of RAM to for 'max server memory'? It is not set now
,
but is performing well without it.
Thanks,
JayHi,
If you have 8 GB ram please enable AWE. My value for SQL Server will be from
6 to 6.5 GB.
I will leave the rest to OS and other applications.
Thanks
Hari
SQL Server MVP
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
> Our current production environment consists of an 2 node (active-active)
> SQL
> Server 2000 SP3a database cluster. It was recently rebuilt and we did not
> reenable Address Windowing Extensions (AWE). Is it recommended that I
> turn
> it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I
> am
> asking this because it appears to be performing well with AWE off. Also
> should I allocate 7 GB of RAM to for 'max server memory'? It is not set
> now,
> but is performing well without it.
> Thanks,
> Jay|||"jay d" wrote:
> Our current production environment consists of an 2 node (active-active) S
QL
> Server 2000 SP3a database cluster. It was recently rebuilt and we did not
> reenable Address Windowing Extensions (AWE). Is it recommended that I tur
n
> it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I a
m
> asking this because it appears to be performing well with AWE off. Also
> should I allocate 7 GB of RAM to for 'max server memory'? It is not set n
ow,
> but is performing well without it.
Jay,
If the servers are running well without AWE, I would say keep it turned
off.
In my experience, the AWE implementation has some bugs. Better to keep
it simple unless you need the extra memory.
-- J|||Just because you have lots of ram does not mean sql server will be able to
use it all effectively. It depends a lot on your data and how you access it.
If your cache hit ratio and page life expectancy arealways high and your
response times are good you may not need to turn it on. But if you do you
certainly should not set it to 7gb since you have an active - active
configuration. Since AWE memory is not dynamic you can have a situation
where one instance gets 7GB and leaves only 1GB for the other instance and
the OS and performance will suffer on all fronts.
Andrew J. Kelly SQL MVP
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
> Our current production environment consists of an 2 node (active-active)
> SQL
> Server 2000 SP3a database cluster. It was recently rebuilt and we did not
> reenable Address Windowing Extensions (AWE). Is it recommended that I
> turn
> it on? Both servers have 8 procs running at 2.8 Ghz and 8 GB of RAM. I
> am
> asking this because it appears to be performing well with AWE off. Also
> should I allocate 7 GB of RAM to for 'max server memory'? It is not set
> now,
> but is performing well without it.
> Thanks,
> Jay|||Thank you all for the help. One more quick question. If I am 3 instances
should I set the max server memory to 7 GIG on each of them or do I divide
the RAM among the 3 instances? ex Instance 1 - 3 GIG, Instance 2 - 3 GIG,
and Instance 3 - 2 GIG.
Thanks,
Jay
"Andrew J. Kelly" wrote:
> Just because you have lots of ram does not mean sql server will be able to
> use it all effectively. It depends a lot on your data and how you access i
t.
> If your cache hit ratio and page life expectancy arealways high and your
> response times are good you may not need to turn it on. But if you do you
> certainly should not set it to 7gb since you have an active - active
> configuration. Since AWE memory is not dynamic you can have a situation
> where one instance gets 7GB and leaves only 1GB for the other instance and
> the OS and performance will suffer on all fronts.
> --
> Andrew J. Kelly SQL MVP
>
> "jay d" <jayd@.discussions.microsoft.com> wrote in message
> news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
>
>|||As I stated when you set AWE it is no longer dynamic. The first instance to
come up will grab all the memory it can up to the MAX Memory setting. If
you set it to 7GB for each instance and you only have 8GB total there isn't
enough to go around. When you use AWE you can not share the memory. So if
you really do have three instances that is probably the real reason why AWE
is turned off to begin with.
Andrew J. Kelly SQL MVP
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:9144E391-55F4-4B7F-9858-321A6973AE50@.microsoft.com...[vbcol=seagreen]
> Thank you all for the help. One more quick question. If I am 3 instances
> should I set the max server memory to 7 GIG on each of them or do I divide
> the RAM among the 3 instances? ex Instance 1 - 3 GIG, Instance 2 - 3 GIG,
> and Instance 3 - 2 GIG.
> Thanks,
> Jay
> "Andrew J. Kelly" wrote:
>|||Hi,
Thanks, I will enable AWE. If I have 2 instances of SQL running, should I
set each instance to 3 GIG RAM and then leave 2 GIG for the OS, just in case
one node of the cluster fails and both instances end up on the same node for
awhile?
Thanks,
Jay
"Hari Prasad" wrote:
> Hi,
> If you have 8 GB ram please enable AWE. My value for SQL Server will be fr
om
> 6 to 6.5 GB.
> I will leave the rest to OS and other applications.
> Thanks
> Hari
> SQL Server MVP
> "jay d" <jayd@.discussions.microsoft.com> wrote in message
> news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
>
>|||Just be sure not to apply SP4 for SQL Server. There is a bug with respect
to AWE. They are working on a fix.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:8A900118-4F9B-4378-87F5-15EA79CC42F4@.microsoft.com...
Hi,
Thanks, I will enable AWE. If I have 2 instances of SQL running, should I
set each instance to 3 GIG RAM and then leave 2 GIG for the OS, just in case
one node of the cluster fails and both instances end up on the same node for
awhile?
Thanks,
Jay
"Hari Prasad" wrote:
> Hi,
> If you have 8 GB ram please enable AWE. My value for SQL Server will be
> from
> 6 to 6.5 GB.
> I will leave the rest to OS and other applications.
> Thanks
> Hari
> SQL Server MVP
> "jay d" <jayd@.discussions.microsoft.com> wrote in message
> news:2B3700C8-036C-454E-A50A-D156CBA98EAC@.microsoft.com...
>
>
Subscribe to:
Posts (Atom)