Showing posts with label purpose. Show all posts
Showing posts with label purpose. Show all posts

Sunday, March 25, 2012

Cluster installation & Domain Group requirements...

Why does a cluster install of SQL2005 require access to a domain group and what is the purpose of having to create a domain group for the cluster installation? Other than the blurb mentioned in BOL I'm having a hard time finding any information out about this requirement.

From BOL: How to create a failover cluster.

Section 18: On the Domain Groups for Clustered Services page, provide a DomainName\GroupName for each clustered service being installed: the SQL Server service, SQL Server Agent service, Analysis Services service, and Full-Text Search service must run as domain accounts that are members of the built-in administrators group on each node of the cluster. To proceed, click Next. For more information, see Domain Groups for Clustered Services.

The purpose for domain groups in cluster installation is security consideration. As SQL Server service accounts in a local group can be changed or removed after SQL Server 2005 is installed. Then the security setting like ACL will be lost. That is why domain group\account is introduced.

|||

Ok, that's kind of what I thought it was for.

Is there any way to change the group after installation? Can I just move the account to another group and be done with it? Or is there somewhere (in SQL Server) that I need to update the group if we desire to change groups?

sqlsql

Thursday, March 22, 2012

Cluster Failover - Setting Affinity

Hi Folks:
How do you script-o-matically set processor affinity on SQL after a
cluster failure?
The purpose is that I'll be failing to a machine with a different
amount of CPU's (4 instead of 8). I want to control what SQL
instances take what amounts of processor.
Is this even possible?
Thanks!
Not that this will help any, but Datacenter allows for this from the Process
Control program
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"The Researcher" <the_re_searcher@.hotmail.com> wrote in message
news:59fe996a.0408300823.1bfbe5d2@.posting.google.c om...
> Hi Folks:
> How do you script-o-matically set processor affinity on SQL after a
> cluster failure?
> The purpose is that I'll be failing to a machine with a different
> amount of CPU's (4 instead of 8). I want to control what SQL
> instances take what amounts of processor.
> Is this even possible?
> Thanks!
|||... then I wonder if you can do it in WSRM in Win2k3 that allows you to set
percentages etc on processors - it seems to be derived from the Process
Control Tool in Datacenter ?
Andy.
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:eHgTAWrjEHA.1656@.TK2MSFTNGP09.phx.gbl...
> Not that this will help any, but Datacenter allows for this from the
Process
> Control program
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> "The Researcher" <the_re_searcher@.hotmail.com> wrote in message
> news:59fe996a.0408300823.1bfbe5d2@.posting.google.c om...
>
|||Excellent idea Andy! WSRM is not do processors affinity though. It does do
these things:
Set CPU and memory allocation policies on applications. This includes
selecting processes to be managed, and setting resource usage targets or
limits.
Manage CPU utilization (percent CPU in use).
Limit the process working set size (physical resident pages in use).
Manage committed memory (pagefile usage).
Apply policies to users or groups on a Terminal Services application
server.
Apply policies on a date/time schedule.
Generate, store, view, and export resource utilization accounting
records for management, service level agreement (SLA) tracking, and
charge-back purposes.
see
http://www.microsoft.com/windowsserv...fastfacts.mspx
for more on WSRM.
Its a great package and free for EE and DC editions.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"Andy Ball" <andy.ball@.remove4spam_greenfell.com> wrote in message
news:O%23xgKBFkEHA.324@.TK2MSFTNGP11.phx.gbl...
> ... then I wonder if you can do it in WSRM in Win2k3 that allows you to
> set
> percentages etc on processors - it seems to be derived from the Process
> Control Tool in Datacenter ?
> Andy.
> "Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
> message news:eHgTAWrjEHA.1656@.TK2MSFTNGP09.phx.gbl...
> Process
>
|||Dang English language and spell chuckers! WSRM is not do processors affinity
though - Should be WSRM does not do processors affinity.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:uunBBKJkEHA.3712@.TK2MSFTNGP15.phx.gbl...
> Excellent idea Andy! WSRM is not do processors affinity though. It does do
> these things:
> Set CPU and memory allocation policies on applications. This includes
> selecting processes to be managed, and setting resource usage targets or
> limits.
> Manage CPU utilization (percent CPU in use).
> Limit the process working set size (physical resident pages in
> use).
> Manage committed memory (pagefile usage).
> Apply policies to users or groups on a Terminal Services
> application server.
> Apply policies on a date/time schedule.
> Generate, store, view, and export resource utilization accounting
> records for management, service level agreement (SLA) tracking, and
> charge-back purposes.
>
> see
> http://www.microsoft.com/windowsserv...fastfacts.mspx
> for more on WSRM.
> Its a great package and free for EE and DC editions.
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> "Andy Ball" <andy.ball@.remove4spam_greenfell.com> wrote in message
> news:O%23xgKBFkEHA.324@.TK2MSFTNGP11.phx.gbl...
>
|||"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in message news:<eHgTAWrjEHA.1656@.TK2MSFTNGP09.phx.gbl>...
> Not that this will help any, but Datacenter allows for this from the Process
> Control program
ehr, I just checked with the WSRM site and found the following snippet:
It is not recommended that you use WSRM CPU affinity for SQL Server 2000.
That being said, it doesn't appear as though that's going to work.
Any other suggestions?
Thx
sqlsql