Showing posts with label sql2005. Show all posts
Showing posts with label sql2005. 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

Monday, March 19, 2012

Cluster - 2000/2005 side-by-side install

I have a two node active/passive win2003/sql 2000 cluster. Can I do a side-by-side install of a sql2005 named instance on this cluster? This is for a test environment were for a limited time (6 months) I need to provide both a sql2000 and sql2005 environment and I would rather not purchase additional hardware.
This is a perfectly valid multi-instance cluster configuration. The new SQL 2005 installation will need its own IP address, disk resource(s), and network name. This will create a second virtual server for the SQL 2005 instance. Once you uninstall the SQL 2000 instance, you can re-assigne the disk resources to the new SQL 2005 instance. You cannot install the SQL 2005 instance in the existing SQL 2000 virtual server.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"AlanH" <AlanH@.community.nospam> wrote in message news:eQXXv6e%23FHA.2472@.TK2MSFTNGP12.phx.gbl...
I have a two node active/passive win2003/sql 2000 cluster. Can I do a side-by-side install of a sql2005 named instance on this cluster? This is for a test environment were for a limited time (6 months) I need to provide both a sql2000 and sql2005 environment and I would rather not purchase additional hardware.
|||In your last line when you say that "You cannot install the SQL2005 instance in the existing SQL2000 virtual server" do you mean the existing cluster group where sql2000 resides?
Also, if the answer to that is yes (meaning I cannot just install sql2005 in my current group), what are my options for sharing the current disk resources or reconfiguring the current disk resources so that I can give the new cluster_group for sql2005 some disk resources.
Thanks in advance...
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message news:Of0GDfg%23FHA.208@.tk2msftngp13.phx.gbl...
This is a perfectly valid multi-instance cluster configuration. The new SQL 2005 installation will need its own IP address, disk resource(s), and network name. This will create a second virtual server for the SQL 2005 instance. Once you uninstall the SQL 2000 instance, you can re-assigne the disk resources to the new SQL 2005 instance. You cannot install the SQL 2005 instance in the existing SQL 2000 virtual server.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"AlanH" <AlanH@.community.nospam> wrote in message news:eQXXv6e%23FHA.2472@.TK2MSFTNGP12.phx.gbl...
I have a two node active/passive win2003/sql 2000 cluster. Can I do a side-by-side install of a sql2005 named instance on this cluster? This is for a test environment were for a limited time (6 months) I need to provide both a sql2000 and sql2005 environment and I would rather not purchase additional hardware.
|||The statement is correct. One group = one virtual server = one instance.
You will either need to add more shared disk(s) to your cluster or remove SQL from some existing disk resources. Disk resources cannot be shared in multiple groups. As such, they can only be used by one virtual server/instance at a time.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"AlanH" <AlanH@.community.nospam> wrote in message news:eq7YDyq%23FHA.3804@.TK2MSFTNGP14.phx.gbl...
In your last line when you say that "You cannot install the SQL2005 instance in the existing SQL2000 virtual server" do you mean the existing cluster group where sql2000 resides?
Also, if the answer to that is yes (meaning I cannot just install sql2005 in my current group), what are my options for sharing the current disk resources or reconfiguring the current disk resources so that I can give the new cluster_group for sql2005 some disk resources.
Thanks in advance...
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message news:Of0GDfg%23FHA.208@.tk2msftngp13.phx.gbl...
This is a perfectly valid multi-instance cluster configuration. The new SQL 2005 installation will need its own IP address, disk resource(s), and network name. This will create a second virtual server for the SQL 2005 instance. Once you uninstall the SQL 2000 instance, you can re-assigne the disk resources to the new SQL 2005 instance. You cannot install the SQL 2005 instance in the existing SQL 2000 virtual server.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"AlanH" <AlanH@.community.nospam> wrote in message news:eQXXv6e%23FHA.2472@.TK2MSFTNGP12.phx.gbl...
I have a two node active/passive win2003/sql 2000 cluster. Can I do a side-by-side install of a sql2005 named instance on this cluster? This is for a test environment were for a limited time (6 months) I need to provide both a sql2000 and sql2005 environment and I would rather not purchase additional hardware.
|||That's what I thought... Thanks!
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message news:uqMvcYt%23FHA.1336@.TK2MSFTNGP10.phx.gbl...
The statement is correct. One group = one virtual server = one instance.
You will either need to add more shared disk(s) to your cluster or remove SQL from some existing disk resources. Disk resources cannot be shared in multiple groups. As such, they can only be used by one virtual server/instance at a time.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"AlanH" <AlanH@.community.nospam> wrote in message news:eq7YDyq%23FHA.3804@.TK2MSFTNGP14.phx.gbl...
In your last line when you say that "You cannot install the SQL2005 instance in the existing SQL2000 virtual server" do you mean the existing cluster group where sql2000 resides?
Also, if the answer to that is yes (meaning I cannot just install sql2005 in my current group), what are my options for sharing the current disk resources or reconfiguring the current disk resources so that I can give the new cluster_group for sql2005 some disk resources.
Thanks in advance...
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message news:Of0GDfg%23FHA.208@.tk2msftngp13.phx.gbl...
This is a perfectly valid multi-instance cluster configuration. The new SQL 2005 installation will need its own IP address, disk resource(s), and network name. This will create a second virtual server for the SQL 2005 instance. Once you uninstall the SQL 2000 instance, you can re-assigne the disk resources to the new SQL 2005 instance. You cannot install the SQL 2005 instance in the existing SQL 2000 virtual server.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"AlanH" <AlanH@.community.nospam> wrote in message news:eQXXv6e%23FHA.2472@.TK2MSFTNGP12.phx.gbl...
I have a two node active/passive win2003/sql 2000 cluster. Can I do a side-by-side install of a sql2005 named instance on this cluster? This is for a test environment were for a limited time (6 months) I need to provide both a sql2000 and sql2005 environment and I would rather not purchase additional hardware.