Remove and Add SQL 2005 cluster nodes CHALLENGE!!!

I have a challenge!!!!!!!!!!!
Requirements are:
A. To replace the 2 nodes of SQL 2005 Cluster on Windows 2003 SP1, with a
set of 2 new nodes (hardware).
B. Keep all the settings of SQL 2005, Databases, .etc. the same way they
are.
C. WITH THE SAME IP ADDRESSES (no change to any IP address).
I know the theory is to implement this KB:
http://msdn2.microsoft.com/en-us/library/ms191545.aspx
My question is:
Can I do the following?
1. Remove the second OLD node, using the same ms191545 above.
2. Add (Join) the 1st New node to the cluster.
3. Remove the last OLD node.
4. Add the NEW second node.
Are the above steps feasible?
What are the things I have to be aware about (so I will not break anything).
How can get thru having the same IP addresses with no change on the 2 new
nodes?
Thanks in advance
wit1 wrote:
> I have a challenge!!!!!!!!!!!
> Requirements are:
> A. To replace the 2 nodes of SQL 2005 Cluster on Windows 2003 SP1, with a
> set of 2 new nodes (hardware).
> B. Keep all the settings of SQL 2005, Databases, .etc. the same way they
> are.
> C. WITH THE SAME IP ADDRESSES (no change to any IP address).
Maybe I'm missing something in your 3rd requirement. When you specify
"same IP address," it implies that your requirement is referring to the
cluster _node_, not a cluster group being hosted by the cluster. Why is
that, and what difference does it make?
As the cluster group is moved from one node to another during failure or
intentional move, there should be an IP address for that group that is
separate and unique from the node(s) that own it.
|||I meant that if node 2 (for example) has IP addresses of
1.2.3.4 for the Virtual IP (Cluster group IP)
2.3.4.5 for public (for the NODE itself not the Virtual IP),
and
1.1.1.1 for private (heart beat)
, the new (coming node) that will replace that node 2 should have the same
IP addresses.
So the plan is to un-install SQL from node 2, then evict it, after that join
the NEW node 2 and install SQL with same IP addresses.
Hope that clears things out.
"horseradish" <millardjk@.gmail.com> wrote in message
news:%237hk1iojHHA.5084@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
> wit1 wrote:
with a[vbcol=seagreen]
they
> Maybe I'm missing something in your 3rd requirement. When you specify
> "same IP address," it implies that your requirement is referring to the
> cluster _node_, not a cluster group being hosted by the cluster. Why is
> that, and what difference does it make?
> As the cluster group is moved from one node to another during failure or
> intentional move, there should be an IP address for that group that is
> separate and unique from the node(s) that own it.

Remote User Connection to SQL Server 7 Standard Edition

Is it possible to connect a remote user (in a wide area network) to a
database running on SQL Server 7 Standard Edition.
Do I need the Enterprise Edition to accomplish this?
Yes (to the first)
and
No (to the second)
Mike John
"guez" <guez@.discussions.microsoft.com> wrote in message
news:C4A2552E-74CA-4DDF-A1D1-4A1E05FB773C@.microsoft.com...
> Is it possible to connect a remote user (in a wide area network) to a
> database running on SQL Server 7 Standard Edition.
> Do I need the Enterprise Edition to accomplish this?

Remote User Connection to SQL Server 7 Standard Edition

Is it possible to connect a remote user (in a wide area network) to a
database running on SQL Server 7 Standard Edition.
Do I need the Enterprise Edition to accomplish this?Yes (to the first)
and
No (to the second)
Mike John
"guez" <guez@.discussions.microsoft.com> wrote in message
news:C4A2552E-74CA-4DDF-A1D1-4A1E05FB773C@.microsoft.com...
> Is it possible to connect a remote user (in a wide area network) to a
> database running on SQL Server 7 Standard Edition.
> Do I need the Enterprise Edition to accomplish this?

Remote User Connection to SQL Server 7 Standard Edition

Is it possible to connect a remote user (in a wide area network) to a
database running on SQL Server 7 Standard Edition.
Do I need the Enterprise Edition to accomplish this?Yes (to the first)
and
No (to the second)
Mike John
"guez" <guez@.discussions.microsoft.com> wrote in message
news:C4A2552E-74CA-4DDF-A1D1-4A1E05FB773C@.microsoft.com...
> Is it possible to connect a remote user (in a wide area network) to a
> database running on SQL Server 7 Standard Edition.
> Do I need the Enterprise Edition to accomplish this?sql

Remote database Connection Error!

