Post reply

Replication Conflict

  • June 9, 2005 at 9:58 am

    #102582

    Hey All,

    I'm trying to create a merge replication with a push subscription between two different db versions. The new version has a table with an additional column and I receive this error when attempting to replicate:

    "The schema definition of base table 'dbo'.'data' at the Subscriber does not match the table in the Publisher database. Re-establish the subscription after recreating the base table to match the table at the Publisher."

    Unfortunately, there is no way to alter the source table to add the new column. I know there is a way to ignore columns on the source db when creating the publication, is there a way to ignore destination columns? Is there another solution?

     

  • June 10, 2005 at 5:28 am

    #564538

    I've never tried using replication when the publisher and subscriber had different table schemas.  However, you may be able to do it this way.

    You may want to try creating the PUBLICATION with filtering.

    Publication Properties:

    Define data filters

    Select "Vertically, by filtering the columns of the published data".  Select the columns to publish which match the subscriber.

    Good luck.

  • June 13, 2005 at 10:14 am

    #565059

    It seems you have different schemas, but the publisher article is a subset of the subscriber one - it's normally the exact opposite . In this case I'd replicate the table as it is exactly, and have an additional table on the subscriber containing the PK and the additional column. Use a view on the subscriber to amalgamate the data (inner join) and an instead-of trigger to synchronize the 2 tables.

    HTH,

    PAul Ibison, SQL Server MVP


    Paul Ibison
    Paul.Ibison@replicationanswers.com

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply