resolver option and tracking level article options disabled

Hi, we are using SQL2005 merge replication, and have 2 publications that
reference the same article. We are trying to change the tracking level option
for this article, but it is greyed out and disabled, because it knows the
article is in another publication, and it disallows this change. We recreated
this on another server. The option, along with the resolver tab options, get
completely greyed when the 2nd publication is added. Any ideas how to change
the tracking level in this case? Should we use a stored procedure to set this
option? Thanks.
Some publication options are limited by other publications the article is
in. There is no way to change this without dropping all publications and
making these properties consistent in all publications.
Another example of one of these properties is automatic identity range
management.
Hilary Cotter
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
"nkleinjan" <nkleinjan@.discussions.microsoft.com> wrote in message
news:325082EB-74C2-42E9-AFB7-843D23CB53B4@.microsoft.com...
> Hi, we are using SQL2005 merge replication, and have 2 publications that
> reference the same article. We are trying to change the tracking level
> option
> for this article, but it is greyed out and disabled, because it knows the
> article is in another publication, and it disallows this change. We
> recreated
> this on another server. The option, along with the resolver tab options,
> get
> completely greyed when the 2nd publication is added. Any ideas how to
> change
> the tracking level in this case? Should we use a stored procedure to set
> this
> option? Thanks.

Resolver Issues

I'm not able to resolve conflicts using the conflict viewer because I have
timestamp columns in my tables. Can I manually resolve these conflicts by
making the necessary changes to the data?
I'm using filters on my articles and I'm noticing that replication is
changing rows in the table that don't meet my filter clause. Well, all
the data didn't change in the row just the Last_Update_Date and
Last_Update_By columns changed. I have a trigger on my tables that
updates these columns. For some reason my trigger is getting fired.
These two columns get updated so replication thinks it needs to push these
changes along to the subscriber. I end up with conflicts if the
subscriber has also changed these rows.
The first thing to figure out is what is causing teh triggers to fire.
As far as manually doing this, you can. The conflict viewer is just another
application which sits over a set of data. You can easily do this yourself.
You can freely read/write to the conflict tables if you choose since the
only things which reads from them is the conflict viewer. If you choose,
you can write your own application to replace the conflict viewer in order
to fit it into your environment and tailor it to your needs.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com
|||I figured out my trigger issue.
I appreciate your help.
"Michael Hotek" <mhotek@.nomail.com> wrote in message
news:O4wRnlLKEHA.620@.tk2msftngp13.phx.gbl...
> The first thing to figure out is what is causing teh triggers to fire.
> As far as manually doing this, you can. The conflict viewer is just
another
> application which sits over a set of data. You can easily do this
yourself.
> You can freely read/write to the conflict tables if you choose since the
> only things which reads from them is the conflict viewer. If you choose,
> you can write your own application to replace the conflict viewer in order
> to fit it into your environment and tailor it to your needs.
> --
> Mike
> Principal Mentor
> Solid Quality Learning
> "More than just Training"
> SQL Server MVP
> http://www.solidqualitylearning.com
> http://www.mssqlserver.com
>

Resolver is either missing or Incorrect

Hi all sql guru's

I'm having this problem for a while now and can't find any solid answer on the net for it.

I have 2 server in diffrent location ( +- 1200k's) away from eachother. When the msmerge agent run it return the following error and return the status as successfull with the following error information:

(The colum information specified for the MS SQL Server maximum conflict resolver) Resolver is either missing or incorrect. I've change every single article to "Latest chagne wins". Any suggestion. I happend when the power failed and the server got restarted.

If you are using the maximum conflict resolver, you need to specify which column to look for this max value. Without this information, the resolver does not know how to resolve the conflict. Use the sp_changemergearticle or the UI to set this column up.sql

Resolver is either missing or Incorrect

Hi all sql guru's

I'm having this problem for a while now and can't find any solid answer on the net for it.

I have 2 server in diffrent location ( +- 1200k's) away from eachother. When the msmerge agent run it return the following error and return the status as successfull with the following error information:

(The colum information specified for the MS SQL Server maximum conflict resolver) Resolver is either missing or incorrect. I've change every single article to "Latest chagne wins". Any suggestion. I happend when the power failed and the server got restarted.

If you are using the maximum conflict resolver, you need to specify which column to look for this max value. Without this information, the resolver does not know how to resolve the conflict. Use the sp_changemergearticle or the UI to set this column up.