Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Clustering / July 2009

Tip: Looking for answers? Try searching our database.

SQL 2008 Installation

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
John - 29 Jun 2009 18:24 GMT
Hello Everyone,

I'm trying to setup a 2 node SQL 2008 failover cluster in windows 2008 (2
instances).

After reading some documentation, I'm confused about the right path to follow.
I read that are 2 installation methods, Integrated and Advanced.

When I start the DVD I select "Installation" and I have the option "New SQL
Server failover cluster installation".???!!!

If I go to "Advanced" menu, I have "advanced cluster preparation" and
"Advanced cluster completion"??!!

What should I use? Should I run advanced cluster preparation" on both nodes
an them "Advanced cluster completion" on both nodes as well???!!!

Can anyone point me the right direction to start with?

Another question is related with having SQL 2008 in a cluster where SQL 2005
is already installed, is this supported? What precautions should I have in a
scenario like this one?

At last, Windows 2008 supports multiple instances of MSDTC. Assuming the SQL
2008 and SQL 2005 in a 2 node failover cluster, what is the right way to
setup MSDTC? Should I create a separate cluster group for MSDTC for each
instance of SQL? Or should I integrate a separate MSDTC cluster reasource in
each SQL cluster group??

Thank you for your time.
Geoff N. Hiten - 29 Jun 2009 18:40 GMT
Advanced is for sysprepped installations that will be duplicated many times.

You need to start with Integrted installation.

Before you start, you need to download and run SQL 2008 SP1.  This will
patch the installation script, which has some cluster-related bugs in the
RTM version.  You will still need to apply SP1 after the regular
installation, since the "pre-patch" only fixes the install script.

Here is the official support policy for mixed version clusters:
http://support.microsoft.com/kb/327518

Here are my thoughts on MSDTC and Windows 2008 clustering.
http://weblogs.sqlteam.com/geoffh/archive/2008/07/31/DTC-configuration-for-Windo
ws-2008-SQL-2005-Clusters.aspx


Hope this helps

Signature

Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP

> Hello Everyone,
>
[quoted text clipped - 33 lines]
>
> Thank you for your time.
John - 29 Jun 2009 21:55 GMT
Hi Geoff and thank you for your response.

Okay, I read your article, if I understand your thoughts correctly:

- MSDTC should be in each Cluster group for each instance of SQL (does this
apply to both SQL 2005 and 2008 right?).
-MSDTC should use the VS name and IP address that was used in that Cluster
group (I mean, you can associate to the networkname and ipaddress that's
being used to SQL server as long as you don't associate with SQL server
resources, right?)

To install SQL 2008, I'm following the KB 955392 to slipstream SP1 and
Update the SQL Server 2008 Setup support files.

You say that I need to start with integrated installation? What option is
that? "Installation" menu or Advanced menu? Do I need to run in both nodes or
just one? In SQL 2005 I needed to create a Cluster group with at least one
disk resource in it, is this still true for SQL 2008?

Thank you for your time and patience :)

> Advanced is for sysprepped installations that will be duplicated many times.
>
[quoted text clipped - 50 lines]
> >
> > Thank you for your time.

-----------------------------------------------------------------------------
Less Spam Better enjoyable experience
Visit : news://spacesst.com
Geoff N. Hiten - 29 Jun 2009 22:14 GMT
Inline.

> Hi Geoff and thank you for your response.
>
[quoted text clipped - 3 lines]
> this
> apply to both SQL 2005 and 2008 right?).
Yes.  I wrote that post before SQL 2008, but the same thought process and
rules apply.

> -MSDTC should use the VS name and IP address that was used in that Cluster
> group (I mean, you can associate to the networkname and ipaddress that's
> being used to SQL server as long as you don't associate with SQL server
> resources, right?)

Exactly.  This is to prevent problems during subsequent SQL Updates.

> To install SQL 2008, I'm following the KB 955392 to slipstream SP1 and
> Update the SQL Server 2008 Setup support files.

You can slipstream or pre-patch.  Your choice.
> You say that I need to start with integrated installation? What option is
> that? "Installation" menu or Advanced menu? Do I need to run in both nodes
> or
> just one? In SQL 2005 I needed to create a Cluster group with at least one
> disk resource in it, is this still true for SQL 2008?

You start off by building the "base" node.  After that you add to the
existing SQL cluster.  Very similar to how yoo build a cluster in the first
place.

> Thank you for your time and patience :)

You are welcome.

>> Advanced is for sysprepped installations that will be duplicated many
>> times.
[quoted text clipped - 57 lines]
>> >
>> > Thank you for your time.
John - 30 Jun 2009 09:45 GMT
Okay, thanks, I'll give it a try and post the results.
Thank you for your help.

> Inline.
>
[quoted text clipped - 94 lines]
> >> >
> >> > Thank you for your time.
John - 14 Jul 2009 14:26 GMT
Hi Geoff,
Almost done :)
I've one more question if you don't mind.