use sql2k5 surface area configuration tool to enable 'remote connections'.
-oj
"Sujata P" <SujataP@.discussions.microsoft.com> wrote in message
news:94D32EEB-9098-4A51-B55D-95BD84B5AA96@.microsoft.com...
> Hi,
> My Application which is written in VB.Net uses database connection to my
> Local Instance of SQL Server Express version.
> My connection string is " Data
> Source=SM5\SQLEXPRESS;AttachDbFilename=C
:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\Data\MgmtSystem.mdf;Initial
> Catalog=MgmtSystem;Persist
> Security Info=True;User ID=sa;Password=belmont". When I run my application
> from the same machine where SQL Server instance is installed, it works
> fine.
> But now I am intending to use it as Client-Server type as database on
> Server
> and application running from another machine. To test this I have
> deployed
> my application on another machine. When I run it I get following error,
> "An
> error has occured while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default setting SQL Server does not allow remote
> connections.(provider: SQL Network Interface, error: 26 - Error Locating
> Server/Instance specified)(Microsoft SQL Server Error:-1).
> To Fix this I did try enabling all protocols(Shared Memory, TCP/IP, Named
> Pipe). Then I even started SQL Browser service to enable the instance to
> be
> browsed by client. Then Checked if Hide Instance property. Still no Luck.
> I am really going crazy. This is really important for me since we are
> migrating from Access to SQL Server Express. Since in Access my
> application
> can have client server
> Architecture. Same thing I need to have in SQL Express.
> Any help is really appreciated.
> Thanks,
> SujataHi,
My Application which is written in VB.Net uses database connection to my
Local Instance of SQL Server Express version.
My connection string is " Data
Source=SM5\SQLEXPRESS;AttachDbFilename=C
:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Data\MgmtSystem.mdf;Initial Catalog=MgmtSystem;Persist
Security Info=True;User ID=sa;Password=belmont". When I run my application
from the same machine where SQL Server instance is installed, it works fine.
But now I am intending to use it as Client-Server type as database on Server
and application running from another machine. To test this I have deployed
my application on another machine. When I run it I get following error, "An
error has occured while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default setting SQL Server does not allow remote
connections.(provider: SQL Network Interface, error: 26 - Error Locating
Server/Instance specified)(Microsoft SQL Server Error:-1).
To Fix this I did try enabling all protocols(Shared Memory, TCP/IP, Named
Pipe). Then I even started SQL Browser service to enable the instance to be
browsed by client. Then Checked if Hide Instance property. Still no Luck.
I am really going crazy. This is really important for me since we are
migrating from Access to SQL Server Express. Since in Access my application
can have client server
Architecture. Same thing I need to have in SQL Express.
Any help is really appreciated.
Thanks,
Sujata|||use sql2k5 surface area configuration tool to enable 'remote connections'.
-oj
"Sujata P" <SujataP@.discussions.microsoft.com> wrote in message
news:94D32EEB-9098-4A51-B55D-95BD84B5AA96@.microsoft.com...
> Hi,
> My Application which is written in VB.Net uses database connection to my
> Local Instance of SQL Server Express version.
> My connection string is " Data
> Source=SM5\SQLEXPRESS;AttachDbFilename=C
:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\Data\MgmtSystem.mdf;Initial
> Catalog=MgmtSystem;Persist
> Security Info=True;User ID=sa;Password=belmont". When I run my application
> from the same machine where SQL Server instance is installed, it works
> fine.
> But now I am intending to use it as Client-Server type as database on
> Server
> and application running from another machine. To test this I have
> deployed
> my application on another machine. When I run it I get following error,
> "An
> error has occured while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default setting SQL Server does not allow remote
> connections.(provider: SQL Network Interface, error: 26 - Error Locating
> Server/Instance specified)(Microsoft SQL Server Error:-1).
> To Fix this I did try enabling all protocols(Shared Memory, TCP/IP, Named
> Pipe). Then I even started SQL Browser service to enable the instance to
> be
> browsed by client. Then Checked if Hide Instance property. Still no Luck.
> I am really going crazy. This is really important for me since we are
> migrating from Access to SQL Server Express. Since in Access my
> application
> can have client server
> Architecture. Same thing I need to have in SQL Express.
> Any help is really appreciated.
> Thanks,
> Sujata|||Thanks oj...but I found answer...Actually I did everything last time except
creating exceptions in Windows Firewall for instance of my SQL Server to
unblock the connection.
For anyone who is facing similar problem, Follow
http://support.microsoft.com/?id=914277..it is very useful for creating
remote connection.
"oj" wrote:

> use sql2k5 surface area configuration tool to enable 'remote connections'.
> --
> -oj
>
> "Sujata P" <SujataP@.discussions.microsoft.com> wrote in message
> news:94D32EEB-9098-4A51-B55D-95BD84B5AA96@.microsoft.com...
>
>|||Thanks oj...but I found answer...Actually I did everything last time except
creating exceptions in Windows Firewall for instance of my SQL Server to
unblock the connection.
For anyone who is facing similar problem, Follow
http://support.microsoft.com/?id=914277..it is very useful for creating
remote connection.
"oj" wrote:

> use sql2k5 surface area configuration tool to enable 'remote connections'.
> --
> -oj
>
> "Sujata P" <SujataP@.discussions.microsoft.com> wrote in message
> news:94D32EEB-9098-4A51-B55D-95BD84B5AA96@.microsoft.com...
>
>