MultiServer SQL 2000 SP3 Administration

Hello,
I am trying to set up multiadministration server, since my company has 2
central cluster servers, with SQL Server 2000 SP3a, and 80 local sql server
2000 SP3a.
I have recently upgraded a central to SP3, and did the same for a local sql
server. Both are in the same domain, started by an special administrator
account for SQL Server services (both SQL Server service and SQL Agent).
I'm thus using Windows authentification. I tried to set up both server for
multiadministration, using SQL queries :
==> EXEC xp_sqlagent_msx_account N'SET', N'', N'', N''
to run multiadministration server under SQL agent account, and then
==>
EXEC sp_grantlogin 'MyDomain\MyUser'
USE msdb
EXEC sp_adduser 'MyDomain\MyUser', MyDomain\MyUser', 'TargetServersRole'
on each server, both central and target (local).
Then I try to set up multiadministration using EM, but the 'Specify MSX
Account' step fails, saying the account I'm using is not a valid MSX Account.
I can't find any more help on forums and BOL.
Your help will be much appreciated...This message was posted a few weeks
ago, but no answer on the SQL server tools forum. Thanks a lot for your help.
Xavier MarcatelCheck the section on "Multi-Server Administration" at this link:
http://www.sqlservercentral.com/columnists/bkelley/sp3coresecurity.asp
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"PetitGosaimass" <PetitGosaimass@.discussions.microsoft.com> wrote in message
news:63E1D6DA-68CB-4EAA-88FC-4462FBF9C5F4@.microsoft.com...
> Hello,
> I am trying to set up multiadministration server, since my company has 2
> central cluster servers, with SQL Server 2000 SP3a, and 80 local sql
> server
> 2000 SP3a.
> I have recently upgraded a central to SP3, and did the same for a local
> sql
> server. Both are in the same domain, started by an special administrator
> account for SQL Server services (both SQL Server service and SQL Agent).
> I'm thus using Windows authentification. I tried to set up both server for
> multiadministration, using SQL queries :
> ==> EXEC xp_sqlagent_msx_account N'SET', N'', N'', N''
> to run multiadministration server under SQL agent account, and then
> ==>
> EXEC sp_grantlogin 'MyDomain\MyUser'
> USE msdb
> EXEC sp_adduser 'MyDomain\MyUser', MyDomain\MyUser', 'TargetServersRole'
> on each server, both central and target (local).
> Then I try to set up multiadministration using EM, but the 'Specify MSX
> Account' step fails, saying the account I'm using is not a valid MSX
> Account.
> I can't find any more help on forums and BOL.
> Your help will be much appreciated...This message was posted a few weeks
> ago, but no answer on the SQL server tools forum. Thanks a lot for your
> help.
> Xavier Marcatel
>

MultiServer SQL 2000 SP3 Administration

Hello,
I am trying to set up multiadministration server, since my company has 2
central cluster servers, with SQL Server 2000 SP3a, and 80 local sql server
2000 SP3a.
I have recently upgraded a central to SP3, and did the same for a local sql
server. Both are in the same domain, started by an special administrator
account for SQL Server services (both SQL Server service and SQL Agent).
I'm thus using Windows authentification. I tried to set up both server for
multiadministration, using SQL queries :
==> EXEC xp_sqlagent_msx_account N'SET', N'', N'', N''
to run multiadministration server under SQL agent account, and then
==>
EXEC sp_grantlogin 'MyDomain\MyUser'
USE msdb
EXEC sp_adduser 'MyDomain\MyUser', MyDomain\MyUser', 'TargetServersRole'
on each server, both central and target (local).
Then I try to set up multiadministration using EM, but the 'Specify MSX
Account' step fails, saying the account I'm using is not a valid MSX Account
.
I can't find any more help on forums and BOL.
Your help will be much appreciated...This message was posted a few weeks
ago, but no answer on the SQL server tools forum. Thanks a lot for your help
.
Xavier MarcatelCheck the section on "Multi-Server Administration" at this link:
http://www.sqlservercentral.com/col...oresecurity.asp
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"PetitGosaimass" <PetitGosaimass@.discussions.microsoft.com> wrote in message
news:63E1D6DA-68CB-4EAA-88FC-4462FBF9C5F4@.microsoft.com...
> Hello,
> I am trying to set up multiadministration server, since my company has 2
> central cluster servers, with SQL Server 2000 SP3a, and 80 local sql
> server
> 2000 SP3a.
> I have recently upgraded a central to SP3, and did the same for a local
> sql
> server. Both are in the same domain, started by an special administrator
> account for SQL Server services (both SQL Server service and SQL Agent).
> I'm thus using Windows authentification. I tried to set up both server for
> multiadministration, using SQL queries :
> ==> EXEC xp_sqlagent_msx_account N'SET', N'', N'', N''
> to run multiadministration server under SQL agent account, and then
> ==>
> EXEC sp_grantlogin 'MyDomain\MyUser'
> USE msdb
> EXEC sp_adduser 'MyDomain\MyUser', MyDomain\MyUser', 'TargetServersRole'
> on each server, both central and target (local).
> Then I try to set up multiadministration using EM, but the 'Specify MSX
> Account' step fails, saying the account I'm using is not a valid MSX
> Account.
> I can't find any more help on forums and BOL.
> Your help will be much appreciated...This message was posted a few weeks
> ago, but no answer on the SQL server tools forum. Thanks a lot for your
> help.
> Xavier Marcatel
>

