Mr. Cotter,
Thank you for your response. Have I chosen the wrong replication option for
As for the transaction log, it is being backed up every hour. DBCC OPENTRAN
being fairly old. I removed the snapshot replication and I don't have the
example in front of me right now. But the output is similar to the following
"Hilary Cotter" wrote:
> At some levels transactional and snapshot replication are considered to be
> the same, for example in sp_replicationdboptions if you want to enable a
> database for snapshot or transactional replication, the parameter you pass
> it the same. They also use the same activex control.
>
> If your log is getting out of control you should try dumping it more
> frequently when it is in bulk logged or full recovery models. Also check to
> ensure there are no open transactions by issuing calls to dbcc opentran.
>
> --
> Looking for a SQL Server replication book?
>
http://www.nwsu.com/0974973602.html >
> Looking for a FAQ on Indexing Services/SQL FTS
>
http://www.indexserverfaq.com > "hmscott" <hmscott@discussions.microsoft.com> wrote in message
> news:E86B58AD-EB7E-423B-BB43-6DE092250389@microsoft.com...
> > SQL 2005 (SP1, +2153)
> >
> > Why does creating a Snapshot publication (with only stored procedures and
> > functions) set the Transactional option on the Publisher?
> >
> > My intent is to create two separate publications (one Merge, the other
> > Snapshot). The Merge publication contains the data articles (tables) and
> > is
> > horizontally filtered. The Snapshot publication is intended to be for
> > Stored
> > procedures and UDFs and is not filtered.
> >
> > But when I create the Snapshot publication, the Transactional publication
> > option is set on the publisher database. Then I get into an issue where
> > the
> > log file is never truncated.
> >
> > Can someone explain? Should I have created the stored procedures and
> > functions in a Merge publication?
> >
> > Regards,
> >
> > hmscott
>
>
