MSSQL & MySQL on the same server?

Hi all,
I was wondering what the PROS & CONS are of running both MSSQL 2000 &
MySQL on the same box? I would think resource contention, such as memory,
would be something to be careful of. But, I'd like to get a broader input
from others out there. Plus I know nothing about MySQL.
Thanks So Much,
Joe DYes they will co-exist peacefully. A more interesting question is why do you
want both.
"Joe D" <jkdriscoll@.qg.com> wrote in message
news:e4vaj6$1adv$1@.sxnews1.qg.com...
> Hi all,
> I was wondering what the PROS & CONS are of running both MSSQL 2000 &
> mysql on the same box? I would think resource contention, such as memory,
> would be something to be careful of. But, I'd like to get a broader input
> from others out there. Plus I know nothing about MySQL.
> Thanks So Much,
> Joe D
>|||Good Question - Same question that I asked. Things like this can happen when
one group in the company does what it wants (in this case go and buys some
3rd party software package) but wants another group (i.e. the IT group) to
make it work on existing servers. If you've been around the business
awhile, you know what I'm talking about.
Thanks for your feedback.
"Steve Dassin" <steve@.nospamrac4sql.net> wrote in message
news:Ohmb2hrfGHA.4464@.TK2MSFTNGP04.phx.gbl...
> Yes they will co-exist peacefully. A more interesting question is why do
> you
> want both.
> "Joe D" <jkdriscoll@.qg.com> wrote in message
> news:e4vaj6$1adv$1@.sxnews1.qg.com...
>

MSSQL & MySQL on the same server?

Hi all,
I was wondering what the PROS & CONS are of running both MSSQL 2000 &
MySQL on the same box? I would think resource contention, such as memory,
would be something to be careful of. But, I'd like to get a broader input
from others out there. Plus I know nothing about MySQL.
Thanks So Much,
Joe DYes they will co-exist peacefully. A more interesting question is why do you
want both.
"Joe D" <jkdriscoll@.qg.com> wrote in message
news:e4vaj6$1adv$1@.sxnews1.qg.com...
> Hi all,
> I was wondering what the PROS & CONS are of running both MSSQL 2000 &
> MySQL on the same box? I would think resource contention, such as memory,
> would be something to be careful of. But, I'd like to get a broader input
> from others out there. Plus I know nothing about MySQL.
> Thanks So Much,
> Joe D
>|||Good Question - Same question that I asked. Things like this can happen when
one group in the company does what it wants (in this case go and buys some
3rd party software package) but wants another group (i.e. the IT group) to
make it work on existing servers. If you've been around the business
awhile, you know what I'm talking about.
Thanks for your feedback.
"Steve Dassin" <steve@.nospamrac4sql.net> wrote in message
news:Ohmb2hrfGHA.4464@.TK2MSFTNGP04.phx.gbl...
> Yes they will co-exist peacefully. A more interesting question is why do
> you
> want both.
> "Joe D" <jkdriscoll@.qg.com> wrote in message
> news:e4vaj6$1adv$1@.sxnews1.qg.com...
>> Hi all,
>> I was wondering what the PROS & CONS are of running both MSSQL 2000 &
>> MySQL on the same box? I would think resource contention, such as memory,
>> would be something to be careful of. But, I'd like to get a broader input
>> from others out there. Plus I know nothing about MySQL.
>> Thanks So Much,
>> Joe D
>

Msg 7404

Can anyone point me to a good resource regarding SQL Server Msg 7404? I've
got a scheduled job that runs a stored procedure that started showing the
following after the last server reboot:
Msg 7404, Sev 16: The server could not load DCOM. [SQLSTATE 42000]
A reboot usually corrects this but I only have a small, weekly window to do
this. Also need to explain to the powers at be why & what this is.
Thanks.
Paul
Hi
Unfortunately I don't think there is a good source, searching Google for
this error doesn't throw up much. You may want to check the SQL Server log
and Windows Event log to try and find out more background to this. What does
the stored procedure do?
John
"Paul" <dbapaul@.noemail.noeamil> wrote in message
news:20201A44-B46F-4F09-89D4-F44DAFB4810F@.microsoft.com...
> Can anyone point me to a good resource regarding SQL Server Msg 7404? I've
> got a scheduled job that runs a stored procedure that started showing the
> following after the last server reboot:
> Msg 7404, Sev 16: The server could not load DCOM. [SQLSTATE 42000]
> A reboot usually corrects this but I only have a small, weekly window to
> do
> this. Also need to explain to the powers at be why & what this is.
> Thanks.
> Paul

