Estimating cluster memory requirement

Hi,
I am aggregating 6-8 SQL Server 2000 databases to a cluster of SQL
Server consisting of two nodes, each with four 3.1GHz Xeon CPUs. How do
I estimate the memory requirement for each node? Do I simply add the
memory utilization of each SQL Server instance on each individual SQL
server? Or, is there some other formula to arrive at this figure?
Thanks,
- Siddhartha
It actually works the other way around. Put as much memory as you can in
each node. SQL will generally run better the more memory you give it. Then
divide the memory amongst the instances. Remember, during a failover, all
your instances will "stack" onto one server so you must plan for that
situation. Also you will need to leave 1-2GB for the OS and support
applications. Use the Performance Monitor tool to watchoverall memory use.
I like to use Page Life Expectancy as a measurement for memory pressure
within SQL Server.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Siddhartha Jain" <sid@.netmagicsolutions.com> wrote in message
news:ufRmfc17FHA.2616@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I am aggregating 6-8 SQL Server 2000 databases to a cluster of SQL
> Server consisting of two nodes, each with four 3.1GHz Xeon CPUs. How do
> I estimate the memory requirement for each node? Do I simply add the
> memory utilization of each SQL Server instance on each individual SQL
> server? Or, is there some other formula to arrive at this figure?
> Thanks,
> - Siddhartha
|||Thanks for the reply Geoff. I don't intend to run multiple instances per
node but only one instance per node. So lets say I have six servers now,
each using 2GB currently for the SQL server instance, then do I size 6GB
for the SQL instance per cluster node (in a cluster of two nodes).
- Siddhartha
Geoff N. Hiten wrote:
> It actually works the other way around. Put as much memory as you can in
> each node. SQL will generally run better the more memory you give it. Then
> divide the memory amongst the instances. Remember, during a failover, all
> your instances will "stack" onto one server so you must plan for that
> situation. Also you will need to leave 1-2GB for the OS and support
> applications. Use the Performance Monitor tool to watchoverall memory use.
> I like to use Page Life Expectancy as a measurement for memory pressure
> within SQL Server.
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
> "Siddhartha Jain" <sid@.netmagicsolutions.com> wrote in message
> news:ufRmfc17FHA.2616@.TK2MSFTNGP15.phx.gbl...
>
>
|||During a cluster node failure event, the instances will all migrate to a
single node. That is how it wirks. You will need to divide the memory so
that both instances can live on a single node. As for total memory
required, there is no exact rule. SQL likes more memory so adding memory
won't hurt. Watch the performance counters to check memory pressure.
GNH
"Siddhartha Jain" <sid@.netmagicsolutions.com> wrote in message
news:%23l$s1u27FHA.744@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Thanks for the reply Geoff. I don't intend to run multiple instances per
> node but only one instance per node. So lets say I have six servers now,
> each using 2GB currently for the SQL server instance, then do I size 6GB
> for the SQL instance per cluster node (in a cluster of two nodes).
> - Siddhartha
>
> Geoff N. Hiten wrote:
sql