The MSDTC is assigned to my cluster name and IPAddress, but after some
additional reading, I read that in some scenarios the DTC Disk resource is
configured outside of the SQL Resource group??!!!!

My DTC configuration is using the Network name and ip address of the SQL
cluster, and I assigned a Disk resource that is also inside the same SQL
Resource Group, should I place the MSDTC Disk resource in a dedicated
Resource group? If yes, what are the advantages?

Thank you again.

> Okay, thanks, I'll give it a try and post the results.
> Thank you for your help.
[quoted text clipped - 97 lines]
> > >> >
> > >> > Thank you for your time.
Geoff N. Hiten - 14 Jul 2009 15:44 GMT
That is a valid scenario.  Personally, I prefer having the DTC resource
inside the SQL Application or Service.  That way there is always a DTC
resource local to the instance.  Thta cuts down on unnecessary inter-node
traffic.

The advantage of a dedicated MSDTC resource is you can put it on a more
lightly loaded node in a multi-node cluster.  That is only important if
there is a very large DTC load.

Signature

Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP

> Hi Geoff,
> Almost done :)
[quoted text clipped - 135 lines]
>> > >> >
>> > >> > Thank you for your time.
John - 15 Jul 2009 02:46 GMT
Ok Great,

But in a cluster with more than one SQL instance makes sence to have one
MSDTC per SQL Cluster Instance, or have only one MSDTC in a dedicated
resource?

Thank you.

> That is a valid scenario.  Personally, I prefer having the DTC resource
> inside the SQL Application or Service.  That way there is always a DTC
[quoted text clipped - 144 lines]
> >> > >> >
> >> > >> > Thank you for your time.
Geoff N. Hiten - 15 Jul 2009 14:41 GMT
It Depends.

As long as the instance count is less than 2x the node count, ine MSDTC per
Instance is a good setting.  Over that, you will get better resource
management with one MSDTC instance per node.

GNH

> Ok Great,
>
[quoted text clipped - 171 lines]
>> >> > >> >
>> >> > >> > Thank you for your time.
John - 16 Jul 2009 16:25 GMT
Okay,

So, if I understand correctly, in a cluster with 2 nodes

2 instances of SQL 2005 (active in node1)
+
2 Instances of SQL 2008 (active in node2)

In a scenario like this one, the best is to have 4 MSDTC instances, one for
each SQL instance, is this correct?

---------------------------------------------------------------------------
---------------------------------------------------------------------------
---------------------------------------------------------------------------

> It Depends.
>
[quoted text clipped - 179 lines]
> >> >> > >> >
> >> >> > >> > Thank you for your time.
Geoff N. Hiten - 16 Jul 2009 17:25 GMT
That is one valid configuration, especially if you plan to add nodes later.
I have no problems with that option.

Signature

Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP

> Okay,
>
[quoted text clipped - 219 lines]
>> >> >> > >> >
>> >> >> > >> > Thank you for your time.
John - 16 Jul 2009 21:48 GMT
I was thinking about having those 4 SQL instances in both nodes, do you think
that is a bad option?

SQL 2005 will have 2 instances, one PROD and one DEV, the same apply to SQL
2008.

Of course if one node fails the other must be able to do the job for the 4
SQL instances... Perhaps I'm asking to much of it?

> That is one valid configuration, especially if you plan to add nodes later.
> I have no problems with that option.
[quoted text clipped - 222 lines]
> >> >> >> > >> >
> >> >> >> > >> > Thank you for your time.
John - 16 Jul 2009 21:52 GMT
And also to the 4 MSDTC instances....

> I was thinking about having those 4 SQL instances in both nodes, do you think
> that is a bad option?
[quoted text clipped - 231 lines]
> > >> >> >> > >> >
> > >> >> >> > >> > Thank you for your time.
Russ Kaufmann - 15 Jul 2009 19:56 GMT
> That is a valid scenario.  Personally, I prefer having the DTC resource
> inside the SQL Application or Service.  That way there is always a DTC
[quoted text clipped - 4 lines]
> lightly loaded node in a multi-node cluster.  That is only important if
> there is a very large DTC load.

To expand on what Geoff said, with SQL 2008 and Windows 2008, it is also
possible to have multiple MSDTC resources so a separate MSDTC resource can
be used for each SQL instance. As SQL fails over or is moved to another
node, it can bring along its MSDTC friend.

Signature

Russ Kaufmann,
MVP, MCSE: Messaging and Security, MCT, MCITP, MCTS and other stuff

ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp

Russ Kaufmann - 15 Jul 2009 20:00 GMT
>> That is a valid scenario.  Personally, I prefer having the DTC resource
>> inside the SQL Application or Service.  That way there is always a DTC
[quoted text clipped - 9 lines]
> be used for each SQL instance. As SQL fails over or is moved to another
> node, it can bring along its MSDTC friend.

Sorry, I should have read the entire thread first. Geoff already covered it.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2010 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.