Home / server / Questions / 56872
Accepted
Refracted Paladin
Asked: 2009-08-21 13:07:46 +0800 CST

Merge Replication: I dropped a table and now I can't reinitialize

  • 772

I have a SQL 2005 Standard*(Publisher/Distributor)* to SQL 2005 Express*(subscriber)* Replication Topology. I deleted(thru SSMS) a table and added a row to a different table. I then ReInitialized All with a Generate New Snapshot option and then ran my Subscribers Sync() Procedure.

I now get the below errors and I have no flippin idea what I should do about them...

Error messages:
The schema script 'tblCaseNotes_3.sch' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
Get help: http://help/MSSQL_REPL-2147201001
Could not drop object 'dbo.tblCaseNotes' because it is referenced by a FOREIGN KEY constraint. (Source: MSSQLServer, Error number: 3726)
Get help: http://help/3726

tblCaseNotes is the Primary table so I don't know why it is trying to drop it...

sql-server

1 Answers

  1. Best Answer

    When you push out a new snapshot to the subscribers, default practice is to drop all the tables in the snapshot and recreate them.

    As the table that you dropped on the publisher was probably related to the tblCaseNotes table you'll need to manually drop that table on all your subscribers. Then the snapshot will be able to be loaded.

    • 2