using triggers to keep all versions of rows after update, delete + replication
i maintain application uses sql 2005 / 2008 data persistence. clients use merge replication (pull or push) replicate data. of tables contain information should never erased. versions of row such table should stored, somewhere in database. means updates , deletes rows should result in in 2 affected rows: • copy of row before change • row containing change (or deletion of row in question) plan achieve using after update,delete triggers on tables "versioning" required. old versions of row may stored in same database, other database (or database on linked server). hoping creating not replication triggers on published database. theory was: update , delete queries performed against subscribed database should replicated (for concurrency) publisher. when updates , deletes replicated, triggers on published database fired, updating table containing version rows. there seem 2 problems approach: 1/ update query against table of subsc...