4 Node cluster

#41

I want to setup A/A SQL 2k and 2k5 virtual servers on a 4 node OS cluster.
Don't know if they can coexist on same nodes.

"Justin Rich" wrote:

Quote:

Wouldnt that just be 2 x 2 node clusters?

why would you want to make it one big cluster?

"MK" <MK (AT) discussions (DOT) microsoft.com> wrote in message
news:F51F3854-4D2C-4763-8B6F-D2CCD3339DBD (AT) microsoft (DOT) com...
We have mix of both SQL 2000 and 2005 enviroments. The push is to
consolidate.

On 4 node windows 2003 64 bit cluster: Is it possible to host on 2 nodes -
SQL 2000 A/A Virtual server and on 3rd and 4th node SQL 2005 A/A vuirtual
server?

All virtual servers will have have there own database drives. MSDTC will
be
in its own group containing IP and drive for MSDTC logs.

Do you see any issues? suggestions plz.

#42

Binaries are local on each node and separate for each instance. The
installer takes care of writing binaries to each node during install or
reinstall. Service Packs are part-cluster aware and part unaware, depending
on whether the components they are updating install local or cluster-wide.
For Example, SQL Engine updates are cluster-wide, SQL 2005 client tools are
local node only.

If MSDCT throughput is a concern, make it a separate instance on isolated
disks and put it on the least-used node.

Be very careful on your failover order.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

"MK" <MK (AT) discussions (DOT) microsoft.com> wrote

Quote:

Sounds good.

Now we have virtual instance running on each of the 4 nodes. With one copy
of MSDTC resource running any concerns with it servicing diferent SQL
versions?Can you provide sone insight on how SQL binaries are placed in
A/A?
If an application is not cluster aware can we have default (single)
instance
on a cluster node? and if so, any conflict with already installed
binaries?

MK

"Geoff N. Hiten" wrote:

Yes. This can be done.

SQL 2000 will live on Win2003 x64.

SQL 2005 and SQL 2000 can live in a mixed cluster.

Here is the official word on mixed-mode cluster support for both 32-64
bit
and SQL 2000-SQL 2005 combinations.
http://support.microsoft.com/kb/327518/en-us

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

"MK" <MK (AT) discussions (DOT) microsoft.com> wrote in message
news:F51F3854-4D2C-4763-8B6F-D2CCD3339DBD (AT) microsoft (DOT) com...
We have mix of both SQL 2000 and 2005 enviroments. The push is to
consolidate.

On 4 node windows 2003 64 bit cluster: Is it possible to host on 2
nodes -
SQL 2000 A/A Virtual server and on 3rd and 4th node SQL 2005 A/A
vuirtual
server?

All virtual servers will have have there own database drives. MSDTC
will
be
in its own group containing IP and drive for MSDTC logs.

Do you see any issues? suggestions plz.

#43

Binaries are local on each node and separate for each instance. The
installer takes care of writing binaries to each node during install or
reinstall. Service Packs are part-cluster aware and part unaware, depending
on whether the components they are updating install local or cluster-wide.
For Example, SQL Engine updates are cluster-wide, SQL 2005 client tools are
local node only.

If MSDCT throughput is a concern, make it a separate instance on isolated
disks and put it on the least-used node.

Be very careful on your failover order.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

"MK" <MK (AT) discussions (DOT) microsoft.com> wrote

Quote:

Sounds good.

Now we have virtual instance running on each of the 4 nodes. With one copy
of MSDTC resource running any concerns with it servicing diferent SQL
versions?Can you provide sone insight on how SQL binaries are placed in
A/A?
If an application is not cluster aware can we have default (single)
instance
on a cluster node? and if so, any conflict with already installed
binaries?

MK

"Geoff N. Hiten" wrote:

Yes. This can be done.

SQL 2000 will live on Win2003 x64.

SQL 2005 and SQL 2000 can live in a mixed cluster.

Here is the official word on mixed-mode cluster support for both 32-64
bit
and SQL 2000-SQL 2005 combinations.
http://support.microsoft.com/kb/327518/en-us

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

"MK" <MK (AT) discussions (DOT) microsoft.com> wrote in message
news:F51F3854-4D2C-4763-8B6F-D2CCD3339DBD (AT) microsoft (DOT) com...
We have mix of both SQL 2000 and 2005 enviroments. The push is to
consolidate.

On 4 node windows 2003 64 bit cluster: Is it possible to host on 2
nodes -
SQL 2000 A/A Virtual server and on 3rd and 4th node SQL 2005 A/A
vuirtual
server?

