"Vikas" <Vikas@discussions.microsoft.com> wrote in message
news:1E8D5056-8AFF-4762-95FD-5B4E000F5FE6@microsoft.com...
> Hi all,
>
> I saw the tracking level as Column-Level tracking in the article
> properties of publication and I saw Conflict_type=1 in
> MSMerge_Conflicts_info
> table.
>
> Is there any common in both of these, I doubt the merging changes is
> set to Column-Level tracking and conflict_type says conflict is detected
> at
> the row level.
> is there any inter-link between the setting at article and logging at the
> MSMerge_conflicts_info table?
>
> Iam in confusion, Please help me out.
>
>
> --
> Cheers
> Vikas

"Vikas" <Vikas@discussions.microsoft.com> wrote in message
news:0C54023A-928C-4767-BA83-0D457E5B9BD9@microsoft.com...
> Hi Hilary,
>
> Thank you for your reply, but still iam not clear in this. What i
> understand is
>
> "There is a setting in the article properties and column-level tracking
> and
> it has been logged as row-level in MSMerge_conflicts_info table" is there
> any
> link between properties and logged table?
>
> I may be not clear in explaining the problem.
> --
> Cheers
>
>
>
> "Hilary Cotter" wrote:
>
>> Its column level if different non timestamp columns are updated on both
>> sides between merges with column level tracking. Its a row conflict if
>> 1) two identical pk values are inserted on both sides between syncs
>> 2) a row is deleted on one side but updated on another side between syncs
>>
>> --
>> 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
>>
>>
>>
>> "Vikas" <Vikas@discussions.microsoft.com> wrote in message
>> news:1E8D5056-8AFF-4762-95FD-5B4E000F5FE6@microsoft.com...
>> > Hi all,
>> >
>> > I saw the tracking level as Column-Level tracking in the article
>> > properties of publication and I saw Conflict_type=1 in
>> > MSMerge_Conflicts_info
>> > table.
>> >
>> > Is there any common in both of these, I doubt the merging changes
>> > is
>> > set to Column-Level tracking and conflict_type says conflict is
>> > detected
>> > at
>> > the row level.
>> > is there any inter-link between the setting at article and logging at
>> > the
>> > MSMerge_conflicts_info table?
>> >
>> > Iam in confusion, Please help me out.
>> >
>> >
>> > --
>> > Cheers
>> > Vikas
>>
>>
>>