Msg 7404

Can anyone point me to a good resource regarding SQL Server Msg 7404? I've
got a scheduled job that runs a stored procedure that started showing the
following after the last server reboot:
Msg 7404, Sev 16: The server could not load DCOM. [SQLSTATE 42000]
A reboot usually corrects this but I only have a small, weekly window to do
this. Also need to explain to the powers at be why & what this is.
Thanks.
PaulHi
Unfortunately I don't think there is a good source, searching Google for
this error doesn't throw up much. You may want to check the SQL Server log
and Windows Event log to try and find out more background to this. What does
the stored procedure do?
John
"Paul" <dbapaul@.noemail.noeamil> wrote in message
news:20201A44-B46F-4F09-89D4-F44DAFB4810F@.microsoft.com...
> Can anyone point me to a good resource regarding SQL Server Msg 7404? I've
> got a scheduled job that runs a stored procedure that started showing the
> following after the last server reboot:
> Msg 7404, Sev 16: The server could not load DCOM. [SQLSTATE 42000]
> A reboot usually corrects this but I only have a small, weekly window to
> do
> this. Also need to explain to the powers at be why & what this is.
> Thanks.
> Paul

Msg 7404

Can anyone point me to a good resource regarding SQL Server Msg 7404? I've
got a scheduled job that runs a stored procedure that started showing the
following after the last server reboot:
Msg 7404, Sev 16: The server could not load DCOM. [SQLSTATE 42000]
A reboot usually corrects this but I only have a small, weekly window to do
this. Also need to explain to the powers at be why & what this is.
Thanks.
PaulHi
Unfortunately I don't think there is a good source, searching Google for
this error doesn't throw up much. You may want to check the SQL Server log
and Windows Event log to try and find out more background to this. What does
the stored procedure do?
John
"Paul" <dbapaul@.noemail.noeamil> wrote in message
news:20201A44-B46F-4F09-89D4-F44DAFB4810F@.microsoft.com...
> Can anyone point me to a good resource regarding SQL Server Msg 7404? I've
> got a scheduled job that runs a stored procedure that started showing the
> following after the last server reboot:
> Msg 7404, Sev 16: The server could not load DCOM. [SQLSTATE 42000]
> A reboot usually corrects this but I only have a small, weekly window to
> do
> this. Also need to explain to the powers at be why & what this is.
> Thanks.
> Paul

MSDTC Resource on Win2003 cluster

I am having trouble to fail over MSDTC Resource group to a second node in a two node cluster. It is running fine on the first node but refuse to start on the second node.
Any help will be greatly appreciated.
Yuhong
yuhong.huo@.yale.edu
I found the solution. Just want post it here in case anybody run into the same problem.
I took the MSDTC Cluster Group offline on the first node and ran msdtc.exe -resetlog command on the second node. And it worked. See article: http://support.microsoft.com/?kbid=243204
Yuhong
|||You may want to check kb article..
http://support.microsoft.com/default...b;EN-US;248025
Van Thothathri
Windows Clustering
High Availability Microsoft Enterprise Server Products
"This posting is provided "AS IS" with no warranties, and confers no
rights."
Use of included script samples, if any, are subject to the terms specified
at http://www.microsoft.com/info/cpyright.htm
"Yuhong Huo" <anonymous@.discussions.microsoft.com> wrote in message
news:EEA345EC-A673-48A9-8E61-2580049D5F14@.microsoft.com...
>I am having trouble to fail over MSDTC Resource group to a second node in a
>two node cluster. It is running fine on the first node but refuse to start
>on the second node.
> Any help will be greatly appreciated.
> Yuhong
> yuhong.huo@.yale.edu

