Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
bryan99y
Starting Member
42 Posts |
Posted - 2002-02-11 : 16:48:43
|
| Is this correct ???Case 1 : AWE and Multi-Instances - statically use memory - SQL Server can access/use 8GB of RAM for SQL Server.Case 2 : AWE and no Multi-Instances - dynamically use memory - SQL Server can access/use 8GB of RAM for SQL Server.Case 3 : Non-AWE and Multi-Instances - dynamically uses memory - SQL Server can access/use 2GB of RAMCase 4 : Non-AWE and no Instances. - dynamically uses memory - SQL Server can access/use 2GB of RAM |
|
|
JustinBigelow
SQL Gigolo
1157 Posts |
Posted - 2002-02-11 : 17:19:38
|
I maybe dense (actually there are no maybe's about it ) but what is AWE?I can't find any mention in books on line and a google search turns up mostly non-database related acronyms.Justin |
 |
|
|
izaltsman
A custom title
1139 Posts |
Posted - 2002-02-11 : 17:48:15
|
| AWE = Address Windowing Extentions API (which allows SQL Server to use more than 2GB of RAM)If you want to find it in BOL, look under sp_configure. To answer the question though... Any time you use AWE, you should set memory to a static value. Same when you have multiple instances. Edited by - izaltsman on 02/11/2002 17:50:07 |
 |
|
|
izaltsman
A custom title
1139 Posts |
Posted - 2002-02-11 : 18:19:35
|
quote: To answer the question though... Any time you use AWE, you should set memory to a static value. Same when you have multiple instances.
Actually, no... I take that back. You don't have to specify max server memory when you are using AWE if you only have a single instance of SQL Server... Memory usage is still going to be static: AWE-enabled SQL Server will grab all the memory it can (up to 8 or 64 GB, depending on edition of the OS), but in case of a single instance that's ok, since you don't need to reserve memory space for another SQL Server. |
 |
|
|
|
|
|