All virtual servers will have have there own database drives. MSDTC
will
be
in its own group containing IP and drive for MSDTC logs.

Do you see any issues? suggestions plz.

#44

Binaries are local on each node and separate for each instance. The
installer takes care of writing binaries to each node during install or
reinstall. Service Packs are part-cluster aware and part unaware, depending
on whether the components they are updating install local or cluster-wide.
For Example, SQL Engine updates are cluster-wide, SQL 2005 client tools are
local node only.

If MSDCT throughput is a concern, make it a separate instance on isolated
disks and put it on the least-used node.

Be very careful on your failover order.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

"MK" <MK (AT) discussions (DOT) microsoft.com> wrote

Quote:

Sounds good.

Now we have virtual instance running on each of the 4 nodes. With one copy
of MSDTC resource running any concerns with it servicing diferent SQL
versions?Can you provide sone insight on how SQL binaries are placed in
A/A?
If an application is not cluster aware can we have default (single)
instance
on a cluster node? and if so, any conflict with already installed
binaries?

MK

"Geoff N. Hiten" wrote:

Yes. This can be done.

SQL 2000 will live on Win2003 x64.

SQL 2005 and SQL 2000 can live in a mixed cluster.

Here is the official word on mixed-mode cluster support for both 32-64
bit
and SQL 2000-SQL 2005 combinations.
http://support.microsoft.com/kb/327518/en-us

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

"MK" <MK (AT) discussions (DOT) microsoft.com> wrote in message
news:F51F3854-4D2C-4763-8B6F-D2CCD3339DBD (AT) microsoft (DOT) com...
We have mix of both SQL 2000 and 2005 enviroments. The push is to
consolidate.

On 4 node windows 2003 64 bit cluster: Is it possible to host on 2
nodes -
SQL 2000 A/A Virtual server and on 3rd and 4th node SQL 2005 A/A
vuirtual
server?

All virtual servers will have have there own database drives. MSDTC
will
be
in its own group containing IP and drive for MSDTC logs.

Do you see any issues? suggestions plz.

#45

Binaries are local on each node and separate for each instance. The
installer takes care of writing binaries to each node during install or
reinstall. Service Packs are part-cluster aware and part unaware, depending
on whether the components they are updating install local or cluster-wide.
For Example, SQL Engine updates are cluster-wide, SQL 2005 client tools are
local node only.

If MSDCT throughput is a concern, make it a separate instance on isolated
disks and put it on the least-used node.

Be very careful on your failover order.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

"MK" <MK (AT) discussions (DOT) microsoft.com> wrote

Quote:

Sounds good.

Now we have virtual instance running on each of the 4 nodes. With one copy
of MSDTC resource running any concerns with it servicing diferent SQL
versions?Can you provide sone insight on how SQL binaries are placed in
A/A?
If an application is not cluster aware can we have default (single)
instance
on a cluster node? and if so, any conflict with already installed
binaries?

MK

"Geoff N. Hiten" wrote:

Yes. This can be done.

SQL 2000 will live on Win2003 x64.

SQL 2005 and SQL 2000 can live in a mixed cluster.

Here is the official word on mixed-mode cluster support for both 32-64
bit
and SQL 2000-SQL 2005 combinations.
http://support.microsoft.com/kb/327518/en-us

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

"MK" <MK (AT) discussions (DOT) microsoft.com> wrote in message
news:F51F3854-4D2C-4763-8B6F-D2CCD3339DBD (AT) microsoft (DOT) com...
We have mix of both SQL 2000 and 2005 enviroments. The push is to
consolidate.

On 4 node windows 2003 64 bit cluster: Is it possible to host on 2
nodes -
SQL 2000 A/A Virtual server and on 3rd and 4th node SQL 2005 A/A
vuirtual
server?

All virtual servers will have have there own database drives. MSDTC
will
be
in its own group containing IP and drive for MSDTC logs.

Do you see any issues? suggestions plz.

#46

Binaries are local on each node and separate for each instance. The
installer takes care of writing binaries to each node during install or
reinstall. Service Packs are part-cluster aware and part unaware, depending
on whether the components they are updating install local or cluster-wide.
For Example, SQL Engine updates are cluster-wide, SQL 2005 client tools are
local node only.

If MSDCT throughput is a concern, make it a separate instance on isolated
disks and put it on the least-used node.

Be very careful on your failover order.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

