Ah, yes, that may even be the most trivial point to start...

Tank your for the feedback.

I did a good deed today 😀

Regarding cursors: In many cases cursors can be and should be avoided.

SSC has got a couple of good article...

Did you try dtcping and dtctester?

http://blogs.msdn.com/b/distributedservices/archive/2008/11/12/troubleshooting-msdtc-issues-with-the-dtcping-tool.aspx

Did someone alter DNS settings, firewall stuff ?

FYI a couple of MS refs that might be helpfull

- http://support.microsoft.com/kb/899115

- http://support.microsoft.com/kb/900216

- http://support.microsoft.com/kb/919034

- http://technet.microsoft.com/en-us/library/aa997579%28EXCHG.80%29.aspx

That's a prosperous observation :crazy:

Other Q may...

C:\WINDOWS\Cluster\cluster.log

chances are you we reading my previous reply at the time I edited it.

can you provide OS info ?

Clustering is one of the things that has been "enhanced" vastly with the differen os versions

Did you have a look in the cluster service log...

yet another alternative ... raise an error that is being captured by sqlagent.

http://www.sqlservercentral.com/scripts/Miscellaneous/31032/

If you're not comfortable with the sqlengine you are using, don't go for the service broker solution;

If it...

GSquared (3/29/2011)

If your actual data is much larger than this, you might get a performance improvement by adding a piece to the Where clause that limits it to only updating...

that's what an outer join is all about.

In your case I would use a left join. It will return NULLS for its column values for the non-matching rows

I see...

there must be some trigger / notification service capturing your action and reverting it.

did the provided script match your question ?

Took a shot. 😉

First shot:

( created a SSC_LVL80 db to mimic sql2000 behaviour )

Is the "one"...