"Elena" <Elena@discussions.microsoft.com> wrote in message
news:1BB8B4FF-07E4-44A3-AAE7-A37022F1ABDD@microsoft.com...
>I got following:
> 1. no free space left on disk because transaction log size. It became 114
> GB.
> 2. replication agent rollbacked transactions
> 3. only after it stopped the work I could truncate and shrink the log
> 4. changed recovery model from simple to bulk logged
> 5. I started distribution agent again but got the same picture. It seems
> that the log will occupy all 200 GB. I do not have space on disk necessary
> to
> finish initial syncronization. What can I do in this situation? Can I
> avoid
> such growth of the log?
> Database is 160 GB. It is heavy used almost all the time. I do not have
> opportunity to get downtime.
>
> "Hilary Cotter" wrote:
>
>> Did you dump it?
>>
>> --
>> 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
>>
>> "Elena" <Elena@discussions.microsoft.com> wrote in message
>> news:C409F1DD-A8AC-41C6-B688-C4DBF6D7C2C7@microsoft.com...
>> > Unfortunately even in recovery model full, I can't free space
>> > - log is active, all pages are in use.
>> >
>> > Elena" wrote:
>> >
>> >> Recovery model is simple, do I really need to change it to full?
>> >> TLog should be truncated.
>> >>
>> >> "Hilary Cotter" wrote:
>> >>
>> >> > put it in full recover model, dump the tlog, then shrink it to
>> >> > something
>> >> > smaller, and put it in bulk copy mode.
>> >> > --
>> >> > 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
>> >> >
>> >> > "Elena" <Elena@discussions.microsoft.com> wrote in message
>> >> > news:E617B877-A6E6-42ED-9A62-7432D9FC3E96@microsoft.com...
>> >> > > Hi,
>> >> > > Transactional log on the subscriber is growing so fast that is
>> >> > > running of
>> >> > > disk space. I can't truncate and shrink it. What can be done in
>> >> > > this
>> >> > > situation?
>> >> >
>> >> >
>> >> >
>>
>>
>>

"Elena" <Elena@discussions.microsoft.com> wrote in message
news:42956588-265D-4D03-B6EE-252A33B096EC@microsoft.com...
>I know that I need to disable triggers on subscriber. I have no identity
> columns. But do I need to delete constraints (FK) on the subscriber?
>
> "Hilary Cotter" wrote:
>
>> this database is likely too large to synchronize via the snapshot. Can
>> you
>> restore a copy of it on the source server, truncate any tables you don't
>> need, and make sure all identity columns, triggers, and constraints are
>> not
>> for replication.
>>
>> --
>> 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
>>
>> "Elena" <Elena@discussions.microsoft.com> wrote in message
>> news:1BB8B4FF-07E4-44A3-AAE7-A37022F1ABDD@microsoft.com...
>> >I got following:
>> > 1. no free space left on disk because transaction log size. It became
>> > 114
>> > GB.
>> > 2. replication agent rollbacked transactions
>> > 3. only after it stopped the work I could truncate and shrink the log
>> > 4. changed recovery model from simple to bulk logged
>> > 5. I started distribution agent again but got the same picture. It
>> > seems
>> > that the log will occupy all 200 GB. I do not have space on disk
>> > necessary
>> > to
>> > finish initial syncronization. What can I do in this situation? Can I
>> > avoid
>> > such growth of the log?
>> > Database is 160 GB. It is heavy used almost all the time. I do not have
>> > opportunity to get downtime.
>> >
>> > "Hilary Cotter" wrote:
>> >
>> >> Did you dump it?
>> >>
>> >> --
>> >> 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
>> >>
>> >> "Elena" <Elena@discussions.microsoft.com> wrote in message
>> >> news:C409F1DD-A8AC-41C6-B688-C4DBF6D7C2C7@microsoft.com...
>> >> > Unfortunately even in recovery model full, I can't free space
>> >> > - log is active, all pages are in use.
>> >> >
>> >> > Elena" wrote:
>> >> >
>> >> >> Recovery model is simple, do I really need to change it to full?
>> >> >> TLog should be truncated.
>> >> >>
>> >> >> "Hilary Cotter" wrote:
>> >> >>
>> >> >> > put it in full recover model, dump the tlog, then shrink it to
>> >> >> > something
>> >> >> > smaller, and put it in bulk copy mode.
>> >> >> > --
>> >> >> > 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
>> >> >> >
>> >> >> > "Elena" <Elena@discussions.microsoft.com> wrote in message
>> >> >> > news:E617B877-A6E6-42ED-9A62-7432D9FC3E96@microsoft.com...
>> >> >> > > Hi,
>> >> >> > > Transactional log on the subscriber is growing so fast that is
>> >> >> > > running of
>> >> >> > > disk space. I can't truncate and shrink it. What can be done in
>> >> >> > > this
>> >> >> > > situation?
>> >> >> >
>> >> >> >
>> >> >> >
>> >>
>> >>
>> >>
>>
>>
>>