Prev: FK references same column in same table
Next: Remove Primary Key
From: cw on 27 Apr 2010 10:30
I have an 8 core SQL2005 EE server on Win2003 EE with 16GB of memory. Is it
a problem if I have the SQL Server set to use 14GBs of the memory leaving
2GBs for the OS?
I can see where the SQL server is using the 14GBs and wonder if there are
times when the server begins to have memory pressure issues. Use AWE to
allocate memory is not turned on.

Thanks


From: TheSQLGuru on 27 Apr 2010 13:47
We are missing information to give you best advice:

1) 32 bit or 64 bit?
2) what else is running on the server?
3) I would think 2GB is insufficient for all non sql server buffer pool
stuff. I would start with 12GB and then monitor various memory and paging
metrics to see if you need to go lower.

--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net


"cw" <cw(a)3mc.com> wrote in message
news:%23BdErYh5KHA.5476(a)TK2MSFTNGP06.phx.gbl...
>
> I have an 8 core SQL2005 EE server on Win2003 EE with 16GB of memory. Is
> it a problem if I have the SQL Server set to use 14GBs of the memory
> leaving 2GBs for the OS?
> I can see where the SQL server is using the 14GBs and wonder if there are
> times when the server begins to have memory pressure issues. Use AWE to
> allocate memory is not turned on.
>
> Thanks
>


From: Villi Bernaroli on 29 Apr 2010 06:56
TheSQLGuru wrote:

> We are missing information to give you best advice:
>
> 1) 32 bit or 64 bit?

I think he must be on a 64bit PC, otherwise he would never see that much RAM

> 2) what else is running on the server?
> 3) I would think 2GB is insufficient for all non sql server buffer
> pool stuff. I would start with 12GB and then monitor various memory
> and paging metrics to see if you need to go lower.

My same opinion: trial and error.
--
Villi Bernaroli, Italy
VFP, SOAP, MS SQLserver, MySQL, Oracle



From: TheSQLGuru on 30 Apr 2010 16:21
> I think he must be on a 64bit PC, otherwise he would never see that much
> RAM

that is not correct. 32 bit with /PAE and AWE enabled can use way more than
16GB

--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net


"Villi Bernaroli" <a(a)b.invalid> wrote in message
news:%233$gkq45KHA.420(a)TK2MSFTNGP02.phx.gbl...
> TheSQLGuru wrote:
>
>> We are missing information to give you best advice:
>>
>> 1) 32 bit or 64 bit?
>
> I think he must be on a 64bit PC, otherwise he would never see that much
> RAM
>
>> 2) what else is running on the server?
>> 3) I would think 2GB is insufficient for all non sql server buffer
>> pool stuff. I would start with 12GB and then monitor various memory
>> and paging metrics to see if you need to go lower.
>
> My same opinion: trial and error.
> --
> Villi Bernaroli, Italy
> VFP, SOAP, MS SQLserver, MySQL, Oracle
>
>


 | 
Pages: 1
Prev: FK references same column in same table
Next: Remove Primary Key