MSDTC Resource in the Cluster Group

Why is it a bad idea to have the MSDTC Resource in the Cluster Group, even if
the MSDTC has its own IP Address and Network Name?
In my planned multiple instance sql cluster, I can see giving up a physical
disk to the Quarum, but another disk to MSTDC as well. Since the MSTDC
doesn't use tons on disk space, can I put it in the same group as the defualt
instance of SQL, again as long has it has its own IP Address and Network
Name?
It's more a matter of usage and availability. If you use it a lot, even
though its small, it takes it toll on the disk. You would never want MSDTC
to take cycles away from what the quorum is trying to use. As for
availability, what happens if you have a resource failure? By default, the
group is afftected. Putting more things in ANY group, affects the group as a
whole. For the Highest Availability, keep everything separate.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:E91F75E1-1006-4062-8BC7-35D94FD3E77F@.microsoft.com...
> Why is it a bad idea to have the MSDTC Resource in the Cluster Group, even
> if
> the MSDTC has its own IP Address and Network Name?
> In my planned multiple instance sql cluster, I can see giving up a
> physical
> disk to the Quarum, but another disk to MSTDC as well. Since the MSTDC
> doesn't use tons on disk space, can I put it in the same group as the
> defualt
> instance of SQL, again as long has it has its own IP Address and Network
> Name?

MSDTC resource in a Cluster

I've read and heard some conflicting information about the best method for
setting up a MSDTC resource in a cluster. I am running MSSQL 2000 SP3a and
Windows 2003. 2 node cluster with currently only once instance of MSSQL
with a great chance of growing.
A few questions I have:
Should the resource be in the cluster group or the virtual server group?
What else does it need, ip address, name...?
If it's not yet being used, is it safe to have it on the quorum drive
(currently 1GB RAID1)?
Has anyone found a white paper specific to Win2k3, MSSQL2k and MSDTC?
Thanks,
Joseph
Hi,
I've found this paper
http://support.microsoft.com/default...b;en-us;301600
It suggests to put MSDTC in its own group with its storage resource(disk).
On other hand if that is not possible you can put it in a group with disk.
Anyway I would mess with quorum drive, so I would put it in a Virtual Server
group.
Danijel
"Joseph" <Joseph@.discussions.microsoft.com> wrote in message
news:OEv$n4M%23EHA.2552@.TK2MSFTNGP09.phx.gbl...
> I've read and heard some conflicting information about the best method for
> setting up a MSDTC resource in a cluster. I am running MSSQL 2000 SP3a
> and
> Windows 2003. 2 node cluster with currently only once instance of MSSQL
> with a great chance of growing.
> A few questions I have:
> Should the resource be in the cluster group or the virtual server group?
> What else does it need, ip address, name...?
> If it's not yet being used, is it safe to have it on the quorum drive
> (currently 1GB RAID1)?
> Has anyone found a white paper specific to Win2k3, MSSQL2k and MSDTC?
> Thanks,
> Joseph
>
|||The official best practice is "put MSDTC in its own group" but to do that
you will need an extra disk, Network Name and IP Address.
Unless you know you will be hitting MSDTC hard, like in a BizTalk
environment for example then leave it in the cluster group. In the event of
an MSDTC failure the Cluster Group will failover to the passive node. The
only "outage" will be for admin's connected to the Virtual Cluster Name in
Cluster Administrator as the resources are re-started on the new node. It
will not affect any other groups.
Alternatively, if MSDTC was in the SQL Group then a failure would cause a
SQL Server outage. If your application is entirely dependant on MSDTC, this
might be fine but its more likely that you wouldn't want that to happen.
You can set MSDTC to not affect the group but then you don't have the
benefit of failover.
In summary, leave MSDTC in the Cluster Group. It makes sense and we support
it
Christian Bolton
Microsoft
"Danijel Novak" <danijel.novak@.snt.si> wrote in message
news:nVfFd.8296$F6.1420730@.news.siol.net...
> Hi,
> I've found this paper
> http://support.microsoft.com/default...b;en-us;301600
> It suggests to put MSDTC in its own group with its storage resource(disk).
> On other hand if that is not possible you can put it in a group with disk.
> Anyway I would mess with quorum drive, so I would put it in a Virtual
> Server group.
> Danijel
> "Joseph" <Joseph@.discussions.microsoft.com> wrote in message
> news:OEv$n4M%23EHA.2552@.TK2MSFTNGP09.phx.gbl...
>