Multiple-Instance Cluster

Situation: Two nodes, two nodes are active, two virtual
servers, two separate applications. One active and one
wait on each. Active on each fails over to wait on each
other server so that I should only lose one application at
a time.
Question: Two SQL instances on each node/virtual server?
Each SQL instance has its own IP address? The active and
wait have their own IP addresses?
Ok, so you want to run a 2 node cluster, with both nodes being active at the
same time. Two databases for two applications.
You will only need 1 instance of SQL on a node, unless the application
requires something different.
Each Node will have an IP addr, the cluster will have an addr, and each
instance (1 on each server) will have an IP addr.
With all the said, I never recommend an Active/Active cluster. SQL optimizes
memory. When you have a failure, both instances of SQL and its IP addr will
then be on one box. This will change the way SQL can use and optimize
memory. This process takes time, during that time, the system is much
slower. Performance on most Active/Active SQL Clusters suffer during a
failed state.
If at all possible, run both apps on the same node, at the same time. Making
sure of course, that each system has ample resources.
Hope this helps.
Cheers,
Rod
"Lucian" <anonymous@.discussions.microsoft.com> wrote in message
news:1d2b101c42329$d3d501c0$a401280a@.phx.gbl...
> Situation: Two nodes, two nodes are active, two virtual
> servers, two separate applications. One active and one
> wait on each. Active on each fails over to wait on each
> other server so that I should only lose one application at
> a time.
> Question: Two SQL instances on each node/virtual server?
> Each SQL instance has its own IP address? The active and
> wait have their own IP addresses?
|||With SQL Server 2000 you can install up to 16 instances (1 default and 15
named or 16 named). The number of nodes that can be a possible owner for
each instance depends on your edition/version of Windows. If you have a
typical 2-node cluster, each node can own 0,1, or many of the installed
instances.
Whether it makes sense to install multiple instances (something that used
to be called active/active when you could only have two instances) depends
totally on your environment - your hardware, your application, your
business needs, etc.
If you want to know more about clustering, check out BOL or the MSPress
book on High Availability.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Multiple SQL Clusters on one EMC LUN?

Hello,
We have a Production SQL 2000 Cluster and are now developing on SQL 2K5 as
we plan to migrate shortly. We'll be introducing new hardware into
production with 2K5 installed. We would like to use a 'straddle migration'
method by utilizing both 2K and 2K5 in production at the same time and
moving services/websites/databases to 2K5 one at a time in case there are
any issues and we need to roll back over to 2K.
The question is how can we utilize the current LUNs/Cluster that's on the
EMC for the new 2K5 servers/cluster? Can we have a 2K and 2K5 cluster using
the same LUN? How would the Q: Quarum drive work? What possible
complications do see in this scenario?
Thank you in advance for your time,
Andew
If you do side by side, then you cannot use the same virtual server name,
instance name, IP address, or network port. Moreover, you will have to have
an independent dedicated disk(s) for the installation to even succeed.
Afterwards, however, you can use either detach/attach or database backups
and restores to migrate from one instance the next. If a rollback is called
for, you only have to point the connections back to the SS2K instance and
you're off and running again.
If your upgrade is successful, then you just uninstall the SS2K instance and
give storage back their original LUN for reuse.
What we typically do is restore pending the prior day's full database
backup, and then kick off a differential right before the migration. This
keeps the backup, transfer, restore window small during the migration
outage.
Sincerely,
Anthony Thomas

"Andrew Williams" <andrew.williams@.freedompay.com> wrote in message
news:99A9028F-DB5C-4E5F-9320-8BCA23F0C2B7@.microsoft.com...
> Hello,
> We have a Production SQL 2000 Cluster and are now developing on SQL 2K5 as
> we plan to migrate shortly. We'll be introducing new hardware into
> production with 2K5 installed. We would like to use a 'straddle
migration'
> method by utilizing both 2K and 2K5 in production at the same time and
> moving services/websites/databases to 2K5 one at a time in case there are
> any issues and we need to roll back over to 2K.
> The question is how can we utilize the current LUNs/Cluster that's on the
> EMC for the new 2K5 servers/cluster? Can we have a 2K and 2K5 cluster
using
> the same LUN? How would the Q: Quarum drive work? What possible
> complications do see in this scenario?
> Thank you in advance for your time,
>
> Andew
>
|||> Can we have a 2K and 2K5 cluster using
> the same LUN?
(assuming with LUN you mean physical disk resource in the cluster)
No, they need to be in there own dedicated cluster group with dedicated
physical disk resources

> How would the Q: Quarum drive work?
Quorum disk should be, together with cluster IP and cluster name and
possibly MSDTC, in it own cluster group, this is the *default* setup. No
changes for the Quorum disk
So you end up with:
cluster group - cluster resources (including Quorum disk)
group1 - SQL2K (with its own dedicated disks, IP, network name)
group2 - SQL2K5 (with its own dedicated disks, IP, network name)
does this answer your question ?
rgds,
edwin.