Multiple Instances of SQL Server on a Failover Cluster

  • Hi All,
    We've been running two two-node active/passive clusters (one development, one production) running Windows Server 2003 here for some time without incident (knock wood!).  We now have the need to install another instance onto the clusters.  We've started in development by creating a separate LUN for the new instance of SQL Server and have been able to install a default instance on the first virtual server, and a named instance on a separate virtual server.
    I'm a little confused though, because I'm not getting the option to install a default instance of SQL Server on the newly-created virtual server.  Should I be getting this option?
    These are the steps we took:
    1.  Installed default instance of SQL Server on two-node cluster "DCluster."  This allowed us to install under the virtual server name of "SQLD1."
    2.  Service packed this instance to SP3a.
    3.  Started installation of SQL Server again, entered "XCluster" as the virtual name.  NOTE: we did not add this in DNS first, and if I had to guess, I'd say this might be the problem.
    4.  Got to the point in the install where it normally asks whether you'd like to create a default instance or named instance, the "Default" checkbox was grayed out and we were forced to name the instance "SQLInstance1."
    5. Setup finished successfully, albeit with a named instance on the XCluster virtual server.
    Am I missing something here?  I read through the knowledge base article 815431 but it didn't seem to speak to the problem that we're having.  In a way, our problem is the opposite of what's described here:

    http://support.microsoft.com/kb/815431

    I've included the text that leads me to believe I can add a default instance of SQL onto each virtual server below.  Any help is greatly appreciated.
    Thanks in advance!!
    Cheers,
    -m
    -----------------------------
    Multiple Instances of SQL Server on a Failover Cluster

    You can run only one instance of SQL Server on each virtual server of a SQL Server failover cluster, although you can install up to 16 virtual servers on a failover cluster. The instance can be either a default instance or a named instance. The virtual server looks like a single computer to applications connecting to that instance of SQL Server. When applications connect to the virtual server, they use the same convention as when connecting to any instance of SQL Server; they specify the virtual server name of the cluster and the optional instance name (only needed for named instances): virtualservername\instancename. For more information about clustering, see (books online link).

  • You can't be able to add a default instance in the second node o virtual server, from BOL -->

    Naming a Virtual Server

    SQL Server 2000 depends on distinct registry keys and service names within the failover cluster so that operations will continue correctly after a failover. Therefore, the name you provide for the instance of SQL Server 2000, including the default instance, must be unique across all nodes in the failover cluster, as well as across all virtual servers within the failover cluster. For example, if all instances failed over to a single server, their service names and registry keys would conflict. If INST1 is a named instance on virtual server VIRTSRV1, there cannot be a named instance INST1 on any node in the failover cluster, either as part of a failover cluster configuration or as a stand-alone installation.

    Additionally, you must use the VIRTUAL_SERVER\Instance-name string to connect to a clustered instance of SQL Server 2000 running on a virtual server. You cannot access the instance of SQL Server 2000 by using the computer name that the clustered instance happens to reside on at any given time. SQL Server 2000 does not listen on the IP address of the local servers. It listens only on the clustered IP addresses created during the setup of a virtual server for SQL Server 2000.

    JR

  • Hey JR,

    Thanks for your reply!  I'm not sure this speaks to my question, however.  I did find a post online that has answered my question though:

    http://www.mcse.ms/message279800.html

    This states that a clustered SQL 2000 installation may only have a total of one (1) default instance, no matter how many "virtual servers" are defined on that cluster.  I guess I interpreted what I quoted in my original post incorrectly.

    Again, thanks for your input!

    Cheers,

    -m

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply