Add SAN Disk Resource to Active/Active SQL cluster

Looking to see if I am missing any steps below to adding a SAN disk
resource to an Active/Active SQL cluster:
-Create Volumes
-Present LUNs to both Nodes
-Failover Cluster Groups to Node2
-On Node1
Disable ClusDisk
Disable Cluster Services
Reboot Node1
Rescan for hardware changes
Write the disk signature
Set disk to basic
Create Partition
Assign Drive Letter
Enable ClusDisk
Enable Cluster Services
Reboot Node1
-On Node2
Failover Cluster Groups to Node1
Disable ClusDisk
Disable Cluster Services
Reboot Node2
Rescan for hardware changes
Assign Drive Letter
Enable ClusDisk
Enable Cluster Services
Reboot Node2
-Assign disk resource to Cluster Groups
-On Node1
Take SQL Server Resource offline
Add SQL Server Resource dependency to disk resource
Bring SQL Server Resource online
-On Node2
Repeat above
-Test failover
Thanks,
Ian in SD
With Windows 2003 as the host, you may be able to skip some of the reboots.
You can rescan the disk list and pick up newly added disks. I have never
had to disable or stop the cluster service to pick up new disks. I do make
sure and do all the work on a node that does not currently host any cluster
resources. Once I am done, I can rescan the disk list on the other node(s)
and failover at will. If you have the downtime, the reboots won't hurt, but
they may not be necessary.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<theredmiata@.hotmail.com> wrote in message
news:1142967852.423752.294080@.i39g2000cwa.googlegr oups.com...
> Looking to see if I am missing any steps below to adding a SAN disk
> resource to an Active/Active SQL cluster:
>
> -Create Volumes
> -Present LUNs to both Nodes
> -Failover Cluster Groups to Node2
> -On Node1
> Disable ClusDisk
> Disable Cluster Services
> Reboot Node1
> Rescan for hardware changes
> Write the disk signature
> Set disk to basic
> Create Partition
> Assign Drive Letter
> Enable ClusDisk
> Enable Cluster Services
> Reboot Node1
> -On Node2
> Failover Cluster Groups to Node1
> Disable ClusDisk
> Disable Cluster Services
> Reboot Node2
> Rescan for hardware changes
> Assign Drive Letter
> Enable ClusDisk
> Enable Cluster Services
> Reboot Node2
> -Assign disk resource to Cluster Groups
> -On Node1
> Take SQL Server Resource offline
> Add SQL Server Resource dependency to disk resource
> Bring SQL Server Resource online
> -On Node2
> Repeat above
> -Test failover
> Thanks,
> Ian in SD
>
|||Thanks for the reply Geoff. This the first time for this process as we
are trying to split the file groups and would like to have each group
on a seperate volume.

add new user with all rights to all dbases

Kind of new to Enterprize Manager, just wondering what the steps are to add
a
new user that will have all rights to all databases? Thanks.
--
Paul G
Software engineer."Paul" <Paul@.discussions.microsoft.com> wrote in message
news:FF651560-0FE5-4B24-B9C2-C66E227CD0FB@.microsoft.com...
> Kind of new to Enterprize Manager, just wondering what the steps are to
> add a
> new user that will have all rights to all databases? Thanks.
> --
> Paul G
> Software engineer.
Add your new user normally. Either as a Windows Authenticated account or as
a SQL User account.
Add that new user to the sysadmins SQL Server group inside SQL Server.
Just a side note on security here. I hope that this is the user account
that you will be connecting with moving forward and not something you are
planning on giving to everyone who uses the database. ;-)
Rick Sawtell
MCT, MCSD, MCDBA|||Thanks for the response. Actually I was trying to set up an account for a
database administrator that could administer all dbases. This would only be
used by one individual.
"Rick Sawtell" wrote:

> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:FF651560-0FE5-4B24-B9C2-C66E227CD0FB@.microsoft.com...
> Add your new user normally. Either as a Windows Authenticated account or
as
> a SQL User account.
> Add that new user to the sysadmins SQL Server group inside SQL Server.
>
> Just a side note on security here. I hope that this is the user account
> that you will be connecting with moving forward and not something you are
> planning on giving to everyone who uses the database. ;-)
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||If it is OK to have sysadmins privileges for the person, just add a login fo
r the person, and make
it sysadmin.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:6401A53E-E9C0-41F9-9E08-C58B82148BD0@.microsoft.com...[vbcol=seagreen]
> Thanks for the response. Actually I was trying to set up an account for a
> database administrator that could administer all dbases. This would only
be
> used by one individual.
> "Rick Sawtell" wrote:
>|||ok thanks for the additional information.
"Tibor Karaszi" wrote:

> If it is OK to have sysadmins privileges for the person, just add a login
for the person, and make
> it sysadmin.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:6401A53E-E9C0-41F9-9E08-C58B82148BD0@.microsoft.com...
>
>

add new user with all rights to all dbases

Kind of new to Enterprize Manager, just wondering what the steps are to add a
new user that will have all rights to all databases? Thanks.
Paul G
Software engineer.
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:FF651560-0FE5-4B24-B9C2-C66E227CD0FB@.microsoft.com...
> Kind of new to Enterprize Manager, just wondering what the steps are to
> add a
> new user that will have all rights to all databases? Thanks.
> --
> Paul G
> Software engineer.
Add your new user normally. Either as a Windows Authenticated account or as
a SQL User account.
Add that new user to the sysadmins SQL Server group inside SQL Server.
Just a side note on security here. I hope that this is the user account
that you will be connecting with moving forward and not something you are
planning on giving to everyone who uses the database. ;-)
Rick Sawtell
MCT, MCSD, MCDBA
|||Thanks for the response. Actually I was trying to set up an account for a
database administrator that could administer all dbases. This would only be
used by one individual.
"Rick Sawtell" wrote:

> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:FF651560-0FE5-4B24-B9C2-C66E227CD0FB@.microsoft.com...
> Add your new user normally. Either as a Windows Authenticated account or as
> a SQL User account.
> Add that new user to the sysadmins SQL Server group inside SQL Server.
>
> Just a side note on security here. I hope that this is the user account
> that you will be connecting with moving forward and not something you are
> planning on giving to everyone who uses the database. ;-)
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
|||If it is OK to have sysadmins privileges for the person, just add a login for the person, and make
it sysadmin.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:6401A53E-E9C0-41F9-9E08-C58B82148BD0@.microsoft.com...[vbcol=seagreen]
> Thanks for the response. Actually I was trying to set up an account for a
> database administrator that could administer all dbases. This would only be
> used by one individual.
> "Rick Sawtell" wrote:
|||ok thanks for the additional information.
"Tibor Karaszi" wrote:

> If it is OK to have sysadmins privileges for the person, just add a login for the person, and make
> it sysadmin.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:6401A53E-E9C0-41F9-9E08-C58B82148BD0@.microsoft.com...
>
>

add new user with all rights to all dbases

Kind of new to Enterprize Manager, just wondering what the steps are to add a
new user that will have all rights to all databases? Thanks.
--
Paul G
Software engineer."Paul" <Paul@.discussions.microsoft.com> wrote in message
news:FF651560-0FE5-4B24-B9C2-C66E227CD0FB@.microsoft.com...
> Kind of new to Enterprize Manager, just wondering what the steps are to
> add a
> new user that will have all rights to all databases? Thanks.
> --
> Paul G
> Software engineer.
Add your new user normally. Either as a Windows Authenticated account or as
a SQL User account.
Add that new user to the sysadmins SQL Server group inside SQL Server.
Just a side note on security here. I hope that this is the user account
that you will be connecting with moving forward and not something you are
planning on giving to everyone who uses the database. ;-)
Rick Sawtell
MCT, MCSD, MCDBA|||Thanks for the response. Actually I was trying to set up an account for a
database administrator that could administer all dbases. This would only be
used by one individual.
"Rick Sawtell" wrote:
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:FF651560-0FE5-4B24-B9C2-C66E227CD0FB@.microsoft.com...
> > Kind of new to Enterprize Manager, just wondering what the steps are to
> > add a
> > new user that will have all rights to all databases? Thanks.
> > --
> > Paul G
> > Software engineer.
> Add your new user normally. Either as a Windows Authenticated account or as
> a SQL User account.
> Add that new user to the sysadmins SQL Server group inside SQL Server.
>
> Just a side note on security here. I hope that this is the user account
> that you will be connecting with moving forward and not something you are
> planning on giving to everyone who uses the database. ;-)
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||If it is OK to have sysadmins privileges for the person, just add a login for the person, and make
it sysadmin.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:6401A53E-E9C0-41F9-9E08-C58B82148BD0@.microsoft.com...
> Thanks for the response. Actually I was trying to set up an account for a
> database administrator that could administer all dbases. This would only be
> used by one individual.
> "Rick Sawtell" wrote:
>> "Paul" <Paul@.discussions.microsoft.com> wrote in message
>> news:FF651560-0FE5-4B24-B9C2-C66E227CD0FB@.microsoft.com...
>> > Kind of new to Enterprize Manager, just wondering what the steps are to
>> > add a
>> > new user that will have all rights to all databases? Thanks.
>> > --
>> > Paul G
>> > Software engineer.
>> Add your new user normally. Either as a Windows Authenticated account or as
>> a SQL User account.
>> Add that new user to the sysadmins SQL Server group inside SQL Server.
>>
>> Just a side note on security here. I hope that this is the user account
>> that you will be connecting with moving forward and not something you are
>> planning on giving to everyone who uses the database. ;-)
>>
>> Rick Sawtell
>> MCT, MCSD, MCDBA
>>
>>|||ok thanks for the additional information.
"Tibor Karaszi" wrote:
> If it is OK to have sysadmins privileges for the person, just add a login for the person, and make
> it sysadmin.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:6401A53E-E9C0-41F9-9E08-C58B82148BD0@.microsoft.com...
> > Thanks for the response. Actually I was trying to set up an account for a
> > database administrator that could administer all dbases. This would only be
> > used by one individual.
> >
> > "Rick Sawtell" wrote:
> >
> >>
> >> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> >> news:FF651560-0FE5-4B24-B9C2-C66E227CD0FB@.microsoft.com...
> >> > Kind of new to Enterprize Manager, just wondering what the steps are to
> >> > add a
> >> > new user that will have all rights to all databases? Thanks.
> >> > --
> >> > Paul G
> >> > Software engineer.
> >>
> >> Add your new user normally. Either as a Windows Authenticated account or as
> >> a SQL User account.
> >>
> >> Add that new user to the sysadmins SQL Server group inside SQL Server.
> >>
> >>
> >> Just a side note on security here. I hope that this is the user account
> >> that you will be connecting with moving forward and not something you are
> >> planning on giving to everyone who uses the database. ;-)
> >>
> >>
> >>
> >> Rick Sawtell
> >> MCT, MCSD, MCDBA
> >>
> >>
> >>
> >>
>
>

Add a new SQL2000 node

Based on the other threads I've read in the group, I'd like to confirm
the steps needed to perform to add a third node to a cluster that has
been running for a while on 2 nodes...
After adding the new node to the cluster, for each instance in the
cluster (assume: each instance is its own cluster group):
1) Run SQL2000 setup from CD on one of the older nodes; instruct setup
to add the new node as a target for failover.
2) Move the cluster group, making it active on the new node.
3) Install SQL2000 SP4 to the instance from the new node.
Am I missing any steps? Are there additional hotfixes (post-SP4) that
should be installed?
The current (active/active) cluster is running on Win2003 ENT SP1, while
the new node already has Win2003 ENT R2 SP2. The plan is to upgrade the
older hosts to the same rev after the new node is up. Is this workable?
To minimize downtime, you don't have to move any groups to apply SP4.
Rather, from the new node, apply SP4. After that, move the SQL group and
apply the post-SP4 hotfix.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"horseradish" <millardjk@.gmail.com> wrote in message
news:O5L1VrQjHHA.4132@.TK2MSFTNGP05.phx.gbl...
Based on the other threads I've read in the group, I'd like to confirm
the steps needed to perform to add a third node to a cluster that has
been running for a while on 2 nodes...
After adding the new node to the cluster, for each instance in the
cluster (assume: each instance is its own cluster group):
1) Run SQL2000 setup from CD on one of the older nodes; instruct setup
to add the new node as a target for failover.
2) Move the cluster group, making it active on the new node.
3) Install SQL2000 SP4 to the instance from the new node.
Am I missing any steps? Are there additional hotfixes (post-SP4) that
should be installed?
The current (active/active) cluster is running on Win2003 ENT SP1, while
the new node already has Win2003 ENT R2 SP2. The plan is to upgrade the
older hosts to the same rev after the new node is up. Is this workable?
|||There's no need to move the cluster group unless you want to test it will
correctly will startup.
For the SP4. If i Remember well Setup will detect that there's only one node
missing for the SP4 binnaries and will update only that node without
affecting the others.
Hope this helps.
Regards.
FR.
"horseradish" wrote:

> Based on the other threads I've read in the group, I'd like to confirm
> the steps needed to perform to add a third node to a cluster that has
> been running for a while on 2 nodes...
> After adding the new node to the cluster, for each instance in the
> cluster (assume: each instance is its own cluster group):
> 1) Run SQL2000 setup from CD on one of the older nodes; instruct setup
> to add the new node as a target for failover.
> 2) Move the cluster group, making it active on the new node.
> 3) Install SQL2000 SP4 to the instance from the new node.
> Am I missing any steps? Are there additional hotfixes (post-SP4) that
> should be installed?
> The current (active/active) cluster is running on Win2003 ENT SP1, while
> the new node already has Win2003 ENT R2 SP2. The plan is to upgrade the
> older hosts to the same rev after the new node is up. Is this workable?
>
|||Tom Moreau wrote:
> To minimize downtime, you don't have to move any groups to apply SP4.
> Rather, from the new node, apply SP4. After that, move the SQL group and
> apply the post-SP4 hotfix.
>
Based on other things I've seen, it appears that I should be able to add
two nodes (my ultimate plan is to get to 3 nodes using two new and one
current host) to the SQL cluster simultaneously, either when installing
SQL2K RTM _or_ SP4.
Then, once I have my 4-node cluster running, I can uninstall from SQL
and MSCS the one node I wish to remove.
Or will I have to fully install & patch the first new node before I can
repeat with the second?
|||You're probably safer to patch as you go. What if there was a failover in
the middle of what you're doing? It's best to have new nodes like the old
one as soon as you can.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"horseradish" <millardjk@.gmail.com> wrote in message
news:Otdi2JojHHA.4896@.TK2MSFTNGP02.phx.gbl...
Tom Moreau wrote:
> To minimize downtime, you don't have to move any groups to apply SP4.
> Rather, from the new node, apply SP4. After that, move the SQL group and
> apply the post-SP4 hotfix.
>
Based on other things I've seen, it appears that I should be able to add
two nodes (my ultimate plan is to get to 3 nodes using two new and one
current host) to the SQL cluster simultaneously, either when installing
SQL2K RTM _or_ SP4.
Then, once I have my 4-node cluster running, I can uninstall from SQL
and MSCS the one node I wish to remove.
Or will I have to fully install & patch the first new node before I can
repeat with the second?
|||Tom Moreau wrote:
> You're probably safer to patch as you go. What if there was a failover in
> the middle of what you're doing? It's best to have new nodes like the old
> one as soon as you can.
>
Thanks! The safer way is the right way for this implementation...
|||Tom Moreau wrote:
> To minimize downtime, you don't have to move any groups to apply SP4.
> Rather, from the new node, apply SP4. After that, move the SQL group and
> apply the post-SP4 hotfix.
>
Which HF is 'the post-SP4 hotfix'?
|||Check out:
http://aspfaq.com/SQL2000Builds.asp
The hotfix to correct the AWE issue is build 8.00.2040. There have been
subsequent fixes, which are cumulative, so you could apply a later one
instead.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"horseradish" <millardjk@.gmail.com> wrote in message
news:%23rObwnioHHA.4412@.TK2MSFTNGP02.phx.gbl...
Tom Moreau wrote:
> To minimize downtime, you don't have to move any groups to apply SP4.
> Rather, from the new node, apply SP4. After that, move the SQL group and
> apply the post-SP4 hotfix.
>
Which HF is 'the post-SP4 hotfix'?