Few Questions
-
Hi,
I have few questions.
1. I have a sqlserver(2000) box( win 2k3) with 8GB of RAM. I abe configured it to use 6GB of RAM through dynamic memory management.I have also enabled the AWE option. My question is do i stil have to include /pae switch in the boot.ini file.
2. How do i know when was the last time my index was rebuilt/updated.( may be recreate or may be using dbccreindex).i tried DBCC show update statiscs, it does show something called last updated. What i know this shows, when the statistics were last updated( mine is auto update).So if i run dbcc reindex will the last updated value change?
-
here's a good article :
http://www.sql-server-performance.com/awe_memory.asp
Johan
Learn to play, play to learn !Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:- How to post Performance Problems
- How to post data/code to get the best help[/url]- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
-
Thanks for the reply.
I have gone thorug the website before but ia m still confused.
3GB /PAE switch comes into picture when i have 4 GB of RAM(certain versions) , and it gives me that extra 1 GB. BUt when i have 8GB , it is AWE Enabled , then what extra benefit do i get by adding this switch? Does AWE depends on PAE switch to fucntion normally. AWE infact takes all the memory space (except 128 MB for OS to work).SO why do i add 3GB /PAE switch to tell OS to give me 1 extra GB more when AWE( it takes the entire memory and not just only 1 GB more 
does that for me. -
from BOL :
Usage Considerations
Before enabling AWE, consider the following:
- When awe enabled is set to 1, instances of SQL Server 2000 do not dynamically manage the size of the address space. SQL Server will reserve and lock almost all available memory (or the value of max server memory if the option has been set) when the server is started. It is strongly recommended that you set a value for the max server memory option each time you enable AWE. Otherwise other applications or instances of SQL Server 2000 will have less than 128 MB of physical memory in which to run.
- If the total available memory is less than 3 GB, the instance of SQL Server 2000 will be started in non-AWE mode even if awe enabled is set to 1. In this situation, you do not need to manage AWE memory because dynamic memory allocation is used automatically.
- You can determine the amount of memory you can safely allocate to instances of SQL Server 2000 by identifying how much memory is available after all other applications to be used on the computer have been started.
Use the SQL Server Performance Monitor Total Server Memory (KB) counter to determine how much memory is allocated by the instance of SQL Server running in AWE mode. Configure the max server memory option to leave some additional memory free to allow for the varying needs of other applications and Windows 2000. For more information, see Monitoring Memory Usage.
Important Using the awe enabled option and the max server memory setting can have a performance impact on other applications or on SQL Server running in a multi-instance or cluster environment. For more information about using AWE memory, see Managing AWE Memory.
In the cases where I have used AWE (w2k/sql2k), I always did set the max server memory to the value I wanted the instance to use. It was on a db-cluster with 4 instances (2 - 2) with 8Gb ram and I wanted to be sure that in case of failover my most-critical instance always had enough ram to get started.
Now I have 3 instances running without AWE and 1 with AWE running just fine.
Johan
Learn to play, play to learn !Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:- How to post Performance Problems
- How to post data/code to get the best help[/url]- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
-
How does Windows 2003/64 bit fit into the picture? We're running on opteron (not itanium) boxes with 32GB ram, but the most I'm able to allocate to sql/server is 4GB.
I did try to put on SQL/Server(23 bit) SP4 and the hotfixes, but performance in this configuration was worse [there's another thread discussing this] so we reverted to SP3.
Does anyone have any experience of a similar configuration?
We had a couple of ideas for workarounds:
buy ramdisk software and use the 28GB unused memory as a fast disk.
Add additional SQL/Server instances - they will get 4GB each, right?
Any comments?
Best Regards,Otto Schreibke
The future is a foreign country, they do things differently there.
(Stolen from Arthur C Clarke) -
Otto, I think 32bit SQL Server database engine is limited to 4GB of ram unless you're running Windows 2003 Enterprise or Datacenter. If you run 64 bit SQL Server you wouldn't be bound by that limitation.
If you don't want to run 64 bit SQL, then I gues the multiple instance idea would be the best use of memory. You'd need to be careful about the underlying disk I/O subsystem though.
--------------------
Colt 45 - the original point and click interface
-
64 bit
No experience
Johan
Learn to play, play to learn !Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:- How to post Performance Problems
- How to post data/code to get the best help[/url]- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
-
Phill,
Thanks for the reply.
We can't use SQL/Server/64bit as we're running on opterons (x86 architecture) and not itaniums. We are using Windows 2003 Enterprise 64 Bit.
The little documentation I found trawling the web indicated we needed SQL/Server SP4 and a couple of hotfixes. Performance seemed to suffer in this configuration though, so we reverted to SP3.
I wasn't able to find any documentation on how to set up windows 2003 64bit and SQL/Server to work together. Any good ideas?
"You'd need to be careful about the underlying disk I/O subsystem though." - agree. Any thoughts on the ramdisk idea? We're loading the database, and will be backing it up to pass to another team when we're done, so recoverability is not an issue.
Regards
Otto
Best Regards,Otto Schreibke
The future is a foreign country, they do things differently there.
(Stolen from Arthur C Clarke) -
Hellow dear Collegues, I would like also to add a simple question,
can I use AWE in SQL 2000 Standard ??????
-
Books online "Maximum Capacity Specifications"
---> Standard Edition max 2Gb
Johan
Learn to play, play to learn !Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:- How to post Performance Problems
- How to post data/code to get the best help[/url]- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply