Subject: SQL Server Replication causes database to grow and log to grow larger than expected<BR> <BR> <BR>Issue: <BR> <BR>I am transferring about 30 MB of data with replication from Database A to Database B on the same server. I am running SQL Server 2000 on the server. Database A is approximately 270MB in total. I am using transactional replication and am using transactional based, push subscription to populate Database B. Database B is initially empty and again I am not transferring all data from Database A. Once the initial snapshot populates the database, I will only be transferring about 12000 records per day. <BR> <BR>The issue is that Database B is growing to over 200MB in size, and the log is growing to 65MB. Yet I know the data size of the replication is only 30MB. I have tried shrinking the database, with no results, and have tried to truncate the log. When I tried to truncate the log, I get a message "The log was not truncated because records at the beginning of the log are pending replication. Ensure the Log Reader Agent is running or use sp_repldone to mark transactions as distributed."<BR> <BR>When I look at the Log Reader agent it seems to be running, and its history says it has applied transactions as it should. Also, the data IS successfully replicating to Database B as it should.<BR> <BR>Any ideas on why Database B is growing so large??<BR>