"MK" <MK (AT) discussions (DOT) microsoft.com> wrote

Quote:

Sounds good.

Now we have virtual instance running on each of the 4 nodes. With one copy
of MSDTC resource running any concerns with it servicing diferent SQL
versions?Can you provide sone insight on how SQL binaries are placed in
A/A?
If an application is not cluster aware can we have default (single)
instance
on a cluster node? and if so, any conflict with already installed
binaries?

MK

"Geoff N. Hiten" wrote:

Yes. This can be done.

SQL 2000 will live on Win2003 x64.

SQL 2005 and SQL 2000 can live in a mixed cluster.

Here is the official word on mixed-mode cluster support for both 32-64
bit
and SQL 2000-SQL 2005 combinations.
http://support.microsoft.com/kb/327518/en-us

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

"MK" <MK (AT) discussions (DOT) microsoft.com> wrote in message
news:F51F3854-4D2C-4763-8B6F-D2CCD3339DBD (AT) microsoft (DOT) com...
We have mix of both SQL 2000 and 2005 enviroments. The push is to
consolidate.

On 4 node windows 2003 64 bit cluster: Is it possible to host on 2
nodes -
SQL 2000 A/A Virtual server and on 3rd and 4th node SQL 2005 A/A
vuirtual
server?

All virtual servers will have have there own database drives. MSDTC
will
be
in its own group containing IP and drive for MSDTC logs.

Do you see any issues? suggestions plz.

#47

Binaries are local on each node and separate for each instance. The
installer takes care of writing binaries to each node during install or
reinstall. Service Packs are part-cluster aware and part unaware, depending
on whether the components they are updating install local or cluster-wide.
For Example, SQL Engine updates are cluster-wide, SQL 2005 client tools are
local node only.

If MSDCT throughput is a concern, make it a separate instance on isolated
disks and put it on the least-used node.

Be very careful on your failover order.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

"MK" <MK (AT) discussions (DOT) microsoft.com> wrote

Quote:

Sounds good.

Now we have virtual instance running on each of the 4 nodes. With one copy
of MSDTC resource running any concerns with it servicing diferent SQL
versions?Can you provide sone insight on how SQL binaries are placed in
A/A?
If an application is not cluster aware can we have default (single)
instance
on a cluster node? and if so, any conflict with already installed
binaries?

MK

"Geoff N. Hiten" wrote:

Yes. This can be done.

SQL 2000 will live on Win2003 x64.

SQL 2005 and SQL 2000 can live in a mixed cluster.

Here is the official word on mixed-mode cluster support for both 32-64
bit
and SQL 2000-SQL 2005 combinations.
http://support.microsoft.com/kb/327518/en-us

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

"MK" <MK (AT) discussions (DOT) microsoft.com> wrote in message
news:F51F3854-4D2C-4763-8B6F-D2CCD3339DBD (AT) microsoft (DOT) com...
We have mix of both SQL 2000 and 2005 enviroments. The push is to
consolidate.

On 4 node windows 2003 64 bit cluster: Is it possible to host on 2
nodes -
SQL 2000 A/A Virtual server and on 3rd and 4th node SQL 2005 A/A
vuirtual
server?

All virtual servers will have have there own database drives. MSDTC
will
be
in its own group containing IP and drive for MSDTC logs.

Do you see any issues? suggestions plz.

#48

Binaries are local on each node and separate for each instance. The
installer takes care of writing binaries to each node during install or
reinstall. Service Packs are part-cluster aware and part unaware, depending
on whether the components they are updating install local or cluster-wide.
For Example, SQL Engine updates are cluster-wide, SQL 2005 client tools are
local node only.

If MSDCT throughput is a concern, make it a separate instance on isolated
disks and put it on the least-used node.

Be very careful on your failover order.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

"MK" <MK (AT) discussions (DOT) microsoft.com> wrote

Quote:

Sounds good.

Now we have virtual instance running on each of the 4 nodes. With one copy
of MSDTC resource running any concerns with it servicing diferent SQL
versions?Can you provide sone insight on how SQL binaries are placed in
A/A?
If an application is not cluster aware can we have default (single)
instance
on a cluster node? and if so, any conflict with already installed
binaries?

MK

"Geoff N. Hiten" wrote:

Yes. This can be done.

SQL 2000 will live on Win2003 x64.

SQL 2005 and SQL 2000 can live in a mixed cluster.

Here is the official word on mixed-mode cluster support for both 32-64
bit
and SQL 2000-SQL 2005 combinations.
http://support.microsoft.com/kb/327518/en-us

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

