Keeping the transaction log small during initialization

How do I keep the transaction log small during initialization of a
subscription. The size of the transaction gets to be at least four
times the size of the data and fills up the hard drive.
Is there a way to initialize the database without keeping the
transaction logs?
I can't seem to truncate and shrink during initialization either.
Any help is greatly appreciated.
Michael Swart
There is no real way to do this, other than a no sync subscription, or to
kick everyone off your publication database while you generate the snapshot.
You might also want to run DBCC Opentran to see if there are any open
transactions which are causing your tlog to balloon.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Michael Swart" <mjswart@.yahoo.com> wrote in message
news:22f04e15.0408040512.115202ca@.posting.google.c om...
> How do I keep the transaction log small during initialization of a
> subscription. The size of the transaction gets to be at least four
> times the size of the data and fills up the hard drive.
> Is there a way to initialize the database without keeping the
> transaction logs?
> I can't seem to truncate and shrink during initialization either.
> Any help is greatly appreciated.
> Michael Swart