 |
|
|
|
Next: T-SQL Sudoku Game
|
| Author |
Message |
External
Since: Jan 14, 2008
Posts: 4
|
(Msg. 1) Posted: Mon Jan 14, 2008 8:04 am
Post subject: Single node cluster with multiple instances but all as default ins
Archived from groups: microsoft>public>sqlserver>clustering (more info?)
|
|
|
Hi,
I am trying to install multiple SQL 2005 instances onto one machine, which
has been configured as a single node cluster. Multiple virtual servers have
been created, and I am trying to install one instance onto each virtual
server set up for SQL installation, and the instance should all be default so
that when referencing the sql instance only the virtual server's name is
needed. Is this possible at all?
The scenario:
Server box name: ServerA
Virtual server names:
1. SQL1
2. SQL2
3. SQL3
I logged into virtual server SQL1, installed a default sql instance (during
the intallation the Virtual SQL Server Name page never appeared, an
indication that the MSCS was not set up properly?). Then I (successfully,
indicating that the cluster/virtual machine set up is done (probably)
correctly?) logged in to SQL2, but when trying to install a default sql
instance on this virtual server, the intallation recognizes an existing
default intance and would not do the next default installation.
There are a few reasons that I am not successful so far:
1. Single node cluster would not support this at all
2. The cluster service was not set up right
3. I am doing something wrong
I just can not see what I am doing is wrong. Anyone can help pointing out
what I should look at? Much thanks. |
|
| Back to top |
|
 | |
