Passwords for cluster and servers

I have a 2 node cluster running Win2000 enterprise and MS clustering.
Also SQL server. Would there be a problem using the same domain
password for SQL and for the clustering service? I thought I read
that there may be a problem but I don't recall where it read it.
Thanks for any help.
I'm using one domain account for SQL and Cluster services and I have no
problems.
Ayad Shammout
SR.DBA/Analyst
Caregroup IS
"Dave" <mine@.none.com> wrote in message
news:foam11pg95kfd57jefn88eou8o160kc3r1@.4ax.com...
> I have a 2 node cluster running Win2000 enterprise and MS clustering.
> Also SQL server. Would there be a problem using the same domain
> password for SQL and for the clustering service? I thought I read
> that there may be a problem but I don't recall where it read it.
> Thanks for any help.
>
|||im using 1 account for cluster and sql services, havent had any issues to
date...
"Dave" <mine@.none.com> wrote in message
news:foam11pg95kfd57jefn88eou8o160kc3r1@.4ax.com...
> I have a 2 node cluster running Win2000 enterprise and MS clustering.
> Also SQL server. Would there be a problem using the same domain
> password for SQL and for the clustering service? I thought I read
> that there may be a problem but I don't recall where it read it.
> Thanks for any help.
>
|||I don't think there's a functional issue, but if you use the same account,
the domain admins will be able to log on to SQL Server as an SA. If you use
separate accounts, you can set the cluster account to have minimal SQL
privledges so the keep alive for SQL will work and not give the domain
admins sa access to the database. In a small environment using the same
account is probably no big deal, but in a larger enterprise it could be.
"Dave" <mine@.none.com> wrote in message
news:foam11pg95kfd57jefn88eou8o160kc3r1@.4ax.com...
> I have a 2 node cluster running Win2000 enterprise and MS clustering.
> Also SQL server. Would there be a problem using the same domain
> password for SQL and for the clustering service? I thought I read
> that there may be a problem but I don't recall where it read it.
> Thanks for any help.
>
|||If you do not want the domain admins to be admins of sql then remove
buildin/admin group, create your own group "Sql Admins" add users who need
admin to sql and add that.
apart for that , using same cluster and sql login is not a prob
"Al" <al@.nospam.com> wrote in message
news:OBnYmUVGFHA.1836@.tk2msftngp13.phx.gbl...
> I don't think there's a functional issue, but if you use the same account,
> the domain admins will be able to log on to SQL Server as an SA. If you
use
> separate accounts, you can set the cluster account to have minimal SQL
> privledges so the keep alive for SQL will work and not give the domain
> admins sa access to the database. In a small environment using the same
> account is probably no big deal, but in a larger enterprise it could be.
> "Dave" <mine@.none.com> wrote in message
> news:foam11pg95kfd57jefn88eou8o160kc3r1@.4ax.com...
>

Passive node starting the SQL Server services - services set to ma

Hello all,
I have a very bizarre situation with a single instance/two node/W2K3
cluster. The issue I am seeing is that the passive node is starting the sql
server services even though the resources are not owned by that node. The
restarts are occuring every five minutes. The system log shows the SYSTEM
account starting MSSQLSERVER. Then, 3 seconds later, I get a message stating
the service stopped. About 5-8 seconds later, I get a message that the
SQLSERVERAGENT could not be started because sqlservr.exe is not running. The
cluster log is not showing anything being started/stopped. The applicaiton
log is complaining about the errorlog being unavailable. However, this is
correct because the resources are not on this node.
The SQL Server services are set to manual on both nodes. Both nodes have
been rebooted in the past 24 hours due to EMC PowerPath upgrades. The only
thing that is a little bizare is that the SQL Server resource group and SQL
Server resource have the preferred owners/possible owners in reverse order.
IE (SQL Server resource group has NODE1/NODE2; SQL Server Resource has
NODE2/NODE1). Right now all resources are on NODE1.
Any ideas would be greatly appreciated.
Thanks in advance
Chris.
Manual start for services is correct for a cluster. The cluster should
control the services on each node. Look at the applicaiotn logs on both
nodes. Check the failover/failback settings. You may be seeing a failback
condition due to different preferred node settings.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Christopher" <Christopher@.discussions.microsoft.com> wrote in message
news:E5873D57-2A8F-4B7B-B76C-7146B8A629DD@.microsoft.com...
> Hello all,
> I have a very bizarre situation with a single instance/two node/W2K3
> cluster. The issue I am seeing is that the passive node is starting the
> sql
> server services even though the resources are not owned by that node. The
> restarts are occuring every five minutes. The system log shows the SYSTEM
> account starting MSSQLSERVER. Then, 3 seconds later, I get a message
> stating
> the service stopped. About 5-8 seconds later, I get a message that the
> SQLSERVERAGENT could not be started because sqlservr.exe is not running.
> The
> cluster log is not showing anything being started/stopped. The
> applicaiton
> log is complaining about the errorlog being unavailable. However, this is
> correct because the resources are not on this node.
> The SQL Server services are set to manual on both nodes. Both nodes have
> been rebooted in the past 24 hours due to EMC PowerPath upgrades. The
> only
> thing that is a little bizare is that the SQL Server resource group and
> SQL
> Server resource have the preferred owners/possible owners in reverse
> order.
> IE (SQL Server resource group has NODE1/NODE2; SQL Server Resource has
> NODE2/NODE1). Right now all resources are on NODE1.
> Any ideas would be greatly appreciated.
> Thanks in advance
> Chris.