Turn of logging for bcp for snapshot

  • Is there a way to setup replication without using the snapshot?  The Publication database is a 24/7 databases that cannot be taken off line.

    The backup/Copy/Restore takes about 5 hours.  How can I make sure that all the transaction make it accross?

    First post by the way.

    Rob.

  • Welcome.

    Hey, I'm not sure what your having trouble with.

    But replication/taking a snapshot does not take the primary(publication) database offline.

    There is no way to start sql server replication without a snapshot. It is the only way sql server will perform the replication. There may be some other home grown more code involved methods, but I have never tried.

    When you start replication you do not need to backup/copy/restore the database, sql server does it all for you.

    From Books Online:

    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/replsql/repltypes_2f8z.asp

     

  • After I posted this I discovered part of the problem.  I originally posted thinking that the bcp aren't batched but I discovered I have the database in Full logging and no backup running so I filled the log.

    Thanks.

  • OK I was wrong.  The replication is not commiting the transaction between bcp's when loading the snapshot.  Does anyone know how to force replication to commit when loading the snapshot?

  • I figured it out.  There is a bulk insert flag on the distributor that has to be turned on so it does log every insert.

  • Could you explain ?  I don't quite follow what your problem & solution are ?   Where's the bulk insert flag ?

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply