sql server replication: Hello,

I took over a project several months ago. I am a basic Client/Server app
developer. I have experimented a little with replication and am currently
studying a book on the subject of replication, but otherwise have no real
industrial experience with replication. Today I just noticed some
triggers in a table, and I am pretty sure I recently recreated that table
(maybe I just copied it), and this table happens to be under replication.
There are 3 triggers for Delete, Insert, Update. They start as follows:

create trigger del_1368F74E47AA41ACB6FB5B4A168CD855 on [dbo].[WorkShop] FOR
DELETE AS
if sessionproperty('replication_agent') = 1 and (select
trigger_nestlevel()) = 1
return
/* Declare variables */
declare @tablenick int, @retcode smallint, @reason nvarchar(255), @nickname
int, @lineage varbinary(255), @oldmaxversion int
....

create trigger ins_1368F74E47AA41ACB6FB5B4A168CD855 on [dbo].[WorkShop] for
insert as
if sessionproperty('replication_agent') = 1 and (select
trigger_nestlevel()) = 1

....

create trigger upd_1368F74E47AA41ACB6FB5B4A168CD855 on [dbo].[WorkShop] FOR
UPDATE AS
if sessionproperty('replication_agent') = 1 and (select
trigger_nestlevel()) = 1
....

Did Sql Server Replication add these triggers to the table or were they
manually added? The database I am working with is using Merge and Snapshot
replication - or is that Transactional and snapshop? I still get confused
between the expression Transactional Replication and Merge Replication.
There are some other tables in the database that are under replication but do
not contain triggers like these. Any explanations greatly appreciated.

Thanks,

Thanks very much for the explanation. I feel much better now.

Question: At what point do these triggers get created? Do they get created
when the Merge Replication is initially set up? Or is it possible for me to
drop the table and re-create it - and the Merge replication will re-create
the triggers?

Thanks,
Rich

[quoted text, click to view]