Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
CorpDirect
Yak Posting Veteran
92 Posts |
 Posted - 2006-01-17 : 18:18:01
|
| Hello all,We're working with an accounting application that breaks when we enable replication on its tables. Can't get around it at this time, though we have put in a feature request to fix this in future releases.Since we can't replicate, we're thinking to duplicate key tables and maintain them using "replay triggers" on the source tables to keep data in the duplicate tables synchronized.Essentially, we'll have identical tables, and for each insert, update, and delete that occurs on the source table, we want to "replay" the same on the destination table -- just like transactional replication would do, if we could use it.I've read this article here on SQLTeam, which concepts may help in generating the necessary code, but I wanted to ask if anyone can offer suggestions for the best way to implement "replay" triggers?Thanks,Daniel |
|
|
CorpDirect
Yak Posting Veteran
92 Posts |
Posted - 2006-01-18 : 09:41:44
|
| To put the question in different words:Is it possible to capture each INSERT, UPDATE or DELETE statement using a trigger? -- then perhaps use REPLACE to modify the table name and execute the same statement on the copy table?Thanks,Daniel |
 |
|
|
|
|
|
|
|
replay triggers when replication won't work