Re: Physical/Vertial node cluster memory setup?

Jerry,

I fully agree with Geoff, however as you are commited to see this thru...
you really need to get VMWare onboard to advice you on this. In the end they
are the vendor supporting you. ( as I do not believe that a physical/virtual
SQL cluster is anywhere supported by Microsoft)

VMWare supports physical/virtual clustering, therefore that is your source
of info

rgds,
Edwin.


"Jerry Cutshaw" <JerryCutshaw@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:79875B1B-A573-4633-9023-599ABEB44596@xxxxxxxxxxxxxxxx
Geoff,
Thanks for the reply even if its not what I wanted to hear :). I was
assured by my vendor and consultants that this is a viable solution
however
and I am commited (or doomed you might think) to see it through to the
end.
Could you offer me any suggestions on memory configuration knowing I have
a
physical/virtual setup? btw I'm not going to be over-subscribing ESX if
that
matters to anyone. It has plenty of memory its just that ESX can't
address
all the physical memory in one VM until the next rev.

Jerry

"Geoff N. Hiten" wrote:

You are running SQL Clustering on VMWare?

I am struggling to find a polite way to question your sanity. Give it a
few
months of trying to support this and you will likely be doing the same.

Seriously, this is not a stable configuration, nor is it one you want to
support if you like sleeping nights or being NOT in the office on
weekends.
Get the MSCS cluster back to bare metal and start over.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP





"Jerry Cutshaw" <JerryCutshaw@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:9EBC83C4-292F-4507-8163-22BCA2B2A55F@xxxxxxxxxxxxxxxx
Hello,
I have a Physical/Virtual node MSCS failover cluster. I am running
64bit
SQL 2005 and Windows 2003. I have read enough posts that indicate you
in
64
bit SQL Server you should set the max memory. Unfortunately my
physical
box
has 32 GB of memory (I could utilize all of it!) and my virtual server
node
(VMWare ESX) can only support 16 GB. My question is:

1. Is it possible to configure the two different nodes to use a
different
max server memory?
2. If #1 isn't possible what happens if I configure max server memory
to
say 24 GB and the server fails over to the virtual node? Will SQL
Server
perform a soft crash dump everytime it gets loaded up?
3. I have found references to the "lock pages in memory" on the
forums
does
this come into play as a possible solution to my problem?

Thank you in advance for your replies.

Jerry L. Cutshaw




.

Relevant Pages

  • Re: Memory settings for Virtual SQL Server
    ... "Geoff N. Hiten" wrote: ... You will need to have flexible memory incase the two instances land ... > A properly tuned SQL server should not page. ... Would you put the SQL bits in the OS RAID group or the pagefile RAID ...
    (microsoft.public.sqlserver.clustering)
  • Re: Memory settings for Virtual SQL Server
    ... Hi again Geoff. ... I am not putting on two instances of SQL Server. ... You will need to have flexible memory incase the two instances land ... Would you put the SQL bits in the OS RAID group or the pagefile RAID ...
    (microsoft.public.sqlserver.clustering)
  • Re: should I Enable AWE in a SQL Cluster enviroment ?
    ... Hello Geoff, so How can I set the maximum server memory on each instance?. ... > I support the Professional Association for SQL Server ...
    (microsoft.public.sqlserver.setup)
  • Re: AWE Memory Question
    ... and leave at least 1GB for any other activity other than SQL Server. ... "Geoff N. Hiten" wrote in message ... The portion allocated to SQL under AWE is not all that SQL ... >>> I agree with Geoff but your numbers don't add up for memory usage. ...
    (microsoft.public.sqlserver.setup)
  • Re: Connecting to an instance in a cluster
    ... "Geoff N. Hiten" wrote: ... you cannot reuse port numbers. ... Microsoft SQL Server MVP ... That is the port you have to open on the firewall. ...
    (microsoft.public.sqlserver.clustering)