MSDTC

#41

It sounds like a case of benign neglect. I find this happens in a lot of
organizations where there is nobody that really knows database technology
that is tasked full-time with keeping stuff like this from happening. Then
again, I have seen it in some $20 Billion corporations, at least the "Room
of Blame".

As Tom said, you might suggest finding a local SQL professional that has no
political axe to grind. You might want to call Microsoft and get them to
refer a local Gold Certified partner. It won't be cheap, but it may be the
best money you ever spent on the system.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

"Paul" <Paul (AT) discussions (DOT) microsoft.com> wrote

Quote:

Thanks Tom,

I'm responsible for the servers but I am not a SQL administrator so I'm a
little unsure what the MSDTC actually does. We are having a meeting
tomorrow
which is going to discuss the poor performance of the SQL server, hence
the
reason why I have posted the question.

The meeting is going to go along the lines of everyone blaming each others
area of responsibility, you know the ype of meeting that goes like, the
network team say 'their is nothing wrong with the network, it's really
fast,
it must be the server. The server team say 'there is nothing wrong with
the
server,event viewer is clean, it must be the application'. Finally the
developers say well the application works well on the dev server' and
round
and round we will go.

It is a two node cluster running 2005 SQL fully patched, it only has one
instance of SQL with no replication. There is only one database on the
sever
which is accessed by about 5 folk at the moment. We do not want to add
more
db's or users until we can try to find out what is going on. I have tried
performance monitors but they show the databases are doing nothing above
20%
at any time.

Any tools or tricks to help would be much appreciated

"Tom Moreau" wrote:

If you don't have many distributed transactions, then MSDTC usually
resides
within the cluster group. However, if you have many distributed
transactions, then you'll want a separate group - with its own disk and
IP.

If this SQL Server is using a backup from a SQL 2000 database, be sure to
update statistics with FULLSCAN. That could be why you are getting
performance problems.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau

"Paul" <Paul (AT) discussions (DOT) microsoft.com> wrote in message
news:FA66F404-AFC0-4827-8AEA-D4E53D8C4689 (AT) microsoft (DOT) com...
Hi,

I have built a 2005 two node sql cluster and we are seeing very poor
client
access speeds. Clearly there could be a zillion reasons for this and I am
trying to narrow them down.

My question is about location of the MSDTC. I currently have the MSDTC
located on the shared disks that also holds the databases, is this
acceptable
or should it be installed on it's own shared disks?

Thanks

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

MSDTC

microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering

Re: MSDTC - 04-28-2008 , 07:12 PM