MSDTC Resource Group - Physical Disk and Network Name

Article 301600 (http://support.microsoft.com/?kbid=301600) mentions that
MSDTC should be in its own resource group.
- What is the recommended size for the physical disk that needs to be in
this resource group?
- Is it necessary to add the Network Name resource to DNS?
Thank you.
500 MB (meg) or bigger.
You will need an IP and Network Name for it to be on the wire.
If you are running Windows Sever 2003, be sure to follow 817064 FIRST.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"vkb" <vkb@.discussions.microsoft.com> wrote in message
news:48A5C66D-988B-47A1-B638-DA2FC15AEB9B@.microsoft.com...
> Article 301600 (http://support.microsoft.com/?kbid=301600) mentions that
> MSDTC should be in its own resource group.
> - What is the recommended size for the physical disk that needs to be in
> this resource group?
> - Is it necessary to add the Network Name resource to DNS?
> Thank you.

MsDTc on each node feasibly?

Is there a possibility to create on each node a MSDTC resource (even local on
each server)?
When you talk about a MSDTC resource, I assume you are talking about it as a
cluster resource. There is only one MSDTC resource in a cluster, not one for
each node.
What may be the reason you want it on each node?
Linchi
"Walter" <Walter@.discussions.microsoft.com> wrote in message
news:F712ECF3-D326-4CCC-8BCD-AA2425A6B503@.microsoft.com...
> Is there a possibility to create on each node a MSDTC resource (even local
> on
> each server)?
|||Thanks for the confirmation. The reason is I like to create a DB env.
active/active for our application that needs MsDTc. The first node DB for
the application and the second node for reporting and is a replicata of the
first DB.
Do you have maybe a solution for this?
Many thanks in advance,
Walter
"Linchi Shea" schreef:

> When you talk about a MSDTC resource, I assume you are talking about it as a
> cluster resource. There is only one MSDTC resource in a cluster, not one for
> each node.
> What may be the reason you want it on each node?
> Linchi
> "Walter" <Walter@.discussions.microsoft.com> wrote in message
> news:F712ECF3-D326-4CCC-8BCD-AA2425A6B503@.microsoft.com...
>
>
|||You can have multiple SQL instances on a cluster. You still need only one
instance of MSDTC for the entire cluster. There are several techniques that
will allow you to create the shadow database for reporting. Replication and
Log shipping are the most popular. Each has its own advantages and
disatvantages, so it is important to learn the capabilities of each.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Walter" <Walter@.discussions.microsoft.com> wrote in message
news:7CB2BC93-2B37-471B-BD4B-049A1F71658D@.microsoft.com...[vbcol=seagreen]
> Thanks for the confirmation. The reason is I like to create a DB env.
> active/active for our application that needs MsDTc. The first node DB for
> the application and the second node for reporting and is a replicata of
> the
> first DB.
> Do you have maybe a solution for this?
> Many thanks in advance,
> Walter
> "Linchi Shea" schreef:

msdtc is down

The resource msdtc is down. Every time, it works pretty well , after we restart the servers(node1 and node2). But, about half a hour later, the problem is there. We reintalled msdtc. It didn't work out too. msdtc and sql server is on a cluster. Can anyone help me out?

What has this got to do with SSIS, the title of this forum?

Have you looked at any MS DTC troubleshooting resources?

Have you looked in the event log?

MSDTC in Default Cluster Group

Hi,
Can I put the MSDTC resource in Defaul Cluster Group ? I dont have available
disk to it.
thanks,
Rubens
Yes, you can put it in this group, but this goes against best practices. You
might want to consider unchecking the "affect the group" paramter for this
resource so a failure of this resource does not kill your cluster group.
Regards,
John
"Rubens Luque Sanches Jr." <rubensluque@.yahoo.com.br> wrote in message
news:eQeH1N4HFHA.2784@.TK2MSFTNGP09.phx.gbl...
> Hi,
> Can I put the MSDTC resource in Defaul Cluster Group ? I dont have
available
> disk to it.
> thanks,
> Rubens
>
|||If one node fail,can msdtc resource automatically move to another node?
Could you tell me more information about following line?
You might want to consider unchecking the "affect the group" paramter for
this resource so a failure of this resource does not kill your cluster
group.
"John Toner [MVP]" <jtoner@.DIE.SPAM.DIE.mvps.org> д?:%23i%23CfY$HFHA.588@.TK2MSFTNGP15.phx. gbl...
> Yes, you can put it in this group, but this goes against best practices.
> You
> might want to consider unchecking the "affect the group" paramter for this
> resource so a failure of this resource does not kill your cluster group.
> Regards,
> John
> "Rubens Luque Sanches Jr." <rubensluque@.yahoo.com.br> wrote in message
> news:eQeH1N4HFHA.2784@.TK2MSFTNGP09.phx.gbl...
> available
>
|||Yes, please read through the following KB article for more details about
setting up MSDTC resource in the cluster.
http://support.microsoft.com/kb/301600
Regards,
John
"lv ming tong" <lmt@.taeco.com.diss> wrote in message
news:uTuiBG3IFHA.1304@.TK2MSFTNGP09.phx.gbl...
> If one node fail,can msdtc resource automatically move to another node?
> Could you tell me more information about following line?
> You might want to consider unchecking the "affect the group" paramter for
> this resource so a failure of this resource does not kill your cluster
> group.
>
> "John Toner [MVP]" <jtoner@.DIE.SPAM.DIE.mvps.org>
д?:%23i%23CfY$HFHA.588@.TK2MSFTNGP15.phx. gbl...[vbcol=seagreen]
this
>
|||While SQL Server does not require MS DTC, MS DTC on a cluster is only
supported when clustered and it is recommended to cluster it.
When clustering MS DTC it is preferred to have it in its own group with its
own resources, your second choice should be to put it in the cluster group,
use the quorum disk and create MS DTC its own Network Name and IP Address
resources for your MSDTC resource to use and set that resources properties
not to affect the group.
Here are some KB articles on correctly setting this up:
301600 How to configure Microsoft Distributed Transaction Coordinator on a
http://support.microsoft.com/?id=301600
817064 How to enable network DTC access in Windows Server 2003
http://support.microsoft.com/?id=817064
Also this article which may be of interest:
817065 How To Enable Network COM Access in Windows Server 2003
http://support.microsoft.com/?id=817065
Dave Whitney
SQL Support

MSDTC in Cluster Group

Why is it a bad idea to have the MSDTC Resource in the Cluster Group, even if
the MSDTC has its own IP Address and Network Name?
In my planned multiple instance sql cluster, I can see giving up a physical
disk to the Quarum, but another disk to MSTDC as well. Since the MSTDC
doesn't use tons on disk space, can I put it in the same group as the defualt
instance of SQL, again as long has it has its own IP Address and Network
Name?
The original MS KB posts recommended using the Cluster Group resource;
however, we've found out that it does not work and an instance of SQL Server
can not bind to it unless it's on the same node.
You can put it in the SQL Server Group resource, but it won't work once you
go multi-instanced. At that point, MS recommends that you create a seperate
shared disk resource with its own IP and Network Name resources and cluster
MS DTC as a seperate group. Looks like the coders didn't think through the
implications of the Quorum and coded against it. The SQL Server
developement group did not realize this.
Sincerely,
Anthony Thomas

"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:922FDA87-A645-43C7-8442-BAD97525A3F1@.microsoft.com...
Why is it a bad idea to have the MSDTC Resource in the Cluster Group, even
if
the MSDTC has its own IP Address and Network Name?
In my planned multiple instance sql cluster, I can see giving up a physical
disk to the Quarum, but another disk to MSTDC as well. Since the MSTDC
doesn't use tons on disk space, can I put it in the same group as the
defualt
instance of SQL, again as long has it has its own IP Address and Network
Name?

MSDTC in Cluster Group

Why is it a bad idea to have the MSDTC Resource in the Cluster Group, even if
the MSDTC has its own IP Address and Network Name?
In my planned multiple instance sql cluster, I can see giving up a physical
disk to the Quarum, but another disk to MSTDC as well. Since the MSTDC
doesn't use tons on disk space, can I put it in the same group as the defualt
instance of SQL, again as long has it has its own IP Address and Network
Name?The original MS KB posts recommended using the Cluster Group resource;
however, we've found out that it does not work and an instance of SQL Server
can not bind to it unless it's on the same node.
You can put it in the SQL Server Group resource, but it won't work once you
go multi-instanced. At that point, MS recommends that you create a seperate
shared disk resource with its own IP and Network Name resources and cluster
MS DTC as a seperate group. Looks like the coders didn't think through the
implications of the Quorum and coded against it. The SQL Server
developement group did not realize this.
Sincerely,
Anthony Thomas
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:922FDA87-A645-43C7-8442-BAD97525A3F1@.microsoft.com...
Why is it a bad idea to have the MSDTC Resource in the Cluster Group, even
if
the MSDTC has its own IP Address and Network Name?
In my planned multiple instance sql cluster, I can see giving up a physical
disk to the Quarum, but another disk to MSTDC as well. Since the MSTDC
doesn't use tons on disk space, can I put it in the same group as the
defualt
instance of SQL, again as long has it has its own IP Address and Network
Name?

MSDTC cluster resource

I am configuring a two node SQL cluster and i have 5 physical disk arrays and
i intend to use them in the following order
disk array 1 for quorum
disk array 2 for DATA
disk array 3 for backup
disk array 4 for TempDB
disk array 5 create two partition (1 for Tlog and 2 for MDTC disk resorces)
Will there be any probelm or is there anything wrong with creating two
partitions on the disk array 5 to make available two disk resource for those
two resources i have mentioned above e.g the MSDTC resource and the TLOg
storage . Since i want the MSDTC resource to be in its own resource group.
Please any help will be gladly appreciated.
Slawal
Clustering does not understand partitions, only disks. With that said, array
5 should stay one partition. MSDTC is only 4 MB by default. Are you sure you
will even use MSDTC with SQL? If not, you don't have to install it
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog
"slawal" <slawal@.discussions.microsoft.com> wrote in message
news:4D82411F-5802-4DE7-AF51-62614083B82E@.microsoft.com...
>I am configuring a two node SQL cluster and i have 5 physical disk arrays
>and
> i intend to use them in the following order
> disk array 1 for quorum
> disk array 2 for DATA
> disk array 3 for backup
> disk array 4 for TempDB
> disk array 5 create two partition (1 for Tlog and 2 for MDTC disk
> resorces)
> Will there be any probelm or is there anything wrong with creating two
> partitions on the disk array 5 to make available two disk resource for
> those
> two resources i have mentioned above e.g the MSDTC resource and the TLOg
> storage . Since i want the MSDTC resource to be in its own resource group.
> Please any help will be gladly appreciated.
>
> Slawal
|||While SQL Server does not require MS DTC, MS DTC on a cluster is only
supported when clustered and it is recommended to cluster it.
When clustering MS DTC it is preferred to have it in its own group with its
own resources, This will require your partion to appear as a physical disk
to place the disk in its own group.
Your second choice should be to put it in the cluster group,
use the quorum disk and create MS DTC its own Network Name and IP Address
resources for your MSDTC resource to use and set that resources properties
not to affect the group.
Here are some KB articles on correctly setting this up:
301600 How to configure Microsoft Distributed Transaction Coordinator on a
http://support.microsoft.com/?id=301600
817064 How to enable network DTC access in Windows Server 2003
http://support.microsoft.com/?id=817064
Also this article which may be of interest:
817065 How To Enable Network COM Access in Windows Server 2003
http://support.microsoft.com/?id=817065
Dave Whitney
SQL Support

MSDTC - running but not available - RPC error?

Hi there.
I am having problems with MSDTC on a 2-node clustered server. I currently
have it added as a resource in a group with disk storage, SQL Server, an IP
Address and a Network name. When I look at the status of MSDTC using MSSQL
Enterprise Manager on either node, it seems to be running Ok (after I select
"bring online" in cluster admin).
I have a non-clustered SQL Server from which I'd like to call stored
procedures on my clustered server (hence I need MSDTC running). However, on
running these queries, I am seeing problems like this:
select * from CLUSTER.MyDB.dbo.MyTable --this works fine BUT
BEGIN DISTRIBUTED TRANSACTION
select * from CLUSTER.MyDB.dbo.MyTable
COMMIT TRANSACTION
returns errors like
'MSDTC on server unavailable' and my stored procedure calls return errors
like:
'OLE DB error trace - ITransactionJoin::JoinTransaction returned 0x8004d00a'
I have performed some configuration according to
http://support.microsoft.com/kb/817064
and
http://support.microsoft.com/kb/301600
but to no avail.
Any ideas? We tried using DTCPing to obtain more detailed errors and what we
saw were 'RPC' errors (the cluster was unable to ping the other linked server)
Any help would be appreciated!
P.S: A constraint I have is that I can't assign a new IPAddress for MSDTC...
|||Hello,
Is your MSDTC the one from Windows 2003?
/Patrice
|||Yes - it's 2003 - sorry for leaving this out (I've ust gone a bit dizzy from
trying to fix this!)
"Patrice" wrote:

> Hello,
> Is your MSDTC the one from Windows 2003?
> /Patrice
>
|||Hello,
Is it possible for you to do the following test...
Cound you call your SP after
(a) you bring SQL online only after MSDTC was fully up and running
(b) you (try to) bring SQL online before MSDTC was fully up and
running
It would be interesting to notice that everything is fine with (a), and
that you got an "MSDTC on server unavailable" error message with (b).
If it is the case it will mean that you are experiencing the same
problem than the one I experienced a couple of months ago ;-)
/Patrice
|||Hello "Len",
Are you able to do the test I have proposed? Should I continue to
monitor this topic?
Thanks in advance for your reply.
/Patrice
|||If Patrice's test works you should contact Microsoft Product Support and
request the hotfix associated with this KB article:
883955 Availability of Windows Server 2003 COM 1.5 Rollup Package 3
http://support.microsoft.com/?id=883955
Dave Whitney
SQL Support

