Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Replication--altering data in replicated tables?

Status
Not open for further replies.

jsteph

Technical User
Oct 24, 2002
2,562
US
Hi all,
We use a replicated sql-server 2000 database from a major payroll vendor for most of our PR/HR reporting. This vendor's live hosted database has some incorrect and missing data, which they refuse to correct, for reasons unexplained.

So my question is two-part:
1. If I add rows to our replicated db, will the replication process 'find' these rows and delete them?

2. If I alter values in existing rows will the replication find them and change them back?

Thanks,
--Jim
 
1. No. However if you reapply the snapshot to your subscriber then yes, the rows will be removed.

2. No, unless you change the values on the production system, or your reapply the snapshot to the subscriber then yes.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog
 
Denny,
Thank you, that clears most if it up...but one thing is unclear--does the replication update the entire record or only the field that changes? For example, the production version's record may change--but in another single field, and the field I update in the replica I'd hope stays the same.

And I'm probably getting too far off tangent here, and it's academic because in my situation I see no triggers...but what happens with triggers--are they simply disabled in the replica? It seems that if they weren't things would get pretty complex.
Thanks,
--Jim
 
Replication should only be pushing the columns that change.

SQL Replication won't push any triggers to the subscribers, and the changes effected by the triggers would be pushed to the subscribers, so the triggers aren't needed on the subscriber.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top