Migrating Clusters

Hi All,
We have a 2 node cluster running SQL Server 2000 on Windows 2000 which
needs replacing. The nature of our business is 24 hour operation, so
the downtime to do such needs to be as small as possible.
We have a new cluster ready and waiting in our data centre that is
built on Windows 2003 with SQL Server 2000.
Our issues are:
=B7Configuring all the applications to the new Cluster Name / IP
Address - In the past we have found things hard-coded
=B7Migrate all the data (~100GB) over to the new MSA
=B7Smallest downtime possible
The idea's we have come up with already are:
=B7Frigg DNS to point the old cluster name to the new cluster name and
then migrate all the applications to the new name as time permits.
=B7Rename the new nodes as <NAME>3/4 and add these into the existing
cluster; however the MSA is directly connected to Nodes 1/2.
=B7Remove 1 node from the old cluster, add a new node in, fail-over to
new node, remove 2nd old node, add new node, however I'm thinking
this may not work?
Another consideration is that we use SecurePath on the MSA's so this
could be a PITA.
Does anyone have any other suggestions which we could consider?
Thanks
Well, since you asked.
You could do a minimally disruptive replacement by replacing each node with
one of the new nodes. Uninstall SQL from the "other" node, evict the node,
add the node, run the SQL nstaller to install and configure SQL on the new
node. Wait for maintenance window and do a failover test. Repeat with the
other node.
The other process I use to migrate systems is to run a custom log ship
script (they aren't that hard to write, google will point to some nice free
examples.) to get them ready. Do a final log backup and put the old
databases into norecovery mode. Do a final catch up and go live on the new
system. Patch DNS (hint, use the SRV record type). and go. I can switch
over a typical server with 10-30 databases with less than 10 minutes of
downtime this way.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Steve" <SMaxwell@.NationalExpress.com> wrote in message
news:1160476240.405910.76230@.e3g2000cwe.googlegrou ps.com...
Hi All,
We have a 2 node cluster running SQL Server 2000 on Windows 2000 which
needs replacing. The nature of our business is 24 hour operation, so
the downtime to do such needs to be as small as possible.
We have a new cluster ready and waiting in our data centre that is
built on Windows 2003 with SQL Server 2000.
Our issues are:
Configuring all the applications to the new Cluster Name / IP
Address - In the past we have found things hard-coded
Migrate all the data (~100GB) over to the new MSA
Smallest downtime possible
The idea's we have come up with already are:
Frigg DNS to point the old cluster name to the new cluster name and
then migrate all the applications to the new name as time permits.
Rename the new nodes as <NAME>3/4 and add these into the existing
cluster; however the MSA is directly connected to Nodes 1/2.
Remove 1 node from the old cluster, add a new node in, fail-over to
new node, remove 2nd old node, add new node, however I'm thinking
this may not work?
Another consideration is that we use SecurePath on the MSA's so this
could be a PITA.
Does anyone have any other suggestions which we could consider?
Thanks

MICROSOFT##SSEE blocks Surface Area Configuration in SQL 2005?

I am running a Windows Small Business Server with SQL Server 2005 on it. I am having a problem in that one of the applications I'm running needs to acess the xp_cmdshell component which is disabled by default. The problem I'm running into is, trying to run the Surface Area Configuration Wizard to turn this on fails because the system is unable to access the MICROSOFT##SSEE instance on the machine.

I dont want to modify the MICROSOFT##SSEE instance, I want to modify a different instance but the wizard detects ALL instances of SQL and craps out trying to access the MICROSOFT##SSEE instance.

Is there a way for me to activate the xp_cmdshell component on other instances without the wizard?

Hi,

Run this code in your query window:

Code Snippet

sp_configure 'xp_cmdshell', 1

reconfigure

Regards,

Janos

|||

I get the following message:

Msg 15123, Level 16, State 1, Procedure sp_configure, Line 51

The configuration option 'xp_cmdshell' does not exist, or it may be an advanced option.

|||

Hi Ron,

First you need to switch on the advanced options, then configure the xp_cmdshell.

run this please:

Code Snippet

sp_configure 'show advanced options', 1

reconfigure

sp_configure 'xp_cmdshell', 1

reconfigure

regards,

Janos

|||Thank you, that did the trick... now I just have to get my code to work <grin>

Microsoft##EESS and MSDE SQL 2000 on Windows 2003 Small Business Server

Currently a server running 2003 small business operating system has MSDE 2000 and Microsoft##SSEE.

A memory problem exists with SQL consuming over 50% of RAM. Total RAM is 4GB.

There is a SQL 2000 patch for this type of problem. However, it calls for SQL to be upgraded to SP4.

Problem:
Can this MSDE 2000 be upgraded with SP4 and have memory patch applied with Microsoft##SSEE also on this box?

Please let me know. Thank you.

Yes.

You might also investigate setting the MAX memory setting for both SQL instances.

|||

Hi,

Yes you can update with SQL Server SP4.

Refering to SQL Server memory architecture it goes upto maximum limit specify by you, and if not specified it can eat up all the memory it can access and freed up as N when require by another resources. I think below articles are good enough to clear it

http://sqljunkies.com/Tutorial/0D4FF40A-695C-4327-A41B-F9F2FE2D58F6.scuk

http://msdn2.microsoft.com/en-us/library/ms187499.aspx

HTH

Hemantgiri S. Goswami