Sending an e-mail from a trigger may not be the best approach. The trigger must complete execution in order for the insert to complete (and control is returned to the application that performed the insert). Doing anything inside a trigger that is dependent on something outside SQL Server could cause issues should something get delayed in that external call.

Having a process that polls your table frequently might provide more predictable performance for the applications.

Jay

-----Original Message-----
From: Indra Timilsina [mailto:mssqldba-ezmlmshield-x88276251.[Email address protected]
Sent: Wed 29-Mar-06 10:18
To: LazyDBA Discussion
Subject: creating trigger on publish conflict table

Hi there,



I am looking for information regarding creating trigger on the table.
Below is the detail



-we are using sql 2000 with merge replication.

-using default conflict viewer

-when we publish tables it create conflict table for all the table in
our database, suppose I have table call Jobs, after publishing this
table there is another table created called
"conflict_pulicationname_Jobs".

-when ever there is duplicate entry in jobs table the second entry go to
"conflict_pulicationname_Jobs" and we can view from conflict viewer.

-I would like to create trigger for insert so that when ever there is
new data inserted in this to "conflict_pulicationname_Jobs" table I
will get the email, so that I can quickly go to conflict viewer and
resolved the conflict.



My question is whether I can create trigger on this to
"conflict_pulicationname_Jobs" table or not, if yes should I have to
mention "not for replication " or this should be for replication also.



Your help and information will be appreciated.



Thanks.







---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
Website : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html



MS Sql Server LazyDBA home page