Moving Non-Clustered to Clustered

Hi,
I have been looking for the last few hours for how to move a non-clustered
environment to a clustered environment without having to change the
connection strings of any of our applications. I'm not finding it anywhere.
It's been a while since I did this, and I thought we could have a virtual
name for both instances that are the same as the old computer names (I.E.
Instance 1 is called "Bitter" and instance 2 is called "silver" from the
apps, even if the actual names are ClustName\Instance1 &
Clustname\Instance2).
Is this possible, and can someone point me to where I can find how to do
this, if it is?
Thanks,
Ryan S
SQL DBA
1Jn5:12
You do it by using DNS SRV records. SRV records allows for an arbitary
service to use DNS to map a name to an IP Address and Port number.
When you cut over, create a "Bitter" and "Silver" record that points to the
new clustered instance names.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Ryan S" <RyanS@.discussions.microsoft.com> wrote in message
news:EA78A067-5C48-4C17-9819-064C8399BF0F@.microsoft.com...
> Hi,
> I have been looking for the last few hours for how to move a non-clustered
> environment to a clustered environment without having to change the
> connection strings of any of our applications. I'm not finding it
> anywhere.
> It's been a while since I did this, and I thought we could have a virtual
> name for both instances that are the same as the old computer names (I.E.
> Instance 1 is called "Bitter" and instance 2 is called "silver" from the
> apps, even if the actual names are ClustName\Instance1 &
> Clustname\Instance2).
> Is this possible, and can someone point me to where I can find how to do
> this, if it is?
> Thanks,
> --
> Ryan S
> SQL DBA
> 1Jn5:12
|||Thanks for the help, but I am still having trouble finding exactly how to do
it.
Is it just as simple as redirecting the TCP/IP traffic to the correct
ip/port, like a dyn dns service or is there more to it?
Sorry if we are being obtuse, but neither I, nor my Net Admin, can seem to
find anything in BOL, or at MS or online about setting up a SQL Instance with
DNS SRV records.
Ryan S
SQL DBA
1Jn5:12
"Geoff N. Hiten" wrote:

> You do it by using DNS SRV records. SRV records allows for an arbitary
> service to use DNS to map a name to an IP Address and Port number.
> When you cut over, create a "Bitter" and "Silver" record that points to the
> new clustered instance names.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "Ryan S" <RyanS@.discussions.microsoft.com> wrote in message
> news:EA78A067-5C48-4C17-9819-064C8399BF0F@.microsoft.com...
>
|||That is about all there is to it. And there is no KB article or section in
BOL about abstracting the service name of a SQL server using DNS SRV
records. Maybe I should write something.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Ryan S" <RyanS@.discussions.microsoft.com> wrote in message
news:6FC957E4-8170-470A-AD57-9EC781EBFF6B@.microsoft.com...[vbcol=seagreen]
> Thanks for the help, but I am still having trouble finding exactly how to
> do
> it.
> Is it just as simple as redirecting the TCP/IP traffic to the correct
> ip/port, like a dyn dns service or is there more to it?
> Sorry if we are being obtuse, but neither I, nor my Net Admin, can seem to
> find anything in BOL, or at MS or online about setting up a SQL Instance
> with
> DNS SRV records.
> --
> Ryan S
> SQL DBA
> 1Jn5:12
>
> "Geoff N. Hiten" wrote:
|||Thanks,
If you do write it, reply to this, and I'll be notified.
Thanks again,
Ryan S
Sr SQL DBA
1Jn5:12
"Geoff N. Hiten" wrote:
[vbcol=seagreen]
> That is about all there is to it. And there is no KB article or section in
> BOL about abstracting the service name of a SQL server using DNS SRV
> records. Maybe I should write something.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "Ryan S" <RyanS@.discussions.microsoft.com> wrote in message
> news:6FC957E4-8170-470A-AD57-9EC781EBFF6B@.microsoft.com...