Push Subscription Failed

  • Message: "Could not drop object "table" because it is referenced by a FOREIGN KEY constraint.

    The subscribing database is a very similar schema and i would like to keep the constaints in place.  Is there anyway of sychronising whilst mainting relationships at the same time?

     

  • Which type o replication are you using? And does the FK source data exist on both servers so that any data sent across will not fail?

  • Just discovered that i have to include all referenced tables in the publication.  I was attempting to publish a table that referenced another table not in the publiication.

    Thanks anyway.

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

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