access up to 2GB of RAM from a single process. Windows 2000/2003 can be
configured to allow for a single process to access 3GB of RAM. If you
have Windows 2000/2003 advanced or data center than a single process
can access more than 3GB of RAM using non-standard system calls i.e. it
has to be written specifically to do that. There is an overhead
associated with all this that makes the effective amount of RAM
available lower than the physical RAM. 64bit systems don't have this
problem. I strongly recommend that you use an Opteron-based system for
SQL Server if you want to use more than 4GB of RAM.
-Matt
On May 11, 2004, at 11:29 AM, Tom Kitta wrote:
> [Tom Kitta]
>
> I agree with the memory leaks but not with the size of RAM
> limitation. There
> is no problem with going past 4Gb on Windows server. For example you
> can
> have SQL server use 8Gb. For how to do this see
> http://www.sql-server-performance.com/
> As far as I know same holds true for other server class OS. On
> non-server OS
> 4Gb is a limit, like on Windows XP Pro.
>
> The OS must do a re-mapping trick to use memory past 4Gb on 32bit
> systems
> and I think this is what Matt was referring to.
>
> TK
> http://www.tomkitta.com
>
> Increasing the amount of RAM never fixes memory leaks. Further, unless
> you are using a 64bit CPU and OS, then you can't make use of more than
> 4GB of RAM anyway. In fact, most 32bit operating systems won't allow
> you to even use all 4GB.
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
