"Hilary Cotter" wrote:

> You need a column which has a datetime datatype. This column will be the
> basis for determining which change has the latest date time value. With a
> stored procedure resolver you can make descions based on the type of
> conflict, where it occurs and consult some of the base tables in the
> resolution.
>
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
>
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
>
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
>
>
> "David Haas" <DavidHaas@discussions.microsoft.com> wrote in message
> news:93E614D4-1288-448B-A596-BE9DB47E2CD6@microsoft.com...
> >I was going to use this resolver but it does not take each column update
> >into
> > account even tho column tracking is enabled. For example if I change
> > column
> > A on one server and column A and B on the seperate server, and the first
> > change was the later change. When the resolver runs it doesn't keep the
> > change for column B, even tho there was no conflict on that column. Is
> > there
> > a way to correct this that when a conflict does occur it takes the changes
> > on
> > nonconflicting columns when there are conflicts on other columns?
> >
> > Also is there a way when you do a stored procedure resolver to determine
> > if
> > a column had been updated?
>
>