Merge replication and clustering

Hello:
Does merge replication support clustering?
I'm having some troubles about merge agent "querytimeout" parameter
throught a clustered system, and the hints that are over there about
"increasing timeout", "refreshing indices" and a lot more don't give any
result.
Anyone can help me?
Is anyway supported merge replication over a clustered system?
thanks a lot
Juan
Hi
Yes it does.
Have used some very high volume replication scenarios and they worked well.
The biggest note with Merge replication is that the GUID on the table is the
only value in the WHERE clause for when synchronization happens.
Make sure that field, on every replicated table, has and index on it (most
of the time, it was the PK).
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Juan" <juan@.tata.net> wrote in message
news:%23mHTPnARFHA.3708@.TK2MSFTNGP15.phx.gbl...
> Hello:
> Does merge replication support clustering?
> I'm having some troubles about merge agent "querytimeout" parameter
> throught a clustered system, and the hints that are over there about
> "increasing timeout", "refreshing indices" and a lot more don't give any
> result.
> Anyone can help me?
> Is anyway supported merge replication over a clustered system?
> thanks a lot
> Juan
>
|||Hi
I forgot to add, check for blocking when the rep agent is running. It other
active processes are blocking it due to locks held, it can't do it's work
either. Long running transactions and replication are not friends.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:e4n5DCGRFHA.3336@.TK2MSFTNGP09.phx.gbl...
> Hi
> Yes it does.
> Have used some very high volume replication scenarios and they worked
> well.
> The biggest note with Merge replication is that the GUID on the table is
> the only value in the WHERE clause for when synchronization happens.
> Make sure that field, on every replicated table, has and index on it (most
> of the time, it was the PK).
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Juan" <juan@.tata.net> wrote in message
> news:%23mHTPnARFHA.3708@.TK2MSFTNGP15.phx.gbl...
>