MSDTC - Give it a dedicated group or use Cluster Group?

Hello group,
I have been testing out SQL 2005 clusters. I noticed that putting the
"Distributed Transaction Coordinator" resource (i.e., MSDTC) in either
its own cluster resource group or in the default Cluster Group with
the quorum works. The latter would be my preference because it saves
an IP address and a disk.
Which way -- dedicated group or shared cluster group -- is the
generally accepted best practice, though?
Thank you in advance,
J Wolfgang Goerlich
Related Links:
Microsoft Article 301600, How to configure Microsoft Distributed
Transaction Coordinator on a Windows Server 2003 cluster
http://support.microsoft.com/default.aspx?scid=kb;en-us;301600
The only reason to give it its own group is performance.
If you have a high load/use for MSDTC, you should configure it in its own
group, however this will impact available drive letters, as the dedicated
group needs a disk (and IP and net-name). If you decide to give MSDTC its
own group, you must carefully design the rest of your cluster in regards to
the available drive letters.
Most applications do not have a high load on MSDTC, and therefore there is
not need for a seperate group. It is very common to place the MSDTC resource
in the Cluster Group, using the Quorum disk.
rgds,
Edwin.
<jwgoerlich@.gmail.com> wrote in message
news:1173815091.825202.19210@.j27g2000cwj.googlegro ups.com...
> Hello group,
> I have been testing out SQL 2005 clusters. I noticed that putting the
> "Distributed Transaction Coordinator" resource (i.e., MSDTC) in either
> its own cluster resource group or in the default Cluster Group with
> the quorum works. The latter would be my preference because it saves
> an IP address and a disk.
> Which way -- dedicated group or shared cluster group -- is the
> generally accepted best practice, though?
> Thank you in advance,
> J Wolfgang Goerlich
>
> Related Links:
> Microsoft Article 301600, How to configure Microsoft Distributed
> Transaction Coordinator on a Windows Server 2003 cluster
> http://support.microsoft.com/default.aspx?scid=kb;en-us;301600
>
|||Much obliged. What's a good rule of thumb to determine a high load?
Tens of transactions per second? Hundreds or more tps?
On Mar 14, 4:54 am, "Edwin vMierlo"
<EdwinvMie...@.discussions.microsoft.com> wrote:
> The only reason to give it its own group is performance.
> If you have a high load/use for MSDTC, you should configure it in its own
> group, however this will impact available drive letters, as the dedicated
> group needs a disk (and IP and net-name). If you decide to give MSDTC its
> own group, you must carefully design the rest of your cluster in regards to
> the available drive letters.
> Most applications do not have a high load on MSDTC, and therefore there is
> not need for a seperate group. It is very common to place the MSDTC resource
> in the Cluster Group, using the Quorum disk.
> rgds,
> Edwin.
|||A simple test:
Put MSDTC in the quorum group. Establish a distributed transaction with SQL
Server, even with itself using a linked server to itself. Now move the
quorum group to passive node. Try to establish another distributed
transaction.
The result is that you cannot. The reason is that when the quorum goes
offline, the SQL Server DTC handle is destroyed.
The only way to alleviate this is to give the DTC its own dedicated cluster
group.
If you only plan on running a single instance of SQL Server, and this is the
only service you will be establishing distributed transactions with, then
put the MS DTC resource inside the SQL Server group, not the quorum.
The Microsoft articles have been updated to reflect this recommendation.
Sincerely,
Anthony Thomas