"MK" <MK (AT) discussions (DOT) microsoft.com> wrote in message
news:F51F3854-4D2C-4763-8B6F-D2CCD3339DBD (AT) microsoft (DOT) com...
We have mix of both SQL 2000 and 2005 enviroments. The push is to
consolidate.

On 4 node windows 2003 64 bit cluster: Is it possible to host on 2
nodes -
SQL 2000 A/A Virtual server and on 3rd and 4th node SQL 2005 A/A
vuirtual
server?

All virtual servers will have have there own database drives. MSDTC
will
be
in its own group containing IP and drive for MSDTC logs.

Do you see any issues? suggestions plz.

#49

Binaries are local on each node and separate for each instance. The
installer takes care of writing binaries to each node during install or
reinstall. Service Packs are part-cluster aware and part unaware, depending
on whether the components they are updating install local or cluster-wide.
For Example, SQL Engine updates are cluster-wide, SQL 2005 client tools are
local node only.

If MSDCT throughput is a concern, make it a separate instance on isolated
disks and put it on the least-used node.

Be very careful on your failover order.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

"MK" <MK (AT) discussions (DOT) microsoft.com> wrote

Quote:

Sounds good.

Now we have virtual instance running on each of the 4 nodes. With one copy
of MSDTC resource running any concerns with it servicing diferent SQL
versions?Can you provide sone insight on how SQL binaries are placed in
A/A?
If an application is not cluster aware can we have default (single)
instance
on a cluster node? and if so, any conflict with already installed
binaries?

MK

"Geoff N. Hiten" wrote:

Yes. This can be done.

SQL 2000 will live on Win2003 x64.

SQL 2005 and SQL 2000 can live in a mixed cluster.

Here is the official word on mixed-mode cluster support for both 32-64
bit
and SQL 2000-SQL 2005 combinations.
http://support.microsoft.com/kb/327518/en-us

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

"MK" <MK (AT) discussions (DOT) microsoft.com> wrote in message
news:F51F3854-4D2C-4763-8B6F-D2CCD3339DBD (AT) microsoft (DOT) com...
We have mix of both SQL 2000 and 2005 enviroments. The push is to
consolidate.

On 4 node windows 2003 64 bit cluster: Is it possible to host on 2
nodes -
SQL 2000 A/A Virtual server and on 3rd and 4th node SQL 2005 A/A
vuirtual
server?

All virtual servers will have have there own database drives. MSDTC
will
be
in its own group containing IP and drive for MSDTC logs.

Do you see any issues? suggestions plz.

#50

Binaries are local on each node and separate for each instance. The
installer takes care of writing binaries to each node during install or
reinstall. Service Packs are part-cluster aware and part unaware, depending
on whether the components they are updating install local or cluster-wide.
For Example, SQL Engine updates are cluster-wide, SQL 2005 client tools are
local node only.

If MSDCT throughput is a concern, make it a separate instance on isolated
disks and put it on the least-used node.

Be very careful on your failover order.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

"MK" <MK (AT) discussions (DOT) microsoft.com> wrote

Quote:

Sounds good.

Now we have virtual instance running on each of the 4 nodes. With one copy
of MSDTC resource running any concerns with it servicing diferent SQL
versions?Can you provide sone insight on how SQL binaries are placed in
A/A?
If an application is not cluster aware can we have default (single)
instance
on a cluster node? and if so, any conflict with already installed
binaries?

MK

"Geoff N. Hiten" wrote:

Yes. This can be done.

SQL 2000 will live on Win2003 x64.

SQL 2005 and SQL 2000 can live in a mixed cluster.

Here is the official word on mixed-mode cluster support for both 32-64
bit
and SQL 2000-SQL 2005 combinations.
http://support.microsoft.com/kb/327518/en-us

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

"MK" <MK (AT) discussions (DOT) microsoft.com> wrote in message
news:F51F3854-4D2C-4763-8B6F-D2CCD3339DBD (AT) microsoft (DOT) com...
We have mix of both SQL 2000 and 2005 enviroments. The push is to
consolidate.

On 4 node windows 2003 64 bit cluster: Is it possible to host on 2
nodes -
SQL 2000 A/A Virtual server and on 3rd and 4th node SQL 2005 A/A
vuirtual
server?

All virtual servers will have have there own database drives. MSDTC
will
be
in its own group containing IP and drive for MSDTC logs.

Do you see any issues? suggestions plz.