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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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