Enterprise Replication
Posted in 2000
Topics: High Availability & Replication, Triggers, Constraints & Referential Integrity
_______________________________________________________________ This message and any attachments are intended for the individual or entity named above. If you are not the intended recipient, please do not read, copy, use or disclose this communication to others; also please notify the sender by replying to this message, and then delete it from your system. Thank you. _______________________________________________________________ When using Enterprise Replication, do both tables involved have to be identical? For example, can I have triggers or column on the secondary table that are not present on the primary table? I think the answer here would be no, they need to be identical, but I thought I'd check with you fine people. TIA
They do not have to be *that* identical. They do not have to have the same triggers. Also since ER can use collumn mapping, the source and target do not have to have the same rows. "Colleen M. Morrow" wrote: > _______________________________________________________________ > > This message and any attachments are intended for the individual or entity > named above. If you are not the intended recipient, please do not read, > copy, use or disclose this communication to others; also please notify the > sender by replying to this message, and then delete it from your system. > Thank you. > _______________________________________________________________ > > When using Enterprise Replication, do both tables involved have to be > identical? For example, can I have triggers or column on the secondary > table that are not present on the primary table? I think the answer here > would be no, they need to be identical, but I thought I'd check with you > fine people. TIA