Scribd
Upload
9 views

Install Microsoft Distributed Transaction Coordinator (MSDTC)

Uploaded by

Nikolaos Tsinganos
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
9 views

Install Microsoft Distributed Transaction Coordinator (MSDTC)

Uploaded by

Nikolaos Tsinganos
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Verify that antivirus software isn't installed on your WSFC cluster.

For more
information, see the Microsoft Knowledge Base article, Antivirus software may
cause problems with cluster services .
To create a failover cluster, you must be a local administrator with permissions
to log in as a service, and to act as part of the operating system on all nodes of
the failover cluster instance.
**Verify that you have disabled NetBIOS for all private network cards** before
beginning SQL Server Setup .
Even though SQL Server supports both Named Pipes and TCP/IP Sockets over
TCP/IP within a cluster, we recommend that you use TCP/IP Sockets in a
clustered configuration.
The Remote Registry service must be up and running.
Remote Administration must be enabled.
SQL Server Enterprise support failover clusters with up to 16 nodes. SQL Server
Business Intelligence and SQL Server Standard supports two-node failover
clusters.
WSFC must be able to verify that the failover clustered instance is running by
using the IsAlive check. This requires connecting to the server by using a trusted
connection. By default, the account that runs the cluster service isn't configured
as an administrator on nodes in the cluster, and **the BUILTIN\Administrators group
doesn't have permission to log into SQL Server.** These settings change only if you
change permissions on the cluster nodes.

Configure Domain Name Service (DNS) or Windows Internet Name Service


(WINS). A DNS server or WINS server must be running in the environment where
your SQL Server failover cluster will be installed. SQL Server Setup requires
dynamic domain name service registration of the SQL Server IP interface virtual
reference. DNS server configuration should allow cluster nodes to dynamically
register an online IP address map to Network Name. If the dynamic registration
can't be completed, the Setup fails, and the installation is rolled back. For more
information, see KB947048 (archived link).
Install Microsoft Distributed Transaction
Coordinator (MSDTC)
Before installing SQL Server on a failover cluster, determine whether the Microsoft
Distributed Transaction Coordinator (MSDTC) cluster resource must be created. If
you're installing only the Database Engine, the MSDTC cluster resource isn't
required. If you're installing the Database Engine and SSIS, Workstation
Components, or if you'll use distributed transactions, you must install MSDTC.
MSDTC isn't required for Analysis Services-only instances.
On Windows Server 2008 and later versions, you can install multiple instances of
MSDTC on a single failover cluster. The first instance of MSDTC that is installed will
be the cluster default instance of MSDTC. SQL Server will take advantage of an
instance of MSDTC installed to the SQL Server local cluster resource group by
automatically using the instance of MSDTC. However, individual applications can be
mapped to any instance of MSDTC on the cluster.
The following rules are applied for an instance of MSDTC to be chosen by SQL
Server:
Use MSDTC installed to the local group, else
Use the mapped instance of MSDTC, else
Use the cluster's default instance of MSDTC, else
Use the local machine's installed instance of MSDTC

Important
If the MSDTC instance that is installed to the local cluster group of SQL Server fails,
SQL Server does not automatically attempt to use the default cluster instance or the
local machine instance of MSDTC. You would need to completely remove the failed
instance of MSDTC from the SQL Server group to use another instance of MSDTC.
Likewise, if you create a mapping for SQL Server and the mapped instance of MSDTC
fails, your distributed transactions will also fail. If you want SQL Server to use a
different instance of MSDTC, you must either add an instance of MSDTC to the local
cluster group of the SQL Server or delete the mapping.
Configure Microsoft Distributed Transaction Coordinator
After you install the operating system and configure your cluster, you must configure
MSDTC to work in a cluster by using the Cluster Administrator. Failure to cluster
MSDTC won't block SQL Server Setup, but SQL Server application functionality may
be affected if MSDTC isn't properly configured.

You might also like