External
Since: Jan 10, 2008
Posts: 111
|
(Msg. 2) Posted: Mon Jan 14, 2008 12:00 pm
Post subject: Re: Single node cluster with multiple instances but all as default ins [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
The short answer is "no".
Even though each SQL instance lives in its own virtual space, there can be
only one default SQL instance per cluster.
You can use a DNS alias to map a short name to the clustered instance name
so when a Client connects to SQL1, they are redirected to the appropriate IP
address and port number.
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"SQL Question" wrote in message
> Hi,
>
> I am trying to install multiple SQL 2005 instances onto one machine, which
> has been configured as a single node cluster. Multiple virtual servers
> have
> been created, and I am trying to install one instance onto each virtual
> server set up for SQL installation, and the instance should all be default
> so
> that when referencing the sql instance only the virtual server's name is
> needed. Is this possible at all?
>
> The scenario:
>
> Server box name: ServerA
> Virtual server names:
> 1. SQL1
> 2. SQL2
> 3. SQL3
>
> I logged into virtual server SQL1, installed a default sql instance
> (during
> the intallation the Virtual SQL Server Name page never appeared, an
> indication that the MSCS was not set up properly?). Then I (successfully,
> indicating that the cluster/virtual machine set up is done (probably)
> correctly?) logged in to SQL2, but when trying to install a default sql
> instance on this virtual server, the intallation recognizes an existing
> default intance and would not do the next default installation.
>
> There are a few reasons that I am not successful so far:
> 1. Single node cluster would not support this at all
> 2. The cluster service was not set up right
> 3. I am doing something wrong
>
> I just can not see what I am doing is wrong. Anyone can help pointing out
> what I should look at? Much thanks.
> |
|
| Back to top |
|
| |
External
Since: Jan 14, 2008
Posts: 4
|
(Msg. 3) Posted: Mon Jan 14, 2008 1:01 pm
Post subject: Re: Single node cluster with multiple instances but all as default [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Much thanks Geoff.
Meanwhile I have tried and asked around and found more about the server
setup that affects the SQL installation and my attempt of simplifying the way
SQL instances are referenced.
though the server has been set up as a single node cluster, it does not have
a shared storage. It has a single SCSI drive that has a few partitions, with
C used as system drive and quarom. This makes it impossible to assign
different IP addresses to different instances, which is a requirement for the
DNS aliasing.
I don't know whether you have any other suggestions as to how I can achieve
what I am trying -- to use a single one part name for the instances to be
referenced, instead of using the machine-name\instance-name two part name.
Thanks for your looking into this and advanced thanks for your possible
reply. I will check back.
"Geoff N. Hiten" wrote:
> The short answer is "no".
>
> Even though each SQL instance lives in its own virtual space, there can be
> only one default SQL instance per cluster.
>
> You can use a DNS alias to map a short name to the clustered instance name
> so when a Client connects to SQL1, they are redirected to the appropriate IP
> address and port number.
>
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
>
> "SQL Question" wrote in message
>
> > Hi,
> >
> > I am trying to install multiple SQL 2005 instances onto one machine, which
> > has been configured as a single node cluster. Multiple virtual servers
> > have
> > been created, and I am trying to install one instance onto each virtual
> > server set up for SQL installation, and the instance should all be default
> > so
> > that when referencing the sql instance only the virtual server's name is
> > needed. Is this possible at all?
> >
> > The scenario:
> >
> > Server box name: ServerA
> > Virtual server names:
> > 1. SQL1
> > 2. SQL2
> > 3. SQL3
> >
> > I logged into virtual server SQL1, installed a default sql instance
> > (during
> > the intallation the Virtual SQL Server Name page never appeared, an
> > indication that the MSCS was not set up properly?). Then I (successfully,
> > indicating that the cluster/virtual machine set up is done (probably)
> > correctly?) logged in to SQL2, but when trying to install a default sql
> > instance on this virtual server, the intallation recognizes an existing
> > default intance and would not do the next default installation.
> >
> > There are a few reasons that I am not successful so far:
> > 1. Single node cluster would not support this at all
> > 2. The cluster service was not set up right
> > 3. I am doing something wrong
> >
> > I just can not see what I am doing is wrong. Anyone can help pointing out
> > what I should look at? Much thanks.
> >
>
> >> Stay informed about: Single node cluster with multiple instances but all as def.. |
|
| Back to top |
|
| |
External
Since: Jan 10, 2008
Posts: 111
|
(Msg. 4) Posted: Tue Jan 15, 2008 10:13 am
Post subject: Re: Single node cluster with multiple instances but all as default [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
You can create multiple instances without clustering. I think you are
trying to fake a cluster to get around the "one default instance per
computer" limitation. However, you still have only one default instance per
cluster, so faking a cluster with a single node will not help. You can
always create client aliases, but that gets time consuming and hard to
manage. I still suggest DNS aliases for short name to IP address/port
number combination. Check with your network guru.
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"SQL Question" wrote in message
> Much thanks Geoff.
>
> Meanwhile I have tried and asked around and found more about the server
> setup that affects the SQL installation and my attempt of simplifying the
> way
> SQL instances are referenced.
>
> though the server has been set up as a single node cluster, it does not
> have
> a shared storage. It has a single SCSI drive that has a few partitions,
> with
> C used as system drive and quarom. This makes it impossible to assign
> different IP addresses to different instances, which is a requirement for
> the
> DNS aliasing.
>
> I don't know whether you have any other suggestions as to how I can
> achieve
> what I am trying -- to use a single one part name for the instances to be
> referenced, instead of using the machine-name\instance-name two part name.
>
> Thanks for your looking into this and advanced thanks for your possible
> reply. I will check back.
>
>
> "Geoff N. Hiten" wrote:
>
>> The short answer is "no".
>>
>> Even though each SQL instance lives in its own virtual space, there can
>> be
>> only one default SQL instance per cluster.
>>
>> You can use a DNS alias to map a short name to the clustered instance
>> name
>> so when a Client connects to SQL1, they are redirected to the appropriate
>> IP
>> address and port number.
>>
>> --
>> Geoff N. Hiten
>> Senior SQL Infrastructure Consultant
>> Microsoft SQL Server MVP
>>
>>
>>
>> "SQL Question" wrote in message
>>
>> > Hi,
>> >
>> > I am trying to install multiple SQL 2005 instances onto one machine,
>> > which
>> > has been configured as a single node cluster. Multiple virtual servers
>> > have
>> > been created, and I am trying to install one instance onto each virtual
>> > server set up for SQL installation, and the instance should all be
>> > default
>> > so
>> > that when referencing the sql instance only the virtual server's name
>> > is
>> > needed. Is this possible at all?
>> >
>> > The scenario:
>> >
>> > Server box name: ServerA
>> > Virtual server names:
>> > 1. SQL1
>> > 2. SQL2
>> > 3. SQL3
>> >
>> > I logged into virtual server SQL1, installed a default sql instance
>> > (during
>> > the intallation the Virtual SQL Server Name page never appeared, an
>> > indication that the MSCS was not set up properly?). Then I
>> > (successfully,
>> > indicating that the cluster/virtual machine set up is done (probably)
>> > correctly?) logged in to SQL2, but when trying to install a default sql
>> > instance on this virtual server, the intallation recognizes an existing
>> > default intance and would not do the next default installation.
>> >
>> > There are a few reasons that I am not successful so far:
>> > 1. Single node cluster would not support this at all
>> > 2. The cluster service was not set up right
>> > 3. I am doing something wrong
>> >
>> > I just can not see what I am doing is wrong. Anyone can help pointing
>> > out
>> > what I should look at? Much thanks.
>> >
>>
>> >> Stay informed about: Single node cluster with multiple instances but all as def.. |
|
| Back to top |
|
| |
External
Since: Jan 14, 2008
Posts: 4
|
(Msg. 5) Posted: Tue Jan 15, 2008 10:13 am
Post subject: Re: Single node cluster with multiple instances but all as default [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Thanks Geoff. Yes I am trying to get a simple name for applications. The
client aliases would be so cumbersome that it defeats the efforts. I'll try
to get a shared storage to have the cluster set up as a single node but
"true" cluster, or stick with the two part naming.
"Geoff N. Hiten" wrote:
> You can create multiple instances without clustering. I think you are
> trying to fake a cluster to get around the "one default instance per
> computer" limitation. However, you still have only one default instance per
> cluster, so faking a cluster with a single node will not help. You can
> always create client aliases, but that gets time consuming and hard to
> manage. I still suggest DNS aliases for short name to IP address/port
> number combination. Check with your network guru.
>
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
>
>
> "SQL Question" wrote in message
>
> > Much thanks Geoff.
> >
> > Meanwhile I have tried and asked around and found more about the server
> > setup that affects the SQL installation and my attempt of simplifying the
> > way
> > SQL instances are referenced.
> >
> > though the server has been set up as a single node cluster, it does not
> > have
> > a shared storage. It has a single SCSI drive that has a few partitions,
> > with
> > C used as system drive and quarom. This makes it impossible to assign
> > different IP addresses to different instances, which is a requirement for
> > the
> > DNS aliasing.
> >
> > I don't know whether you have any other suggestions as to how I can
> > achieve
> > what I am trying -- to use a single one part name for the instances to be
> > referenced, instead of using the machine-name\instance-name two part name.
> >
> > Thanks for your looking into this and advanced thanks for your possible
> > reply. I will check back.
> >
> >
> > "Geoff N. Hiten" wrote:
> >
> >> The short answer is "no".
> >>
> >> Even though each SQL instance lives in its own virtual space, there can
> >> be
> >> only one default SQL instance per cluster.
> >>
> >> You can use a DNS alias to map a short name to the clustered instance
> >> name
> >> so when a Client connects to SQL1, they are redirected to the appropriate
> >> IP
> >> address and port number.
> >>
> >> --
> >> Geoff N. Hiten
> >> Senior SQL Infrastructure Consultant
> >> Microsoft SQL Server MVP
> >>
> >>
> >>
> >> "SQL Question" wrote in message
> >>
> >> > Hi,
> >> >
> >> > I am trying to install multiple SQL 2005 instances onto one machine,
> >> > which
> >> > has been configured as a single node cluster. Multiple virtual servers
> >> > have
> >> > been created, and I am trying to install one instance onto each virtual
> >> > server set up for SQL installation, and the instance should all be
> >> > default
> >> > so
> >> > that when referencing the sql instance only the virtual server's name
> >> > is
> >> > needed. Is this possible at all?
> >> >
> >> > The scenario:
> >> >
> >> > Server box name: ServerA
> >> > Virtual server names:
> >> > 1. SQL1
> >> > 2. SQL2
> >> > 3. SQL3
> >> >
> >> > I logged into virtual server SQL1, installed a default sql instance
> >> > (during
> >> > the intallation the Virtual SQL Server Name page never appeared, an
> >> > indication that the MSCS was not set up properly?). Then I
> >> > (successfully,
> >> > indicating that the cluster/virtual machine set up is done (probably)
> >> > correctly?) logged in to SQL2, but when trying to install a default sql
> >> > instance on this virtual server, the intallation recognizes an existing
> >> > default intance and would not do the next default installation.
> >> >
> >> > There are a few reasons that I am not successful so far:
> >> > 1. Single node cluster would not support this at all
> >> > 2. The cluster service was not set up right
> >> > 3. I am doing something wrong
> >> >
> >> > I just can not see what I am doing is wrong. Anyone can help pointing
> >> > out
> >> > what I should look at? Much thanks.
> >> >
> >>
> >>
>
> >> Stay informed about: Single node cluster with multiple instances but all as def.. |
|
| Back to top |
|
| |
| Related Topics: | One node SQL cluster - Hey guys, I have a client who would like to install a one node SQL 2005 cluster now and add a node later when financially feasible. I haven't tried this in the past and unfortunately don't have any hardware to test with. Does SQL Server 2005..
3/4 Node Clustering - Hi, We plan to install/setup 3-4 node SQL Clustering using Windows 2003 (Enterprise Edition)/SQL2000 (Enterprise Edition) on SAN (EMC) we plan to initially setup/install clustering using two servers (S1& S2) as an ACTIVE/PASSIVE and then later ad...
CLUSTER NAME - Hi , is there any command to display current cluster name through query . Thanks ARR
Using SQL Mail in a cluster - Hello, I'm trying to set up alerts for jobs and backups, using sql mail. Will this work in a clustered enviroment? if so, can you please forward some information on how to get this set up? thanks in advace. Calvin
Need to add additional NIC to SQL Cluster - Hi We recently built a W2K Advanced server, SQL Ent 2000 cluster. Each node of the cluster had 2 NIC ports: 1 NIC was used for Cross over cable Other NIC was used for LAN. All standard build servers in our environment should have 2 NIC connections -.... |
|
You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum
|
|
|
|
|
|
|
FAQ
Search
Profile
Private Messages
Log in
