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 |
|
Svetyha
Starting Member
2 Posts |
 Posted - 2002-10-30 : 10:38:48
|
| Hi!I have setup transactional replication between two SQL Server 2000 servers. I have configured a push subscription from the publisher db. Replication works correctly. But I have a problem with firing triggers on subscriber's table (triggers don't fire).Does anybody know a way to fire triggers during replication process?I appreciate your help. |
|
|
KnooKie
Aged Yak Warrior
623 Posts |
Posted - 2002-10-31 : 09:20:11
|
| What sort of transactional replication have you set up ??Uni or bi directional ?===========Paul |
 |
|
|
Tim
Starting Member
392 Posts |
Posted - 2002-10-31 : 20:52:56
|
| just wondering if the triggers have NOT FOR REPLICATION option in effect?probly not but it sounds like something I would fall for.----Nancy Davolio: Best looking chick at Northwind 1992-2000 |
|
|
|
samrat
Yak Posting Veteran
94 Posts |
Posted - 2002-10-31 : 22:23:36
|
| Greetings,looks like NOT FOR REPLICATION is in effect in your trigger, which is stopping your trigger from executing during the replication process.. If you find, thats not the case, then can you do a simple test by adding the data at subscriber and see if the trigger fires.Let us know if that happens.Cheers,Samrat |
|
|
|
Svetyha
Starting Member
2 Posts |
Posted - 2002-11-01 : 10:28:37
|
| Hi!I don't have the NOT FOR REPLICATION option set in my trigger.I am so sorry but it was my fault in problem's discription. In actual fact the trigger wasn't been fired during applying the initial snapshot only. And I found out from the documentation that foreing key constraints? check constraints, and triggers will be disabled during the concurrent snapshot generation and will be enabled after the snapshot is generated. Thanks for your time. |
|
|
|
|
|
|
Triggers and Replication