Merge Replication issue with the data type geography

Alfie B. Larioza 1 Reputation point
2022-03-30T09:20:49.327+00:00

188304-image.png

looking for help about our problem in merge replication in sql 2019.

SQL Server Migration Assistant
SQL Server Migration Assistant
A Microsoft tool designed to automate database migration to SQL Server from Access, DB2, MySQL, Oracle, and SAP ASE.
527 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Olaf Helper 44,301 Reputation points
    2022-03-30T09:28:05.807+00:00

    Read the error message: Schema definition Publisher/Subscriber mismatch. The tables on both side must have the same definition.


  2. CathyJi-MSFT 21,866 Reputation points Microsoft Vendor
    2022-03-31T06:47:40.02+00:00

    Hi @Alfie B. Larioza ,

    > The Merge Agent failed because the schema of the article at the Publisher does not match the schema of the article at the Subscriber. This can occur when there are pending DDL changes waiting to be applied at the Subscriber. Restart the Merge Agent to apply the DDL changes and synchronize the subscription.

    Please restart the sync process. From the client in a pull situation, or restart from the publisher in a push situation.

    In short the application of DDL changes ran into a conflict but restarting the sync will usually resolve the issue. And no, it doesn't start from the beginning, it should just pick up from the point of failure.

    Refer to this similar thread.

    > Error converting data type varchar to geography

    Please check data type of values that changed in articles. Did you enter the wrong data type?


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.