Re: Log won't Truncate when Publication is created

The log reader is not replicating all the transactions. The log is
"truncated" at the last replication point - or where transactions are read
out of the transaction log and marked as replicated.

Are you certain you are using snapshot replication? Normally you get this
with transactional replication.

I would also use transactional replication as it means (in most situations)
that less data is going across the wire.

--
Hilary Cotter

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



"Bodhicitta" <Bodhicitta@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3923DF8C-3BC1-4D25-A7C5-03CA22DCC106@xxxxxxxxxxxxxxxx
We are having an issue whereby the log file on a database will not
truncate
once a snapshot publication is created for the database.

-The database is set to the Simple Recovery Model.
-Data in the database is updated/refreshed every 3 hours via a series of
stored procedures which complete in about 25 minutes.
- As soon as a snapshot publication and push subscription are created,
with
each pass of the stored procedures (every 3 hours) which update the
database,
the active portion of the log grows, eventually causing the log file to
autogrow, and eventually we run out of disk space.
- The publication is scheduled to create a snapshot once per day, and the
subscriber is scheduled to synchronize with the snapshot thereafter.
-The database is fully backed up once per day, about an hour after the
snapshot is created.
-The stored procedures are not running while either the snapshot or backup
are in progress. When no publications are present, the log file stays
small
due to the Simple Recovery Model.
-The log truncates as soon as I delete the publication.

What is causing the log to grow like this? Thanks.


.

Relevant Pages

  • Re: Newbie question: "No replicated transactions are available"
    ... "No replicated transactions are available" - Snapshot replication does not ... > day and the distribution agent running 24 times per day, ...
    (microsoft.public.sqlserver.replication)
  • Re: Prefetch objects failed Error when added more than 2 table as
    ... snapshoting tables and then came the line:The replication agent had ... seeing (Prefetch objects failed for Database 'myDB'), ... snapshot agent from the command line with -OutputVerboseLevel of 2. ...
    (microsoft.public.sqlserver.replication)
  • Re: Replicating with Access in Hilarys book
    ... database as a subscriber and if all the changes originate there it could act ... Looking for a SQL Server replication book? ... In the hint, it says in part, "all transactions occuring on the Merge ...
    (microsoft.public.sqlserver.replication)
  • Re: Replication Suggestions
    ... Works well as long as the transactions are all going in one ... >>I have an application with a sql backend. ... >> database on the webbox and an internal database for inter-company use. ... I'm new to replication and I'm not sure what the best way ...
    (microsoft.public.sqlserver.replication)
  • Re: Log wont Truncate when Publication is created
    ... Looking for a SQL Server replication book? ... recreating the snapshot publication. ... database is almost completely rebuilt with each update, ... log space is to delete the publication. ...
    (microsoft.public.sqlserver.replication)
Loading