One other way to reset a tran log for a restored database that is showing REPLICATION and won't shrink is to detach the database, rename or delete the log file...

When we moved this fix to production, it work for one subscription and failed for two others. After a little more trial and error I was able to determine...

I have discovered the solution by trial and error. Uninstalling SP3 and the hotfix from the Distributor only seems to have corrected the problem.

Update to the problem - I create numbered copies of all the stored procedures and reran the snapshot. I received the same error as before. I copied the...

Thanks I'll try that!  Any ideas how long every one needs to be kicked off for a 160 GB database?

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.

Thanks for the info.  I did get it working using the full snap shot.  You have to make sure you have the bulkinsert flag on in the distributor.

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?

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...