Hi Folks,

I have recently set up Snapshot replication in my team . The DB is usually about 9GB in size. But from during the same time replication started, I see 12 new tables added to the DB (at Publisher):

dbo.MSpeerIsns,

dbo.MSpeer_request,

dbo.MSpeer_response,

dbo.MSpeer_Identity_range,

dbo.sysarticlecolumns,

dbo.sysarticles,

dbo.syspublications,

dbo.sysreplservers,

dbo.sysschemaarticles,

dbo.syssubscriptions,

dbo.systranschemas

My questions are:

1. with Snapshot Replication going on with 2 subscribers hosted on a different server, will the transaction log on the publisher increase?( does snapshot replication have anything to do with transaction log's increase in size? )

[ note: The subscribers are initializing(syncing) constantly and the publisher does a snapshot dump to a share twice daily) note that over the past week, the publisher DB size has increased to 22GB. It could be the actual data thats being pushed into the DB, or it could be Replication. I'm trying to remove Replication as a culprit to transaction log size increase.]

Thanks in advance,

Kiran