<jwgoerlich@.gmail.com> wrote in message
news:1173870206.954497.204520@.e1g2000hsg.googlegro ups.com...[vbcol=seagreen]
> Much obliged. What's a good rule of thumb to determine a high load?
> Tens of transactions per second? Hundreds or more tps?
> On Mar 14, 4:54 am, "Edwin vMierlo"
> <EdwinvMie...@.discussions.microsoft.com> wrote:
own[vbcol=seagreen]
dedicated[vbcol=seagreen]
its[vbcol=seagreen]
to[vbcol=seagreen]
is[vbcol=seagreen]
resource
>
|||Alright, I think I am following your explanation. If the MSDTC is in
the quorum resource group (e.g., the Cluster Group) and that group
goes offline then any DTC transactions will fail.
Now, how would this change if the MSDTC were in its own group (e.g.,
MSDTC Resource)? When the MSDTC Resource goes offline, any
distributed transactions will also fail. I am probably missing
something here. What would this dedicated group gain us, then?
J Wolfgang Goerlich
On Mar 16, 10:39 pm, "Anthony Thomas" <ALTho...@.kc.rr.com> wrote:
> A simple test:
> Put MSDTC in the quorum group. Establish a distributed transaction with SQL
> Server, even with itself using a linked server to itself. Now move the
> quorum group to passive node. Try to establish another distributed
> transaction.
> The result is that you cannot. The reason is that when the quorum goes
> offline, the SQL Server DTC handle is destroyed.
> The only way to alleviate this is to give the DTC its own dedicated cluster
> group.
> If you only plan on running a single instance of SQL Server, and this is the
> only service you will be establishing distributed transactions with, then
> put the MS DTC resource inside the SQL Server group, not the quorum.
> The Microsoft articles have been updated to reflect this recommendation.
> Sincerely,
> Anthony Thomas