Re: Multi Instance Cluster Question

From: Geoff N. Hiten (SRDBA_at_Careerbuilder.com)
Date: 04/27/04 

Date: Tue, 27 Apr 2004 19:46:36 -0400

Answer #1.
You can have one default instance and 15 named instances OR 16 named
instances of SQL per cluster. Each named instance will be
VirtualServerName\InstanceName. For consistancy I use only named
instances on a cluster, but that is just a personal thing.

Answer #2.
You may have an older version of MDAC on your client system. I think the
breakover is MDAC 2.6, but I may be wrong. Version 2.6 and higher
understand named instances. Versions before that do not. You can make an
older version connect to a named instance if you create an alias that
includes the port number. 

-- 
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"Ronald" <anonymous@discussions.microsoft.com> wrote in message
news:520a01c42ca8$dfdc9680$a301280a@phx.gbl...
> I decided to try and setup a multi instance cluster on my
> own and seem to be fairly successful . Its SQL 2000 EE on
> Windows Server 2003 EE
>
> Just had 2 questions. When i installed the second
> instance, it asked me for a virtual name.. so i gave it
> one ..in my case SQL2.. and then was asked for an
> instance name so i called it ins2.. Eventually this
> second sql server is now called sql2\ins2 and not sql2 as
> i had thought it would be..  The first instance which was
> a default instance was named as SQL1 . Is this the right
> way it should be ? i.e one instance called SQL1 and the
> other SQL2\ins2 in my case. I was under the impression
> that since its a virtual name i could get them to be
> called SQL1 and SQL2
>
> If not, then my next question is..
>
> When i connect to those 2 virtual names from a client, it
> seems to connect fine to SQL1 but when i connect to SQL2
> \ins2 it fails...with SQL Server does not exist or access
> denied. Any reason why ? Thanks

Relevant Pages

  • Re: Two named instances. Why ?
    ... I agree with Mike & Geoff. ... All my clustered SQL instances have always ... think of to having both instances being named instances and the ...
    (microsoft.public.sqlserver.clustering)
  • Re: Default or named instances??
    ... Come to think of it, a lot of SQL documentation doesn't specify exceptons for clusters where they are clearly warranted, but that is another discussion. ... When it comes to default and named instances on a cluster, you treat the cluster as you would a single system, that is you get a single default instance per cluster, nt per node. ... As for the relationship between a virtual server and an instance, ...
    (microsoft.public.sqlserver.clustering)
  • Re: Default or named instances??
    ... The limitation that makes it impossible is that each virtual server can only host a single SQL instance. ... And it is the cluster, not the virtual server, that is the entity that is limited to a single default instance. ... When it comes to default and named instances on a cluster, you treat the cluster as you would a single system, that is you get a single default instance per cluster, nt per node. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Enumerating Named Instances of SQL Server/MSDE
    ... I think SQL Enterprise Manager uses ... SQL-DMO, and it doesn't detect named instances automatically either on ... >> running SQL Server on the network, but it doesn't return any SQL ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Accessing SQL 2K from SQL 7
    ... I think) don't understand named instances. ... try creating an alias that includes specifying the port number. ... > We added a new SQL instance of SQL 2K - name XXX\AB ... > "Specified SQL Server not found" ...
    (microsoft.public.sqlserver.security)