For each database that will be published in transactional replication, ensure that the transaction log has ample space allocated. The transaction log of a published database may require more space than the log of an identical, nonpublished database. If the distribution database is unavailable, or if the Log Reader Agent is not running, the transaction log of a publication database continues to grow. The log cannot be truncated past the oldest published transaction that has not been passed into the distribution database (unless replication is turned off completely for that database).