Post reply

different schema definitions

  • March 29, 2007 at 2:03 am

    #172609

    I have a problem with a merge replication. I made a change in my schema with an Alter Table statement (two new columns) and then the publisher ignored these changes. Now it is not possible to synchronize the subscribers in the replication. The error message is:

    The schema definition of the destination table dbo.xxx in the subscription database does not match the schema definition of the source table in the publication database. Reinitialize the subscription without a snapshot after ensuring that the shema definition of the destination table is the same as the source table.

     

    Has anyone an idea, how to get the  two columns to the subscriber to have the same schema without making a new subscription? The only way I know is to delete the subscription and add the two columns and then create a new subscription. but I think I will loose the not synchronized datachanges? Is there a way not to loose the different data?

     

    Thanks

     

    Thomas

  • July 18, 2007 at 8:51 am

    #720389

    Hi Tom,

    I realize your post is old and you probably already came across this but for the others out there - this touted feature in SQL 2005 does NOT work.  You cannot replicate schema changes.  Read this post for more information:

    http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1695860&SiteID=1

    Basically - we are all back to the "features" of SQL 2000...unable to replicate schema changes.

    Sure hope MS has a fix / solution soon!

    -Dave

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

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