Multi Instance Cluster Question

From: Ronald (anonymous_at_discussions.microsoft.com)
Date: 04/27/04 

Date: Tue, 27 Apr 2004 15:42:09 -0700

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: Error for a job that uses a MSDASQL linked server
    ... Tibor Karaszi, SQL Server MVP ... that calls a remote stored procedure saved on SQL1. ... The remote stored procedure use a OPENQUERY that uses a MSDASQL ...
    (microsoft.public.sqlserver.server)
  • Re: Error for a job that uses a MSDASQL linked server
    ... Tibor Karaszi, SQL Server MVP ... to SQL1. ... that calls a remote stored procedure saved on SQL1. ...
    (microsoft.public.sqlserver.server)
  • Re: General SQL Clustering Question
    ... Senior SQL Infrastructure Consultant ... Microsoft SQL Server MVP ... following was setup when SQL1 was the active node and was different when SQL2 ... shouldn't be any difference between the nodes either because the cluster ...
    (microsoft.public.sqlserver.clustering)
  • Remote Server issue...
    ... production server to my reporting server. ... I have replication from sql1 to sql2. ... I noticed that there is already a remote server setup on ...
    (microsoft.public.sqlserver.security)
  • error 18483 & 18482
    ... as a remote login at the server. ... that the name returned is not the same as the computer name(e.g SQL1) ... to SQL1 because 'SQL2' is not defined as a remote server ...
    (microsoft.public.sqlserver.replication)