If SQL Server cannot connect to a clustered DTC, you will see an error message like the following: This updatated post stems from the blog post “ Creating a Clustered DTC for SQL Server Redux“.Ī sign that you need to use DTC for a given FCI can be found right in the SQL Server error log. To get this done, you really need to script it. Part of this is ensuring that even though DTC is in the group with SQL, it still gets its own name and IP address using the SQL Server name can be problematic.
In fact, the only truly reliable way some of us have found was talked about by my friend and fellow Cluster MVP (also a big SQL guy), Mike Steineke ( blog | Twitter) in a post last week entitled “Clustered DTC and Multiple SQL Instances” where he shows how he had to configure DTC. Having said that, what Cindy wrote doesn’t always work. This way it always lives on the node where the instance is currently running. In my opinion, with W2K8+, you really should create one DTC for each FCI and put it in with the SQL Server instance.
The “definitive” word on the subject for awhile has been both of Cindy Gross’ blog posts ( “Do I need DTC for my SQL Server?” and “How to configure DTC for SQL Server in a Windows 2008 cluster”).
HOW TO PROPERLY INSTALL SQL SERVER 2014 HOW TO
How to Properly Configure DTC for Clustered Instances of SQL Server (Revised)īy: Allan Hirt on Main Distributed Transaction Coordinator, DTC, Featured, PowerShell, SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, Windows Server 2008 R2, Windows Server 2012Ĭonfiguring the Microsoft Distributed Transaction Coordinator (DTC) for clustered SQL Server instances (FCIs) with Windows Server 2008 and later has been a confusing topic for many.
0 kommentar(er)
