Installing a Named SQL Instance

I am migrating a SQL Instance to an existing SQL 2000 cluster that already
has the default instance installed. There is a large user community that
will be accessing the databases in the 2nd instance and I am trying to find a
way to configure the installation so that they can continue to use the same
ODBC connections. Today, they are configured using a single name (such as
RAVEN). Is it possible to configure the 2nd instance using this single name?
Thanks in advance.
You should be able to create a DNS SRV record to point to the named
instance.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Brian" <Brian@.discussions.microsoft.com> wrote in message
news:9FC76909-7CB6-48E2-A5E5-236F7665A150@.microsoft.com...
I am migrating a SQL Instance to an existing SQL 2000 cluster that already
has the default instance installed. There is a large user community that
will be accessing the databases in the 2nd instance and I am trying to find
a
way to configure the installation so that they can continue to use the same
ODBC connections. Today, they are configured using a single name (such as
RAVEN). Is it possible to configure the 2nd instance using this single
name?
Thanks in advance.
|||I remember doing this on a migration, and i had issues with some clients
trying to access using the new DNS record, it ws solved applying MDAC 2.8.
I hope you don't run in this error but try to check this is you experience
any problem.
"Tom Moreau" wrote:

> You should be able to create a DNS SRV record to point to the named
> instance.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Brian" <Brian@.discussions.microsoft.com> wrote in message
> news:9FC76909-7CB6-48E2-A5E5-236F7665A150@.microsoft.com...
> I am migrating a SQL Instance to an existing SQL 2000 cluster that already
> has the default instance installed. There is a large user community that
> will be accessing the databases in the 2nd instance and I am trying to find
> a
> way to configure the installation so that they can continue to use the same
> ODBC connections. Today, they are configured using a single name (such as
> RAVEN). Is it possible to configure the 2nd instance using this single
> name?
> Thanks in advance.
>
|||I assumed he was using current MDAC, but that's a good point.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Frivas" <Frivas@.discussions.microsoft.com> wrote in message
news:3DFCE095-1AD3-42E5-B97B-D38570E13B8D@.microsoft.com...
I remember doing this on a migration, and i had issues with some clients
trying to access using the new DNS record, it ws solved applying MDAC 2.8.
I hope you don't run in this error but try to check this is you experience
any problem.
"Tom Moreau" wrote:

> You should be able to create a DNS SRV record to point to the named
> instance.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Brian" <Brian@.discussions.microsoft.com> wrote in message
> news:9FC76909-7CB6-48E2-A5E5-236F7665A150@.microsoft.com...
> I am migrating a SQL Instance to an existing SQL 2000 cluster that already
> has the default instance installed. There is a large user community that
> will be accessing the databases in the 2nd instance and I am trying to
> find
> a
> way to configure the installation so that they can continue to use the
> same
> ODBC connections. Today, they are configured using a single name (such as
> RAVEN). Is it possible to configure the 2nd instance using this single
> name?
> Thanks in advance.
>
|||Named Instance support was introduced in MDAC 2.6. If you have to use an
earlier MDAC stack, you must alias the named instance using the client
network utility on each client.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Frivas" <Frivas@.discussions.microsoft.com> wrote in message
news:3DFCE095-1AD3-42E5-B97B-D38570E13B8D@.microsoft.com...[vbcol=seagreen]
>I remember doing this on a migration, and i had issues with some clients
> trying to access using the new DNS record, it ws solved applying MDAC 2.8.
> I hope you don't run in this error but try to check this is you experience
> any problem.
> "Tom Moreau" wrote: