Information for Column-Level Merge Replication

Please provide me a column-level merge replication in SQL Server 2005. In the SQL Sever books online, I could able to get very few informaiton about this topic. Please provide me a best practices for using this kind of conflict resolution in Merge-replication.

Provide me a best solution for this problem

Following are my tables structure

Organization (top-level) AddressID -> ID Address

Employee (top-level) AddressID -> ID Address

Organization and employee in this scenario are isolated from each other, in terms of transactions. However, they contain linked data which lives in an Address table. In order to configure logical records in this example, the Address table would be the top-level, and the organization and employee tables would include join filters referencing it. The problem is, Organization and Employee are not really part of a logical record with Address, at least in terms of all three tables. Instead, Address and Organization participate in a logical record. Address and Employee also should be represented with a logical record.

what would be the suggested implementation approach for managing this type of relationship? I don't want to risk situations where conflicts in the employee table disallow updates to the organization table.You can try to get logical record scenario in this case.
I havent tried it myself, will do so shortly. Meanwhile go ahead and give it a try.
Make Address table the base table. Have Organization and Employee Tables join with the Address table in a Logical Record format.

Will post more after I try it out.|||Thanks for your reply. We will try to do that. Please kindly provide the solution if you achieved at your end.|||This cannot be configured with Logical records in the fashion that you desire. The address table has to be the top-level and you are bound to get conflicts in the entire logical record including organization if there was an error in employee table.
You can have logical record on one (address-employee) or the other (address-organization) but not both and address has to be the defined as the top article due to potential conflicts. This is a restriction in logical records.

Indicating the end of replication

Hi,
Is there a way one can tell when the Merge Replication between the
publisher and subscriber is done completely? Because, when replicating
large tables, it does take considerable amount of time, and I want to
somehow ensure that the replication is completed before disconnecting
the subscriber.
I appreciate any help in this regard!
Thanks!
Jane.
Jane,
if you're using the the activeX controls, they have a status event.
You could use the On Success action of the Run agent step of the merge job.
Alternatively you could check the latest record for this agent in
MSmerge_history (if you're not in continuous mode, you should get the
message 'No data needed to be merged.' at some time).
HTH,
Paul Ibison

indexes and merge replication

just putting out a feeler on this since I think I am about to be asked to do
this.
Can I add/remove indexes on replicated tables? If so, will that schema
change replicate to subscribers (sql server 2000 subscribers)?
I have used the sp_repladdcolumn stored procedure. Hopefully there is one
for indexes as well?
any info is appreciated. Thanks.
Thanks Paul. I'll checkout sp_addscriptexec in sql server books online.
I appreciate the direction.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:1d3f01c49a59$3a4fed60$a501280a@.phx.gbl...
> DJC,
> you can use sp_addscriptexec to replicate index changes.
> HTH,
> Paul Ibison
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>