Just wondering if this is correct. I have SQL 2000 set up across a Server
2003 cluster. Say I have PhysicalNode1 and PhysicalNode2 and VirtualServer1.


VirtualServer1 is sitting on top of PhysicalNode1 and I go into Enterprise
manager and make some configuration settings to SQL server like Default
Data/Log directories, boosting SQL server process priority, etc. Within a
few minutes the changes I make are wiped out and it's set back to the
default. Also, if I switch to PhysicalNode2, VirtualServer1 does not
maintain the settings I've added.

I've spoken with a MS tech and he claimed that was "By design". Is this
true or was he wrong and I have my cluster configured improperly.

I know I can go into the registries and hack the changes I want onto each
physical node, but that definitely is not something I'd prefer to do. Anyone
have a workaround or any thoughts on this?

Thanks,

Chris

Are you connected to the virtual server or local instance?


joe.

"Chris" <Chris (AT) discussions (DOT) microsoft.com> wrote

Hmm, I wasn't really logged directly onto either the virtual server or the
underlying node. I was using Enterprise manager to connect to the virtual
server.

Should I be only running Ent Manager while term serv'd into the virtual
server or the underlying node?

"Joe Yong" wrote:

Chris wrote:
I have had this to. I dont think the changes are whiped out, they
probably never get set. The work around I used was to log on to the node
were the virtual sevrver was active, and use the enterprise manager to
set the data and log dirs.

--
Hans