guptaajay1985 (6/30/2009)

---

I have successfully implemented Transactional replication yet only tables which has primary key has populated on subscriber and the data is also not replicating on subscriber. I have used push subscription and no schedule.

ps (6/30/2009)

---

your log reader agent must be running continously or at specified intervals to read the log of the published database and bring 'changes' to subscribed articles to the distribution database. Once the transactions are moved to the distribution db, the distribution agent moves the transactions to the subscribers.
As suggested by Rajan, your log reader job must be scheduled for the transactions to move to distribution db.

side-effect - Since you've not scheduled your log reader agent, your publisher db's log will keep on growing (backing up the log wont truncate log as the db is replicated).